Upload
michelangelo-van-dam
View
598
Download
2
Embed Size (px)
Citation preview
DISCLAIMERThis is not “legal advice” and all points made should be checked with your company’s legal department or consult a legal advisor
for your specific situation!
GENERAL DATA PROTECTION REGULATION (GDPR)
➤ More strict modification of already existing advisories (not rules) of best practices towards protecting privacy data in EU
➤ Become law in all 28 EU countries on May 25, 2018
➤ Impact all businesses that collect and process privacy related data of EU data subjects (even outside of EU)
WHAT GDPR WANTS TO PROTECT
Religion & Beliefs
Physical Appearance
Cultural Background
Sexual Orientation
Social Status
Financial Strength Mental State
Medical Conditions
Studies & Education
Memberships
Loyalty Programs
Identity & Nationality
WHAT IS CONSIDERED “PRIVATE DATA”?
➤ Name, email address, home address, phone number
➤ Social security number, national identity number, passport number
➤ Medical data, social status, religion, political views, sexual orientation, nationality, financial balance
➤ Concert tickets, travel arrangements, library cards, loyalty programs
➤ IP addresses with timestamps
➤ and much more…
PROTECT & SERVE➤ Protect data of EU data subjects
➤ Secure the way you store data
➤ Audit access to data
➤ Know what data is kept in the company
FINES & PENALTIES➤ up to 10 million Euro or 2% of annual
global turnover
➤ up to 20 million Euro or 4% of annual global turnover for more severe infringements
IMPROVING KNOWLEDGEon the private data collected and processed by your company and
who had access to it.
IMPROVE SECURITYGDPR is a risk based approach to protect privacy data. All measures to ensure this protection will improve your overal
security.
ASSESS AND PREPARE
➤ Assess all data across
➤ Clients
➤ Employees
➤ Suppliers
➤ Contacts
➤ Develop a GDPR readiness roadmap
➤ Identify personal data
LOOK OUT FOR KEY IDENTIFIERS
➤ When privacy data contains keys
➤ email address
➤ social security number
➤ national identity number
➤ …
DESIGN
➤ Governance (how are you going to protect the data?)
➤ Training (how are employees handling the data?)
➤ Communication (how is data communicated?)
➤ Processes (how is data processed?)
STANDARDS AND PROCEDURES
➤ Create a company wide standards to handle data
➤ Create procedures for
➤ Collecting data
➤ Processing data
➤ Exchanging data
AUTOMATION IS KEY
➤ Develop and implement
➤ Procedures
➤ Processes
➤ Tools
➤ Deliver GDPR training
➤ Adhere to
➤ Privacy by design
➤ Security by design
DATA MANAGEMENT POLICIES
➤ Data must be protected
➤ Collect the minimum amount of data
➤ Store the data safely (with encryption) and securely
➤ Anonymise the data before processing
➤ Ensure these policies are enforced
IN OPERATION
➤ Execute automated business processes
➤ Monitor security and privacy
➤ Manage data access and consent rights
RIGHT FOR DATA INSIGHT AND “BE FORGOTTEN”
➤ Data subjects
➤ Can request insight in data collected
➤ Can request to be forgotten
MAKE SURE YOU CONFORM TO YOUR POLICIES
➤ Assess that your procedures are implemented
➤ Monitor data access
➤ Report on data activity
➤ Audit on a regular basis the security of your data
➤ Evaluate continuously adherence to GDPR standards
PASSWORD MANAGEMENT
➤ Don’t store data access passwords in common repository
➤ Don’t keep passwords in environment variables*
➤ Make use of an Identity Management System to manage
➤ SSH keys
➤ API keys
➤ DSN’s
➤ Public keys
(*) Why not use environment variables: diogomonica.com
AUDIT TRAILS WITH MIDDLEWARE
➤ Log access to data
➤ Automate anonymising of privacy data
➤ Automate encryption of privacy data
REDUCE ACCESS TO DETAILSIf a user has other ways to communicate with your clients,
remove the visible display of common data elements like full names, email and shipment addresses and phone numbers.
SAME FUNCTIONALITY, BUT KEEPS DATA HIDDEN
➤ Prevents accidentally exposing email and phone numbers (e.g. during a call)
➤ Hides details from end-user, but functionality is still provided
➤ Sending out an email uses build-in mail client
➤ Making calls uses a phone middleware used in the company
➤ Gives clear audit trail on who accessed what
NOT 100% PROTECTION, BUT…
➤ We remove the personal one-on-one communication with customers
➤ We add better access management on customer communication
➤ Full audit trail now possible as communication stays in-application
➤ Less chance for data loss as contact details are kept away from users
…AND DON’T FORGET TO ENCRYPT YOUR STORAGE & COMMUNICATIONS!
App
Data Storage
File Storage
Log Storage
Backup Storage
Public - private key exchange| encrypted data storage
SOME RESOURCES
➤ European Commission: Protection of personal data
➤ EU GDPR Infograph
➤ Charting the Course to GDPR: Setting Sail
➤ Deloitte GDPR Series
➤ InfoSecurity Group GDPR Checklist
➤ Securing MongoDB
➤ Table and tablespace encryption on MariaDB 10.1
Please leave feedback on joind.in to improve this talk
and grab the slides on your way out.
in it2PROFESSIONAL PHP SERVICES
Michelangelo van DamZend Certified Engineer
[email protected] - www.in2it.be - T in2itvof - F in2itvof
Microsoft Azure Zend Framework Consulting
Quality Assurance & Disaster Recovery