Privacy Engineering As a Competitive Advantage
Should this idea be revolutionary? Perhaps not, but it’s a departure from how many developers and tech executives regard privacy practices. The era of “bolt-on” and stop-gap privacy patching is coming to an end. The stakes are high as users are growing increasingly aware of privacy issues.
What Is Privacy Engineering and Why Does it Matter?
Privacy Engineering is a method for implementing Privacy by Design principles using engineering methods. It’s been said that privacy engineering provides the “how” – a methodology for the inclusion and implementation of privacy requirements as an integral part of systems engineering.
The drive for innovation often overlooks privacy. Privacy engineering can bridge the gap, shedding light on where the crucial concepts of PbD and innovation must be reconciled. Privacy engineering is not only an insurance policy against costly lapses in privacy compliance—it also helps companies build more robust products users can trust.
Wired Magazine’s recent article, The Privacy Revolt: The Growing Demand for Privacy-as-a-Service, should help underscore the point: Privacy engineering is not a competitive advantage for the distant future. The future is right now in terms of customer demand.
As noted in the article:
“No matter what market you’re in, no matter what service you provide or product you sell… from right now until the end of time, you’re in the privacy game. Welcome.”
How Do You Implement Privacy Engineering?
Though it depends on the maturity and structure of each organization, engineers and legal teams must work together to incorporate effective PbD principles into the development and product review cycle. This involves keeping policy and implementation in alignment and planning for ongoing compliance beyond the initial launch.
One tool is the Privacy Impact Assessment (PIA), which defines the objectives of the system in terms of privacy risk analysis. This Privacy Engineering Whitepaper from the Information and Privacy Commissioner of Ontario includes a discussion of the core steps of a PIA. It also discusses the concepts of data minimization, obfuscation, abstraction, aggregation, and integration of user controls. These design strategies are the “how” and point developers to tangible requirements they can incorporate into the design and development of products.
Marketing teams also need visibility into privacy engineering implementation and can perform a valuable role in understanding attitudes about privacy. A recent article in Marketing Land, Marketers’ Balancing Act Between Value And Privacy provides a compelling view of the need for technology that is privacy-conscious by default and explains how privacy is a complex, personal issue for users.
Where Do You Find Privacy Engineers?
You’re not the only one with that question. The White House has also been on the hunt for privacy-minded technology professionals, and they’ve found them in the private sector. Demand for privacy engineers will continue to rise.
As Ann Cavoukian, former Privacy Commissioner in Ontario, Canada, has said:
“To embed privacy by design into all things involving information technology, we will need to have privacy engineers, of which there are currently very few.”
Fortunately, institutions are working to expand the profession, including Carnegie Mellon’s Master of Science in Information Technology-Privacy Engineering program.
The MSIT-PE degree is a one-year program designed for computer scientists and engineers who wish to pursue careers as privacy engineers or technical privacy managers. A detailed list of privacy engineering skills can be found on the Carnegie Mellon website and is aligned closely with PbD principles for privacy engineers (PDF).
Privacy engineers are privacy champions! We thank you for your great work!