Last week IBM developerWorks released a three-part guidance series I have written to help
Application Developers develop GDPR compliant applications.
Developing GDPR Compliant Applications Guidance
- Part 1: A Developer’s Guide to the GDPR
- Part 2: Application Privacy by Design
- Part 3: Minimizing Application Privacy Risk
The General Data Protection Regulation (GDPR) was created by the European Commission and Council to strengthen and unify Europe’s data protection law, replacing the 1995 European Data Protection Directive. Although the GDPR is a European Union (EU) regulation, it applies to any organizations outside of Europe that handle the personal data of EU citizens. This includes the development of applications that are intended to process the personal information of EU citizens. Therefore, organizations that provide web applications, mobile apps, or traditional desktop applications that can indirectly process EU citizen’s personal data or allow EU citizens sign in are subject to the GDPR’s privacy obligations. Organizations face the prospect of powerful sanctions should applications fail to comply with the GDPR.
Part 1: A Developer’s Guide to the GDPR
Part 1 summarizes the GDPR and explains how the privacy regulation impacts and applies to developing and supporting applications that are intended to be used by European Union citizens.
Part 2: Application Privacy by Design
Part 3: Minimizing Application Privacy Risk
Part 3 provides practical application development techniques that can alleviate an application’s privacy risk.
*** This is a Security Bloggers Network syndicated blog from IT Security Expert Blog authored by Dave Whitelegg. Read the original post at: http://feedproxy.google.com/~r/securityexpert/~3/1eUYupRlmQE/application-development-gdpr-compliance.html