Is Your Data Safe? How to Assess Your Data Risk - Part 1
May 25, 2021

Christophe Toum
Talend

Share this

Data is one of a company's most valuable assets — but Talend's recent Data Health Survey found only 40% of executives always trust the data they work with.

Today, we have codes and inspections for physical infrastructure, satisfaction surveys for employees, and up-time monitors and stability tests for websites. But are we doing everything we can to understand the degree to which our data is exposed to risk?

There's more to security than protecting yourself from hackers. On one end of the spectrum, you have those big exposures to governmental regulations and security breaches that can shake an entire organization. But even small things — like a little bit of bad data entering the system — can cause a trickle down effect that impacts every department.

We could all be doing a better job of assessing (and mitigating) risk to our data. The key is to start small: just make sure that you have the right data in the right place.

Then you want to make sure that the right people have access to the data and the wrong people don't have access to the data.

Once you have that covered, and you've defined processes for keeping your data clean and standardized, then you can start focusing on making that a daily practice. All it takes is the right combination of people, processes and technology.

What Do We Mean by "Risk?"

When most people think about the risks associated with data, they immediately recall the headline-grabbing data breaches that seem to flood our news feeds with alarming regularity.

But it doesn't take an epic leak affecting millions of users to have serious consequences for most companies. Even a handful of exposed records could have serious legal, financial and reputational repercussions. Fines for GDPR violations alone can run in the millions of dollars, to say nothing of the incalculable cost of losing consumer trust in an increasingly connected and competitive marketplace.

How do these breaches happen?

It can be something as simple as the right data in the wrong place. So much of our conversation about security centers around personally identifiable information (PII). If PII data isn't identified or isn't in the right field — for example, payment information erroneously mapped to an unprotected field and viewed by unauthorized individuals — you could be at risk of exposing some very sensitive information.

But external risks aren't the only dangers we should be worried about. A few years ago, IBM famously calculated that bad data costs US businesses over$3 trillion per year. This is death by a thousand cuts, parceled out in seconds, minutes and hours lost to manual data correction, re-running suspect reports and pursuing strategies and programs that were originally scoped based on data that was later revealed to be faulty.

Of course, the volumes of data we must deal with has grown by over 400% since IBM released that study — and it's only growing.

So how much could we be losing today?

And how much do we stand to lose over the coming years?

Taking all these dangers into account, one thing is clear: no company can afford to expose its data to risk.

Go to: Is Your Data Safe? How to Assess Your Data Risk - Part 2

Christophe Toum is Senior Director of Product Management at Talend
Share this

The Latest

March 23, 2023

APMdigest and leading IT research firm Enterprise Management Associates (EMA) are partnering to bring you the EMA-APMdigest Podcast, a new podcast focused on the latest technologies impacting IT Operations. In Episode 2 - Part 1 Pete Goldin, Editor and Publisher of APMdigest, discusses Network Observability with Shamus McGillicuddy, Vice President of Research, Network Infrastructure and Operations, at EMA ...

March 22, 2023

CIOs have stepped into the role of digital leader and strategic advisor, according to the 2023 Global CIO Survey from Logicalis ...

March 21, 2023

Synthetic monitoring is crucial to deploy code with confidence as catching bugs with E2E tests on staging is becoming increasingly difficult. It isn't trivial to provide realistic staging systems, especially because today's apps are intertwined with many third-party APIs ...

March 20, 2023

Recent EMA field research found that ServiceOps is either an active effort or a formal initiative in 78% of the organizations represented by a global panel of 400+ IT leaders. It is relatively early but gaining momentum across industries and organizations of all sizes globally ...

March 16, 2023

Managing availability and performance within SAP environments has long been a challenge for IT teams. But as IT environments grow more complex and dynamic, and the speed of innovation in almost every industry continues to accelerate, this situation is becoming a whole lot worse ...

March 15, 2023

Harnessing the power of network-derived intelligence and insights is critical in detecting today's increasingly sophisticated security threats across hybrid and multi-cloud infrastructure, according to a new research study from IDC ...

March 14, 2023

Recent research suggests that many organizations are paying for more software than they need. If organizations are looking to reduce IT spend, leaders should take a closer look at the tools being offered to employees, as not all software is essential ...

March 13, 2023

Organizations are challenged by tool sprawl and data source overload, according to the Grafana Labs Observability Survey 2023, with 52% of respondents reporting that their companies use 6 or more observability tools, including 11% that use 16 or more.

March 09, 2023

An array of tools purport to maintain availability — the trick is sorting through the noise to find the right one. Let us discuss why availability is so important and then unpack the ROI of deploying Artificial Intelligence for IT Operations (AIOps) during an economic downturn ...

March 08, 2023

Development teams so often find themselves rushing to get a release out on time. When it comes time for testing, the software works fine in the lab. But, when it's released, customers report a bunch of bugs. How does this happen? Why weren't the flaws found in QA? ...