Safe at Any Speed: Formalizing Consumer Privacy Risk Management

In light of ever-increasing speed in time to market, new technology products and their updates can be rife with data privacy risks. Follow this guidance to manage the risk.

safe at any speed formalizing consumer privacy risk management

As regulators and legislators consider new approaches to addressing consumer privacy, CISOs and colleagues in technology and consumer products companies that use personal data should reconsider how they’re balancing their management of data privacy risks and the need for speed. Developing a privacy risk analysis capability is a useful way to address consumer privacy issues without impeding the rapid pace at which the company puts forth new products and updates of existing offerings.

Many technology companies update their products on a weekly, if not daily, basis. And many, though certainly not all, of those updates pose potential data privacy risks. The trick is to quickly and reliably identify which new products and/or updates can give rise to privacy risks and then mitigate those risks, while letting updates that have little or no impact on consumer data privacy zip through the filter.

When a company releases 10 bits of code to production, the code should be subject to a privacy assessment process that evaluates the data privacy risks as quickly and as unobtrusively as possible. However, when that update moves a button from one side of a user’s screen to the other side, that change likely does not need to be subject to a comprehensive risk impact assessment.

A privacy risk analysis consists of three enabling activities:

  • Inventory privacy risks: Start by developing a long list of privacy risks related to specific offerings that a company confronts. When developing this list, keep in mind that data privacy issues often arise when a company begins using data in ways that it has not done previously. A platform, app, or product update might contain a new feature that relies on geolocation data to track customers, for example. If the privacy policy indicates that the company does not use geolocation data to track consumers, that update warrants additional scrutiny. In addition to strengthening the identification and mitigation of privacy risks, this inventory helps support efficiency. After all, it’s much quicker to assess whether a software update might trigger one or more of 50 or 100 defined privacy risks than to start the assessment from scratch each time.
  • Involve your engineers: Most data privacy missteps are unintentional, and many of these unintentional mistakes occur as second-degree impact of a change that otherwise poses a minimal direct risk. A slight change to an in-car app’s algorithm may have the unintended effect of letting a third party track the vehicle. These types of unexpected data privacy impacts are precisely why software engineers should be involved in identifying the privacy risk inventory and analyzing whether a product update might trigger a privacy risk. Engineers can walk their data privacy and security colleagues through discussions along the lines of if we make this update, the consumer will do X, which will cause Y and Z to happen.
  • Mitigate and document: When a privacy risk associated with an update occurs, the privacy team must determine what actions to take to reduce that risk to an acceptable level. And that mitigation should be documented. If the car app update might let an unauthorized third-party track someone’s vehicle, the team should document the technical and procedural controls that were put in place to prevent that outcome from occurring.

While developing and refining a privacy risk analysis requires a fair amount of upfront work and ongoing collaboration, its design is relatively straightforward. Yet many organizations lack this capability, not because of its intricacy, but due to other common hindrances, such as:

  • Compliance myopia: Some organizations overfocus on compliance-related privacy risks while neglecting risks that arise from using consumer data in ways that depart from the stated policy and/or other promises that the company has previously made to consumers. Compliance risks are important, of course, but many types of privacy risks lurk beyond the reach of regulations.
  • Reacting instead of reaching out: In some cases, privacy teams only get involved in the software development lifecycle by invitation – when a member of the development teams thinks a change might create a data privacy problem. The reality is that far more changes in the development lifecycle have potential privacy impacts than many development teams realize.
  • Ineffective filtering: Without a comprehensive list of privacy risks, too many software and product changes with privacy risk implications slip through the filter without being mitigated.

A sound privacy risk analysis program helps companies overcome those obstacles without interfering with the roll-out of new functionality and new products.

This article was written by Jeffrey Sanchez.


Copyright © 2022 IDG Communications, Inc.