Annex 2: Technical and organizational measures
a) Entry Control
Measures to prevent unauthorized persons from accessing data processing systems with which personal data are processed.
The Service is a PaaS service consumed by EasyLife and governed by Microsoft 365. There is no physical access to such environments.
b) Access Control
Measures to prevent the use of data processing systems by unauthorized persons:
- - Assignment of user rights
- - Password assignment
- - Authentication with username/password
- - Use of intrusion prevention systems
- - Additional measures: web-application firewalls, regular vulnerability scans, regular penetration testing, patch management, minimum requirements for password complexity
- - Access Control governed by Conditional Access, Privileged Identity Management (PIM), and Multi-factor Authentication
- - Encryption of storage accounts
- - Use of mobile device management (for example, remote locking and wiping of smartphones)
- - Hardware encryption for notebooks
- - Use of a software firewall (office clients)
c) Access Rights Control
Measures to ensure that those authorized to use a data processing system can only access the data subject to their access rights and that personal data cannot be processed, used, or stored without authorization, read, copied, modified, or removed:
- - Creation of an authorization concept
- - Number of administrators reduced to the "absolute minimum.”
- - Logging of the application access, especially for entry, modification, and data deletion
- - Hardware encryption
- - Rights management by system administrators
- - Password policy with guidelines on password length, password change management
d) Transfer Control
Measures to ensure that personal data cannot be read, copied, altered, or removed without authorization during electronic transmission or while being transported or stored on data carriers and that it can be verified and ascertained to which bodies the transmission of personal data using data transmission facilities is intended:
- - Documentation of data recipients and transmission times, including agreed deletion times
- - Hardware encryption
- - Data disclosure (only) in anonymized or coded form
- - Overview of general requests and delivery operations
- - TLS encryption for all communications (web client, APIs, mobile apps)
e) Input control
Measures to ensure that it is possible to verify at a later date whether and by whom personal data can be entered, modified, or removed in data processing systems:
- - Logging of entry, modification, and deletion of data
- - Traceability of data entry, modification, and deletion by individual users (not user groups)
- - Assignment of rights for entry, modification, and deletion of data based on an authorization concept
- - Creation of an overview of the approved applications for entering, modifying, or deleting data
- - Storage of forms through which data has been collected using automated processing
f) Instruction control
Measures to ensure that data further processed on behalf and in agreement with the data controller are only processed on its instructions:
- - Selection of subcontractors taking into account their history (especially about information security)
- - Written instructions to subcontractors
- - Ensure that subcontractors have appointed a data protection officer
- - Effective control rights assured by subcontractors
- - Prior review of documentation and security measures taken by subcontractors
- - Obligation of subcontractor's employees to maintain confidentiality
- - Secure deletion of data at the end of the contract
- - Continuous monitoring of subcontractors and their activities
g) Availability Check
Measures to ensure that personal data is protected against accidental destruction or loss:
- - Testing of data recovery
- - Creation of backup & recovery concepts
- - Preparation of an emergency response plan
- - Several data centers in the active configuration
h) Principle of Separation
Measures to ensure that personal data collected for different purposes are processed separately:
- - Creation of an authorization concept
- - Records with purpose attribute/data fields
- - Authorised and documented database rights
- - Logical client separation (at software level)
- - For coded data: Separation of the assignment file and storage on a separate secured IT system
- - Separation of productive and test systems