Data Loss Prevention
Data Loss Prevention
Data Loss Prevention
Business brieng
October 2011
Contents
Introduction ................................................................... 1 Understanding the problem ............................................. 2 Challenges ..................................................................... 6 Employing a holistic approach ....................................... 10 Data governance ....................................................... 13 Data loss prevention controls ..................................... 16 Supporting information security processes ................. 17 Using technology to support the DLP program ............ 18 Ernst & Young insights and lessons learned ................... 20 Dont be a victim .......................................................... 21
Data loss prevention (DLP) is the practice of detecting and preventing condential data from being leaked out of an organizations boundaries for unauthorized use. Data may be physically or logically removed from the organization either intentionally or unintentionally.
Introduction
Over the last few years, companies in every industry sector around the globe have seen their sensitive internal data lost, stolen or leaked to the outside world. A wide range of high-prole data loss incidents have cost organizations millions of dollars in direct and indirect costs and have resulted in tremendous damage to brands and reputations. Many different types of incidents have occurred, including the sale of customer account details to external parties and the loss of many laptops, USB sticks, backup tapes and mobile devices, to name just a few. The vast majority of these incidents resulted from the actions of internal users and trusted third parties, and most have been unintentional. As data is likely one of your organizations most valuable assets, protecting it and keeping it out of the public domain is of paramount importance. In order to accomplish this, a number of DLP controls must be implemented, combining strategic, operational and tactical measures. However, before DLP controls can be effectively implemented, your organization must understand the answer to these three fundamental questions: 1. What sensitive data do you hold? 2. Where does your sensitive data reside, both internally and with third parties? 3. Where is your data going? This paper explores these questions and the challenges organizations face in relation to business drivers and regulatory obligations for protecting this data. We will share our point of view and approach to data loss prevention, along with insights and lessons learned from our experiences working with some of the most advanced companies in the world on data loss prevention practices.
For a better understanding of the way to address IT Risk and developing an effective IT Risk management function, please refer to Ernst & Youngs Insights on IT Risk paper, The evolving IT risk landscape, published in June 2011. An overview of recent megatrends included in this paper shows that data protection will continue to be a signicant challenge for organizations. Four out of six megatrends discussed are linked to the risk category data, highlighting the fact that many of the technology trends observed in the market result in increasing data risk.
Megatrend
Business benet
Mobile computing: Anytime and anywhere connectivity/ high-volume portable data storage capability Social media: New and advanced information sharing capabilities such as crowdsourcing Lower total cost of ownership Focus on core activities and reduction of effort spent on managing IT infrastructure and applications Contribute to reduction of global carbon footprint
Business/IT risks
Increased vulnerability due to anytime, anywhere accessibility Risk of unintended sharing, amplication of casual remarks and disclosure of personal and company data. The availability of this data on the web facilitates cyber attacks. Employees may violate company policies in terms of data leakage Lack of governance and oversight over IT infrastructure, applications and databases Vendor lock-in Privacy and security Availability of IT to be impacted by the use of the cloud Increased risk to regulatory noncompliance (e.g., SOX, PCI). The cloud also brings about challenges in auditing compliance. The cloud may impact the agility of IT and organizations; the platform dictated by the provider may not align with software development and strategic needs of the user Failure of the business continuity and disaster recovery plans causing nancial or reputational loss
Emerging consumerization
Security and privacy Data Third-party suppliers and outsourcing Applications and databases Infrastructure Legal and regulatory
24/7/365 availability of IT systems to enable continuous consumer support, operations, e-commerce, and other functions
Spread of malicious code in company systems, causing system outages The risk of theft of personal, nancial and health information Loss of condential data due to external vulnerabilities Financial loss due to unauthorized wire transfers Assigning access rights that are beyond what is required for the role by employees or contractors Failure to remove access rights to employees or contractors who leave the organization
N/A
Fast adoption of new business models or reducing costs provides organizations with competitive advantage
Failure to deliver IT projects and programs within budget, timing, quality and scope causing value leakage
But good statistics on this phenomenon are very hard to get, and the gures available will never represent the actual situation because many more leaks and data breaches go unreported. There is not a nite number that can be reported with certainty, because there is no single repository for incident tracking and these statistics only include incidents that reach the media or are self-reported by companies. The only certainties are that leakage happens and that it is a growing problem. It is not only the number of incidents but also their magnitude and the increased attention of the general public that increase the impact of an incident for any organization.
Description
Outside legal counsel, mail notication, calls, call center and discounted product offers Employees diverted from other tasks Customer churn and difculty in getting new customers FTC, PCI, SOX Civil courts may ask to put this money aside in case breaches are discovered The security and audit requirements levied as a result of a breach Credit card replacement costs. Civil penalties if specic fraud can be traced to the breach
$20 $20 $0 $0
$0
$5
$10
$0
$0
$25
$90
$155
$305
Source: The Forrester Wave: Information Security and Risk Consulting Services, Q3 2010, Forrester Research, Inc., 2 August 2010.
1 Calculating The Cost Of A Security Breach, Khalid Kark, Forrester Research Inc, April 10, 2007.
Several high-impact incidents have occurred recently that have resulted in high costs and extreme media attention for the affected companies:
Online storage were at risk of a data breach. As soon as the bug was discovered, as a precaution all logged in sessions were provider disconnected. The bug was active for almost four hours and took ve minutes to x.
So, what is new? Threats of data loss from internal users have always been a risk. To sum up the changing landscape and increasing risk: 1. There are now many more ways data can leave an organization (i.e., data loss vectors). 2. Storage is cheap. Many gigabytes of data can walk out of the door on an employees keychain or smartphone or be sent through online systems such as Dropbox. 3. Data is everywhere. Decentralized systems and work collaboration tools make it much more difcult for organizations to track and control information within the business. 4. Data has value in the real world, including from seemingly legitimate sources. 5. The most recent generation of workers to join companies has grown up with openness and information sharing as a cultural norm.
6. It is easier than ever for data to cross borders, and demand for sensitive information is coming from all over the world as companies (and nations) try to gain competitiveness in the global marketplace. 7. The sheer volume of data is increasing as never before. In addition to business risks, regulatory risks are also increasing. The volume, impact and visibility of incidents has resulted in renewed focus from regulators. Data protection requirements, particularly breach notication rules, for organizations are becoming more strict, and enforcement penalties are on the rise. From a companys perspective, reducing the risk of data loss reduces regulatory risk and helps to protect the companys brand, strategic business data and intellectual property.
Challenges
From our experience, one of the greatest challenges in managing data loss is that there are so many reasons why data loss can occur, numerous data loss scenarios to account for and many different controls that must be effective in order to manage the problem. There is no simple solution or tool that can be implemented to address the variety of data loss risks that organizations face. In order to address the pervasive issue that data loss risks pose, a comprehensive solution that includes people, processes and technology needs to be implemented.
Cause
Loss or theft of laptops and mobile devices Unauthorized transfer of data to USB devices Improper categorization of sensitive data Data theft by employees or external parties Printing and copying of sensitive data by employees Insuf cient response to intrusions Unintentional transmission of sensitive data
Effect
Brand damage and loss of reputation Loss of competitive advantage Loss of customers Loss of market share Erosion of shareholder value Fines and civil penalties Litigation/legal action
Customer data
Sales
Your data
Contractors
HR, Legal
Finance
Transaction data
egulatory nes/sanctions Signi cant cost and effort to notify affected parties and recover from the breach
People
Lack of awareness Lack of accountability Lack of user responsibility for their actions
Process
Lack of data usage policies/guidance Lack of data transmission procedures
Technology
Lack of exibility in remote connectivity No content-aware DLP tools Lack of secure communication platforms
People
Employees do not clearly understand or feel accountable for the protection of sensitive data.
Process
Data protection, data classication and acceptable use policies do not clearly articulate: The controls that should be implemented for securely sending sensitive data to third parties Whether employees may send sensitive data to home computers and personal email accounts The specic data that is considered sensitive and requires data protection controls
Technology
Current remote access tools are not exible enough to support the business, resulting in users employing alternative approaches, such as emailing documents to their personal email accounts, to enable working from home and remote locations.
Training and awareness programs do not focus enough on protecting sensitive data, appropriate use of email and the internet, use of security tools such as le encryption and each employees personal responsibility for complying with information security/data protection policies.
Process owners have not assessed their methods in which sensitive data is shared with third parties to evaluate information security risks.
Content-aware email encryption tools are not effectively used to automatically require encryption of emails containing sensitive data, such as account numbers.
Employees feel that there is no risk involved in breaking the rules (i.e., no one is watching so I will not be caught).
Without an ongoing DLP monitoring program, policy violations cannot be identied efciently, and the success of policy communications, training and awareness programs and technical controls is not measurable.
Secure links between the company and its third parties are not in place to enable encrypted email or other secure transmission methods.
Data category
Customer data
Case description
A frustrated staff member used the standard data export procedures to export sensitive data and copied it to a CD. A database administrator with an understanding of test procedures was able to reverse engineer a sanitized process by referencing hidden tables. An experienced IT developer was able to reconstruct transaction data by gaining access to condential data from an inexperienced developer unaware of the companys access policies and restrictions. A call center staff member provided screenshots of internal systems to fraudsters to help them reverse engineer an application. An employee leaving the company came in over a weekend prior to resigning on Monday, accessed the customer master le and exported it to an Excel le. This le was then emailed to the employees personal email account. An employee with access to prereleased nancial information fed information to an external analyst, resulting in improper stock trades for both the employee and the analyst.
Transaction data
Corporate data
Employee discontent
Corporate data
Insider trading
Corporate data
10
Data at rest
Databases or repositories
Data in use
Laptops
Workstations
Data in motion
Firewall
Workstations
Data at rest
Internet
11
Throughout the remainder of this section, we will explain how this model can be used to help you think through your DLP strategy and risks tackling the three components of the model: Data governance Data loss prevention controls Support for information security processes
Data governance
Policies and standards Identication Risk assessment Classication Architecture Quality
Data in use
Privileged user monitoring Access/usage monitoring Data anonymization Use of test data Data redaction Export/save control
Data at rest
EndPoint security Host encryption Mobile device protection Network/internet storage Physical media control Disposal and destruction
Function areas
Network monitoring Internet access control Data collection and exchange Messaging (email, IM) Remote access
Unstructured data
12
Data governance
Data governance activities help to answer some of the key questions that must be addressed prior to implementing DLP controls, including: 1. What sensitive data do you hold what is your most important data? 2. Where does your sensitive data reside, both internally and with third parties? 3. Where is your data going?
When classifying data from a DLP perspective, for each data type, you must consider the consequences of this data becoming available to unauthorized parties (e.g., business disruption, damage to reputation and brand, regulatory violations and nes, loss of competitive advantage, direct nancial losses). The following categories depicted below are a good starting point for identifying common types of sensitive data.
Future direction
Additionally, it is helpful to assess the risk of the relevant data types that you identify. Examples of considerations for assessing the risk of each data type include: Whether the data is protected by regulations Relative value of internal data (e.g., board papers versus corporate customer lists) Direct impact to customers and business partners Potential impact on brand and reputation Potential loss of competitive advantage in the market Going through this exercise will help you to prioritize DLP activities so that the highest risk data is protected rst.
Corporate data
Price/cost lists Target customer lists New designs Source code Formulas Process advantages Pending patents Intellectual property Unreleased merger/ acquisition plans and nancial reports Legal documents Employee personal data
Transaction data
Bank payments B2B orders Vendor data Sales volumes Purchase power Revenue potential Sales projections Discount ratios
Customer data
Customer list Spending habits Contact details User preferences Product customer prole Payment status Contact history Account balances Purchase/transaction history Payment/contract terms
13
Strategies for identifying sensitive structured data in each type of location include working with the business and IT to identify repositories that hold sensitive data, as dened through the data classication exercise. This can be accomplished through a combination of: Business process walk-throughs Use of questionnaires sent to business process owners, analysts, database administrators, application developers, business intelligence/report developers and other relevant parties. Reviews of existing documentation (e.g., data ow diagrams, application descriptions, information held in IT asset inventories). Unstructured sensitive data, by denition, will reside in unpredictable locations, as well as on commonly known network shares, internal sites and end-user repositories. As is the case with structured data, inquiry of business users and IT personnel can provide useful information about commonly used data stores. However, due to the nature of unstructured data, these sources are not likely to be complete. For this reason, the use of tools should be considered to assist in data discovery. DLP discovery tools have advanced signicantly over the last two years and can provide the following features that aid in data discovery: Scanning of known network shares, intranet sites, wikis and databases with different levels of access privileges Scanning of network segments to identify undocumented share drives, databases and servers Scanning of user workstations to identify sensitive data stored on local drives These activities can be performed using rules designed to detect sensitive data. Rules should be customized for your organization based on the high-risk data types identied. Through the use of these tools, repositories containing sensitive data can be identied and then steps can be taken to ensure that these repositories are secure or to move sensitive data to more appropriate locations.
14
DLP concepts that should be documented in policies include: Transmission of sensitive data through email and the internet Storage of sensitive data on mobile devices, laptops, workstations and non-company owned equipment Storage of sensitive data on company le and document repositories (where it is acceptable and not acceptable to store sensitive data) Appropriate use of remote access technologies Use of technology not provided by the organization (such as work use of personal email accounts, portable devices, storage and media) User responsibilities for classifying data at the point of creation and ensuring that sensitive data users create is included in relevant data/information inventories In addition, DLP principles should be used to drive security requirements in system development and change projects. Example principles include: Sensitive data may not be transmitted through public networks without adequate encryption Only company-approved technologies may be used to exchange data with third parties Access to sensitive data must be logged and monitored where appropriate Access to sensitive data stored on information systems must be restricted to those who require it to perform their job responsibilities Sensitive data may not be shared with third parties without sufcient contracts in place specifying information security requirements, their obligations to protect company data, their responsibilities for monitoring their own third parties and the companys right to audit and monitor Sensitive data must be anonymized before being stored in less controlled environments, such as test and development environments Sensitive data must be adequately protected through all stages of the data lifecycle and the systems development lifecycle (SDLC)
Future direction
15
Data in motion
Focus area Perimeter security Network monitoring Internet access control Example of control objective Prevent unencrypted sensitive data from leaving the perimeter Log and monitor network trafc to identifying and investigate inappropriate sensitive data transfers Prevent users from accessing unauthorized sites or uploading data through the web through personal webmail, social media, online backup tools, etc Supporting technologies DLP technology, rewalls, proxy servers DLP technology Proxy servers, content lters
Data collection and exchange Ensure that data exchange with third parties only occurs through secure means with third parties Use of instant messaging Remote access Prevent le transfers to external parties through instant messaging and other non-web-based applications Ensure that remote access to the company network is secured and control the data that can be saved through remote facilities such as Outlook Web Access Example of control objective Monitor the actions of privileged users with the ability to override DLP controls, perform mass data extracts, etc Monitor access and usage of high-risk data to identify potentially inappropriate usage Sanitize/anonymize sensitive data when it is not required for the intended use Do not use or copy sensitive data into non-production systems. Sanitize data before moving into test systems when possible Remove sensitive data elements from reports, interfaces and extracts when they are not necessary for the intended use Restrict user abilities to copy sensitive data into unapproved containers (e.g., email, web browsers) including controlling the ability to copy, paste and print sections of documents
Secure email, secure FTP, secure APIs, encrypted physical media Firewalls, proxy servers, workstation restrictions Encrypted remote access, restrictions on use of remote access tools to prevent data leakage to non-corporate assets Supporting technologies Security information and event monitoring, operating database and application log les Security information and event monitoring, operating database and application log les, endpoint DLP logs Data sanitation routines and programs Data sanitation routines and programs
Data in use
Focus area Privileged user monitoring Access/usage monitoring
Data redaction
Export/save control
16
Data at rest
Focus area Endpoint security Example of control objective Supporting technologies Restrict access to local admin functions such as the ability Operating system workstation restrictions, security software (e.g., A/V, personal to install software and modify security settings. Prevent rewall, etc.), endpoint DLP technology malware, viruses, spyware, etc Ensure hard disks are encrypted on all servers, workstations, laptops and mobile devices Harden mobile device congurations and enable features such as password protection and remote wipe facilities Govern access to network-based repositories containing sensitive data on a least privilege basis Prevent the copying of sensitive data to unapproved media. Ensure that authorized data extraction only takes place on encrypted media. Ensure all equipment with data storage capabilities are cleansed or destroyed as part of the equipment disposal process (including devices such as digital copiers and fax machines) Full disk encryption tools Built-in security features, third-party mobile device control products Access control software and permission control in operating systems, databases and le storage systems Endpoint DLP technology, endpoint media encryption tools, operating system workstation restrictions Data erasure/data wiping software
information security processes section of the DLP conceptual model will help you identify key controls outside of the DLP program that can impact your overall effectiveness in managing data loss risks. It is essential that DLP controls and supporting information security controls are implemented and that the effectiveness of these controls is monitored over time. Having a structured data loss risk management program and a clear set of controls to mitigate data loss risks can provide a holistic view of data loss potential across your organization. The DLP conceptual model can also aid in building a customized data loss risk dashboard and performing current-state assessments.
17
Purpose
Control user capabilities on endpoint systems Detect and report on sensitive data in motion Scan the network and specic hosts/shares to identify and report (and potentially quarantine) unprotected sensitive data Detect sensitive data owing through endpoints and stop trafc that violates DLP rules
Endpoint technologies are more difcult and slower to deploy, but they provide more direct control over user actions and coverage for systems that are connected outside of the corporate network. Network-based technologies can be deployed very quickly and provide greater coverage on the internal network, but they are generally unable to scan encrypted trafc and can impact network performance when they are in prevent mode i.e., blocking inappropriate trafc. A hybrid approach provides multiple layers of defense with detect and prevent capabilities but is more costly than a single approach to deploy.
18
Monitor phase
Prevent/protect phase
Risk reduction
Network monitoring (data in motion) Endpoint monitoring and discovery (data at rest) Network prevent Endpoint prevent (data in use) low
low
Complexity
These include:
high
Difculty scaling to support many languages Limited effectiveness in identifying sensitive intellectual property Limited built-in support for standard data formats outside of the United States Limited deployment capabilities in different countries based on local privacy laws These are among the reasons that effective people and processes are as important as ever in managing data loss risks. Users must be aware of the risks, DLP roles and responsibilities must be clearly dened and processes must be in place to properly congure DLP tools and to act efciently on the output.
19
Lessons learned
From our involvement helping many clients with their DLP programs, we have identied the following practices that can help to make a DLP program successful: Determine goals and objectives for your DLP program up front As with all change initiatives, DLP programs should help achieve strategic business objectives and provide benets in return for the costs incurred. Clear goals and objectives based on the company strategy and mission should be determined up front as a baseline for your program. This will ensure that the program is focused on protecting the data that is most important to the business. Address all aspects of people, process and technology As we have illustrated, a defense-in-depth approach must be taken, with clear roles and responsibilities for individuals, tfor-purpose tools to identify and prevent data loss and effective processes to research and respond to incidents. Establish ample executive support, understanding and participation Company-wide support and involvement from various business and operating units will create more user acceptance of the transition toward a more secure environment and will help to ensure that business input is provided at key stages. Dening sensitive data is a fundamental requirement Implementing DLP technology and controls universally across an organization has an adverse and costly impact on the business. By dening sensitive data up front and aligning the program to protect their most sensitive data, organizations can ensure that resources are spent managing the highest risks. Focus on a defense-in-depth approach, not just complying with legislation A DLP implementation should not be based solely on solving your compliance issues but should focus on the entire risk spectrum that affects your data.
Ownership for non-user Service accounts accounts Non-primary user accounts without documented owner Lack of engagement from relevant stakeholders Lack of coordination with business stakeholders Project viewed as an IT project only
20
Top practical tips to help optimize your data loss prevention program
1. Identify and classify your data. A well-developed, granular
data classication scheme will enable your company to design and implement the proper controls for different types of data. A data inventory, linking the data classication scheme to specic data held within the IT infrastructure and with external parties, will help appropriately scope your DLP program.
7. Understand data usage and ows and your data loss vectors. Organizations need to understand how data is being
used and how it can leave the organization. Tools should be implemented to monitor data trafc ows within your infrastructure. File access monitoring can increase your current knowledge of data usage within the organization, and networkbased DLP tools should also be considered to gain visibility over data owing across internal networks and to the internet.
5. Do not permit the copying of sensitive data to removable media. Endpoints should be congured to
disable writing to all removable storage devices, or alternatively, content-aware endpoint DLP technology should be in place to prevent sensitive data from being copied from the source. Mobile devices like laptops and mobile smartphones or PDAs should have full disk encryption, and your company should have the ability to erase them remotely if they are lost or stolen.
Dont be a victim
The ever-evolving risk landscape is becoming more challenging to manage. With data loss, prevention is always better than recovering after a breach. Todays common threats are accelerating by technological evolution. Data loss through social media, consumerization, cybercrime and internal threats represent increasing business risks. An organization that knows which data is most vital to its business operations, understands where that data resides and how that data is sent beyond its walls will achieve competitive advantages in the marketplace. It is important to use that knowledge to ensure that key business data is effectively protected and that the organization rapidly and efciently responds to incidents that occur.
21
Contacts
Global
Norman Lonergan (Advisory Services Leader, London) Paul van Kessel (IT Risk and Assurance Services Leader, Amsterdam) +44 20 7980 0596 +31 88 40 71271 norman.lonergan@uk.ey.com paul.van.kessel@nl.ey.com
Advisory Services
Robert Patton (Americas Leader, Atlanta) Andrew Embury (Europe, Middle East, India and Africa Leader, London) Doug Simpson (Asia-Pacic Leader, Sydney) Naoki Matsumura (Japan Leader, Tokyo) +1 404 817 5579 +44 20 7951 1802 robert.patton@ey.com aembury@uk.ey.com
doug.simpson@au.ey.com matsumura-nk@shinnihon.or.jp
troy.kelly@hk.ey.com stagno-gvnn@shinnihon.or.jp