One of the core responsibilities of data engineers is to manage the security of the information that they process. The team at Satori has a background in cybersecurity and they are using the lessons that they learned in that field to address the challenge of access control and auditing for data governance. In this episode co-founder and CTO Yoav Cohen explains how the Satori platform provides a proxy layer for your data, the challenges of managing security across disparate storage systems, and their approach to building a dynamic data catalog based on the records that your organization is actually using. This is an interesting conversation about the intersection of data and security and the lessons that can be learned in each direction.
- Hello and welcome to the Data Engineering Podcast, the show about modern data management
- When you’re ready to build your next pipeline, or want to test out the projects you hear about on the show, you’ll need somewhere to deploy it, so check out our friends at Linode. With their managed Kubernetes platform it’s now even easier to deploy and scale your workflows, or try out the latest Helm charts from tools like Pulsar and Pachyderm. With simple pricing, fast networking, object storage, and worldwide data centers, you’ve got everything you need to run a bulletproof data platform. Go to dataengineeringpodcast.com/linode today and get a $60 credit to try out a Kubernetes cluster of your own. And don’t forget to thank them for their continued support of this show!
- Your host is Tobias Macey and today I’m interviewing Yoav Cohen about Satori, a data access service to monitor, classify and control access to sensitive data
- How did you get involved in the area of data management?
- Can you start by describing what you have built at Satori?
- What is the story behind the product and company?
- How does Satori compare to other tools and products for managing access control and governance for data assets?
- What are the biggest challenges that organizations face in establishing and enforcing policies for their data?
- What are the main goals for the Satori product and what use cases does it enable?
- Can you describe how the Satori platform is architected?
- How has the design of the platform evolved since you first began working on it?
- How have your experiences working in cyber security informed your approach to data governance?
- How does the design of the Satori platform simplify technical aspects of data governance?
- What aspects of governance do you delegate to other systems or platforms?
- What elements of data infrastructure does Satori integrate with?
- For someone who is adopting Satori, what is involved in getting it deployed and set up with their existing data platforms?
- What do you see as being the most complex or underserved aspects of data governance?
- How much of that complexity is inherent to the problem vs. being a result of how the industry has evolved?
- What are some of the most interesting, innovative, or unexpected ways that you have seen the Satori platform used?
- What are the most interesting, unexpected, or challenging lessons that you have learned while building Satori?
- When is Satori the wrong choice?
- What do you have planned for the future of the platform?
This article has been published from a wire agency feed without modifications to the text. Only the headline has been changed.