For years, financial institutions focused on perimeter security to thwart the ever-increasing number of data threats. But now, with more than 50 percent of security breaches perpetrated internally, perimeter defenses are no longer sufficient for securing data.
Today, companies need to extend their data infrastructure across business units, partners, suppliers, customers, and a growing mobile workforce. The outsider is now an insider. Because of this, financial institutions must adopt an enterprise data protection strategy in order to effectively protect data from the core to the edge of the enterprise, an end-to-end encryption solution across databases, applications, networks, and endpoint devices. The result is secure data at all times—at rest, in motion, and in use.
"An effective data privacy solution must follow the data from the core, where key data repositories exist, to the edge, where the data is used.”
- Derek Tumulak
Many financial institutions are looking towards consolidation and merging security infrastructures in an effort to cut costs, retain customers, and improve business processes. Be careful. Data is extremely vulnerable during consolidations because it resides on multiple heterogenous systems that are often complex, incompatible, and difficult to secure; the slightest hiccup can be disastrous.
Classifying Sensitive Data
Data classification is an important element of achieving data privacy. When performing this task, take the following actions:
� Determine data confidentiality levels
� Identify and classify sensitive data.
� Determine where sensitive data is located
� Determine data access models
Define a Security Policy Around Identified Data
Once the data identification and classification process is complete, you are ready to develop a security policy, which turns enterprise expectations into tenable objectives. The essential points of a comprehensive security policy include the following:
� Acceptable Threat Level—Determine an acceptable level of threat, keeping in mind that the sooner in the data processing life cycle the data is encrypted, the more secure the overall environment.
� Authentication and Authorisation Policies—Develop an authentication and authorisation policy that leverages best practices and historical information to help determine which users, processes, and applications have access to sensitive information.
� Compliance Measures—Identify the legislative measures that apply to your organisation, and, once an acceptable threat model is agreed upon, translate those legislative requirements into technical requirements.
Determine a Mode of Data Privacy Implementation
Implementing a data privacy solution can be done at multiple points within the enterprise. Choosing the point of implementation dictates the work ahead and significantly affects the overall security model.
� Network-level encryption guarantees the most secure deployment of a data privacy solution, ensuring that the data is secured at every point within the enterprise. Enterprises routinely interact with customers, partners, and other entities over the Internet, and secure the transport of those communications with well-defined and mature technologies, such as SSL and IPsec. Yet, once these secure communication points are terminated, typically at the network perimeter, secure transports are seldom used within the enterprise. Consequently, information that has been transmitted is in the clear and left unprotected. One solution is to selectively parse data after the secure communication is terminated and encrypt sensitive data elements at the SSL/Web layer. Doing so allows enterprises to choose, at a very granular level, sensitive data and secure it throughout the enterprise.
� Application-level encryption allows enterprises to selectively encrypt granular data within application logic. This solution provides a strong security framework and will leverage standard application cryptographic APIs. This type of solution is well-suited for data elements (e.g., credit cards, e-mail addresses, critical health records, etc.) that are processed, authorised, and manipulated at the application tier. Application-level encryption protects data against database and storage attacks, and theft of storage media.
� Database-level encryption secures data as it is written to and read from a database. This type of deployment is typically done at the column level within a database table and, if coupled with database security and access controls, can prevent theft of critical data. Database-level encryption eliminates all application changes required in the application-level model, and also addresses a growing trend towards embedding business logic within a DBMS through the use of stored procedures and triggers. Careful consideration has to be given to the performance impact of implementing a database encryption solution. First, enterprises must adopt an approach to encrypting only sensitive fields. Second, this level of encryption must leverage hardware to increase the level of security and to offload the cryptographic process in order to minimise any performance impact.
� Storage-level encryption enables enterprises to encrypt data at the storage sub-system, either at the file level (NAS/DAS) or at the block level SAN. This type of encryption is well-suited for encrypting files, directories, storage blocks, and tape media. In today's large storage environments, storage-level encryption addresses a requirement to secure data without using LUN masking or soning.