Last week I took some time to attend the 25th annual Enterprise Data World (EDW) event which ALTR sponsored. If you haven’t had a chance to check it out, it’s one of the most comprehensive educational conferences on Data Management in the world. With 5 key notes, 20 tutorial and 90 conference sessions there was a lot to see and learn in the land of data management.
One of my favorite sessions was “Who's on First? A Tutorial on Data Governance Roles and Responsibilities” by Kathy Rondon, Chief Business Strategist, R2C. Kathy laid out a compelling case around who’s responsible for data governance: everyone.
She explained that data will go through stages throughout its lifecycle, starting with Planning, Acquistion/Creation through to Share/Use and Archive/Dispose. Various roles will touch, modify, and utilize data at each of those points. The Chief Data Officer (CDO) might be responsible for the overall data lifecycle while the Data Owner is responsible for the data produced in their business unit, while Data Stewards and Data Users might get the most benefit from the information to make their jobs more effective and efficient.
Caring for Data Like Your Child
Kathy explained that you can think of this like caring for your child. At various points in a child’s life, there are different caretakers: parents, babysitters, schools, friends. And each environment might require a different kind of protection: a babysitter may need to make sure the child is buckled in for a car ride and friends may need to watch out for cars when playing outside. Most children don’t have one single security guard following them around 24 hours a day making sure they’re always safe.
Data governance is the same: it’s not one person’s job, it’s everyone’s. But unfortunately, that can sometimes mean it’s no one’s. Because it doesn’t live with one specific role, data governance can end up as an “orphan”, like a child whose babysitter thinks the parent is picking up from school that day and parents who think the babysitter is handling it.
Secure Your Slice of the Data Lifecycle
This is similar to something we’ve been talking about for a while: Whose Job Is Data Security, Anyway? Like Doug said in his blog, “When responsibility is distributed across various functions, you can end up with an ambiguous, inefficient mess — and serious security gaps.”
To ensure a child is safe, safety needs to be easy and achievable for everyone responsible: a seatbelt needs to be easily buckled and all the kids need to look out for cars when playing in the street. It’s important that each role has the ability to deal with the risks that crop up in their stage.
When it comes to using data security to enforce data governance policies, we need tools that are easy for everyone to use or buy or spin up or manage. That’s the point of ALTR’s platform: we make data security simple for everyone in the data lifecycle.
With a SaaS-based, no-code, automated solution, whether you’re a CDO or a Data User, you can purchase and use data security for the section of the data you’re responsible for. You can get what you need to fit your role’s security needs and the outcomes required by your function: Data Owners might care about the analytics and the reporting, while the Data Stewards may need to ensure that the actual policies and locks are correct.
Data Security for Everyone
When it’s nobody’s job, it needs to be really easy to secure your slice of the data. It can’t be cumbersome, it can’t be expensive, it can’t be slow. Data security has to be just as easy as putting on a seat belt.
Learn how you can simplify your data governance through automation in our OneTrust + ALTR webinar. Watch now.