In technology, change is constant. Professionals working in tech are called on to integrate new processes and ways of thinking to stay abreast of their field. A case in point is data privacy.
In technology, change is constant. Professionals working in tech are called on to integrate new processes and ways of thinking to stay abreast of their field. A case in point is data privacy.
If you entered the workforce a decade ago in any number of tech-related tracks, privacy, and processes to protect users was a topic of passing interest. Today, the emergence of GDPR, CCPA, and other landmark pieces of legislation has increased data privacy concerns and has become a pivotal part of the development space and beyond.
This article provides a quick-hit synopsis of how the renewed focus on user data privacy impacts different roles in technology organizations in jurisdictions around the world.
Teams that stay compliant incorporate privacy considerations into the development process while simultaneously balancing ongoing pressures for speed and agility.
The SANS institute suggests several best practices that DevOps teams can do to continue working efficiently. Here are the most crucial.
The fundamental principle that has emerged in the UX space is “privacy by design.”
In the 1990s, Dr. Ann Cavoukian developed these seven principles and embedded data privacy features in the very fabric of a software product. GDPR framers regarded Dr. Cavoukian’s so much that they made “privacy by design” a foundational tenet of their legislation.
Listed below are the seven principles of privacy by design, and UX professionals must now incorporate them into their work.
Product managers are more responsible than most for ensuring their organization heeds new privacy regulation. Above all, they are responsible for product quality. If that product is running in a non-compliant way, it’s undoubtedly a defective product.
Fortunately, product managers have resources across the organization to ensure they are staying up-to-date with privacy reform. In her guide to GDPR Mastery for Product Managers, Karen Cohen runs through a set of clearly defined organizational processes that should be employed to protect from privacy violations:
Published from our Privacy Magazine – To read more, visit privacy .dev
At Ethyca, we believe that software engineers are becoming major privacy stakeholders, but do they feel the same way? To answer this question, we went out and asked 337 software engineers what they think about the state of contemporary privacy… and how they would improve it.
The UK’s new Data Reform Bill is set to ease data privacy compliance burdens on businesses to enable convenience and spark innovation in the country. We explain why convenience should not be the end result of a country’s privacy legislation.
Our team at Ethyca attended the PEPR 2022 Conference in Santa Monica live and virtually between June 23rd and 24th. We compiled three main takeaways after listening to so many great presentations about the current state of privacy engineering, and how the field will change in the future.
For privacy engineers to build privacy directly into the codebase, they need agreed-upon definitions for translating policy into code. Ethyca CEO Cillian unveils an open source system to standardize definitions for personal data living in the tech stack.
Masking data is an essential part of modern privacy engineering. We highlight a handful of masking strategies made possible with the Fides open-source platform, and we explain the difference between key terms: pseudonymization and anonymization.
The American Data Privacy and Protection Act is gaining attention as one of the most promising federal privacy bills in recent history. We highlight some of the key provisions with an emphasis on their relationship to privacy engineering.
Our team of data privacy devotees would love to show you how Ethyca helps engineers deploy CCPA, GDPR, and LGPD privacy compliance deep into business systems. Let’s chat!
Book a Demo