Change is constant in the technology sector, and professionals working in tech are continuously called on to integrate new processes and ways of thinking to stay abreast of their field. A case in point is privacy. If you entered the workforce a decade ago in any number of tech-related tracks, privacy and processes to protect may have been a topic of passing interest. But with the emergence of the GDPR, the CCPA, and other landmark pieces of legislation, privacy concerns have become a pivotal part of development space and beyond. This article provides a quick-hit synopsis of how different roles in technology organizations are impacted by renewed focus on user privacy in jurisdictions all over the world.
Teams must now incorporate privacy considerations into the development process while trying to balance ongoing pressures for speed and agility. The SANS institute suggests a number of best practices that DevOps teams can use to stay privacy compliant while working efficiently. Here are the most crucial:
- Streamlined Access Control: Business processes and systems must ensure only authorized users can access sensitive information. Session management tools like tokens and timeouts should be used to protect against unwanted access.
- Error Handling and logging: DevOps teams must store data logs securely and track all administrative activity, plus all inbound and outbound data processing activities.
- Continuous Integration: DevOps teams should build authentication, password management and other security features into code, and incorporate automated security scanning into the delivery process.
The key principle that has emerged in the UX space is “privacy by design.” this principle was developed in the 1990s by Dr. Ann Cavoukian, and contains seven principles that set out the way that privacy features can be embedded into the very fabric of a software product. The framers of the GDPR had such regard for Dr. Cavoukian’s work that they made “privacy by design” a key tenet of their legislation. Below are the seven principles of privacy by design that UX professionals most now incorporate into their work:
- Proactive not reactive: preventative not remedial
- Privacy as the default setting
- Privacy embedded into design
- Full functionality: positive-sum, not zero-sum
- End-to-end security: full lifecycle protection
- Visibility and transparency: keep it open
- Respect for user privacy: keep it user-centric
Product managers have more responsibility than most for ensuring that their organization heeds new privacy regulation. They’re ultimately responsible for product quality, and if that product is running in a non-compliant way, it’s in essence a defective product. Fortunately, product managers have resources across the organization to help ensure that they’re staying up-to-date with privacy reform. In her guide to GDPR mastery for Product Managers, Karen Cohen runs through a set of organizational processes that should be employed to protect from privacy violations:
- Work closely with legal teams: it’s their responsibility to understand the regulations and how they might impact your product. It’s the product manager’s job to translate their opinions into actionable steps for different stakeholders in the business.
- Research and Compare: domain knowledge is important. So is competitor research. How are other businesses in your sector handling information access requests? What do their opt-in and opt-outs look like on site? These are breadcrumbs your business can follow on a path to privacy success.
- Establish clear ownership: If you have a big complicated product, it’s impossible for a single person to have granular privacy oversight throughout the system. That’s why it’s important for product managers to establish clear roles and areas of ownership, including a structure of command to help support the activities of the GDPR-mandated Data Protection Officer. Building this company infrastructure from scratch is undoubtedly a challenge, but in the long-term this purposeful delegation will beat ad-hoc process every time, and leave your business less vulnerable to breaches and violations.
This Article is Republished from our Privacy Magazine – To read more, visit Privacy.dev