Do You Really Have Big Data, Or Just Too Much Data?Do You Really Have Big Data, Or Just Too Much Data?
Brian Lee, a Practice Leader in CEB’s Compliance & Legal Practice, keeps a keen eye on the information overload happening at enterprises. Here, he provides insight into the dangers of collecting data for its own sake – and offers 5 questions IT professionals can start asking to create a sensible data retention strategy.
September 12, 2016
9 Ways IT Can Ruin Its Relationship With The Business
9 Ways IT Can Ruin Its Relationship With The Business (Click image for larger view and slideshow.)
There is more data available to organizations today than ever before. In 2015 alone, customers, employees, and other users created about 7.9 zettabytes of data globally -- and that number is expected to reach 35 zettabytes in 2020.
The type of information companies are collecting is also multiplying -- from traditional sources such as customer mailing addresses and phone numbers to more advanced demographics, web histories, shopping preferences, and even biometric data.
Advances in technology, computer power, and analytics mean companies can collect and process data in almost real-time. This may lead executives to believe that the more data they have, the greater their advantage. However, collecting a virtually unlimited amount of data can create a serious threat for organizations, because the amount collected often outstrips the ability to protect it.
In fact, when CEB surveyed 54 information risk executives around the globe in 2015, more than three-quarters of them indicated it is harder, or significantly harder, to prevent data breaches than in the past.
If a company does have a data breach containing certain types of sensitive personal information, such as social security numbers or health records, it can trigger additional burdensome legal duties and invite increased regulatory scrutiny, not to mention potential reputational damage.
[Are your new-hire contracts doing more harm than good? Read Why I Banned Non-Compete Clauses From Our Hiring Practices.]
The simplest way to protect sensitive data is not to have it in the first place. But companies drawn in by big data's tantalizing promises often collect too much information in the hopes they will find the time and resources to analyze it later.
Worse, companies often keep data long after its usefulness has passed. Ultimately, there's a difference between big data and "lots of data," and organizations need to regularly evaluate how they use data and set clear guidelines for what they collect and store.
Assess the Value of Data You Collect
Assessing and evaluating the true value of data, and the potential risk of a breach, will help IT leaders set their data strategy and avoid collecting too much. But IT can't do it alone. Creating a sensible data management strategy requires input from stakeholders across the business.
CIOs and other IT leaders charged with managing and protecting data can get the conversation started by asking these six questions:
What is the business need for the information we collect? Too often, companies use a "collect now, analyze later" approach, thinking that more information is better. Instead, leaders should carefully consider how the information will help them achieve their corporate strategy and performance objectives.
Do we have the capabilities to use the data effectively? In addition to understanding the data's value, leaders need to evaluate whether their teams have the skills and capabilities needed to collect, manage, and analyze it. Analytic capabilities required to use and apply information in decision making are rare. Without a capable team of analysts and data experts ready to turn data into insight, it may sit untapped, or worse, be misused.
How would the public react to the information we collect and how we use it? Merely because companies can lawfully collect an enormous amount of customer and employee data doesn't mean they should. Leading companies are working to better understand how customers and employees feel about providing personal data. They weigh the data's potential value against the potential reputational harm from the public knowing the information is being collected, in order to decide whether to collect it.
What information do we need to protect, and at what level and at what cost? Keeping all company information secure is important, but certain types of information like credit card and social security numbers require heightened protection under specific privacy laws or regulations. Losing such sensitive information can turn a data breach into a full-blown privacy failure. Companies need to address and classify these types of information and understand the oversight and compliance costs to retain them.
How long should we keep sensitive data? As business changes, previously collected data can be forgotten. Leading companies incorporate the data they collect into their records management policies to ensure the data does not exist indefinitely. Establishing data's shelf life is a critical step in minimizing the risk of a costly data breach involving low-value data.
Who needs access to the information? Given the multitude of ways to use data, many employees will need access to collected data or to the results of its application. A comprehensive understanding of who will be working with the data can help prioritize risks and pinpoint potential breach points. When determining this, leaders should identify which functions will handle the data, how they will use it, and who might need continuous (as opposed to one-time) access. Take steps to ensure employees who don't need access to sensitive data don't have it.
Information drives many aspects of corporate performance. That said, failing to secure data -- lingering reputational harm. IT professionals have has a role to play in helping their companies adequately assess and evaluate the true value of their data and the potential risk of a breach in order. The best way to do this is to set a successful data strategy and to avoid collecting too much information.
About the Author(s)
You May Also Like