The systemic privacy issues in our digital infrastructure stem largely from a fundamental design flaw: privacy is only considered reactively, once personal data is already flowing. Consumer trust is more valuable than ever, and the legal stakes for respecting personal data continue to climb. Appointing a privacy engineer to check boxes at the time of deployment won't cut it...the status quo for data context and data control - in other words, privacy controls - needs to change.

Analogous to AppSec's leftward shift, privacy responsibility lies with builders and maintainers of data and software systems. This requires resources for developers to embrace their role in tasks like evaluating privacy risk with minimal friction, compatible with the array of modern data infrastructure. Cillian will share actionable steps to implement Privacy by Design and offer just one example of what it could look like in action with open-source devtools for automated privacy checks in the CI pipeline.

Connect with us: Website: https://databricks.com Facebook: https://www.facebook.com/databricksinc Twitter: https://twitter.com/databricks LinkedIn: https://www.linkedin.com/company/data... Instagram: https://www.instagram.com/databricksinc/