Every byte of data has a story to tell. The question is whether the story is being narrated accurately and securely. Usually, we focus sharply on the trends around data with a goal of revenue acceleration but commonly forget about the vulnerabilities caused due to bad data management. Data possesses immense power, but immense power comes with increased responsibility. In today’s world collecting, analyzing and build prediction models is simply not enough. Keep in mind that we are in a generation where the requirements for data security have perhaps surpassed the need for data correctness. Hence the need for Privacy By Design is greater than ever.
“Privacy by Design” and “Privacy by Default” have been frequently-discussed topics related to data protection. The first thoughts of “Privacy by Design” were expressed in the 1970s and were incorporated in the 1990s into the RL 95/46/EC data protection directive. Privacy by design is an approach to systems engineering that seeks to ensure protection for the privacy of individuals by integrating considerations of privacy issues from the very beginning of the development of products, services, business practices, and physical infrastructures. The adoption of security and privacy principles is a crucial step in building a secure, audit-ready program.
Privacy by Design is based on following 7 principles:
- Proactive not Reactive; Preventative not Remedial - Privacy by Design comes before-the-fact, not after.
- Privacy as the Default Setting - it is built into the system, by default.
- Privacy by Design is embedded into the design and architecture of IT systems and business practices
- Privacy by Design seeks to accommodate all legitimate interests and objectives in a positive-sum “win-win” manner not Zero-Sum
- End-to-End Security — Full Life-cycle Protection
- Visibility and Transparency — Privacy by Design seeks to assure all stakeholders that whatever the business practice or technology involved, it is in fact, operating according to the stated promises and objectives,
- Respect for User Privacy — Keep it User-Centric
(c) the purpose of collection and usage of such personal or sensitive personal data;
(d) whether personal or sensitive personal data is being shared with other data fiduciaries or data processors;
(e) reasonable security practices and procedures used by the data fiduciary to safeguard the personal or sensitive personal data that is being processed.
No comments:
Post a Comment