GDPR

GDPR configuration evidence for Azure

The GDPR requires appropriate technical and organisational measures to protect personal data. When that data sits in Azure, many of the technical measures take the form of configuration settings. Equalis OpsReg checks those settings with 74 rules and keeps the result as evidence.

74 of the 437 rules belong to GDPR. Both plans include all five frameworks.

What the text asks of your Azure environment

Article 5(1)(f) requires personal data to be processed in a manner that ensures appropriate security, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organisational measures. Article 5(2) adds that the controller is responsible for, and must be able to demonstrate, compliance with these principles.

Article 25 requires data protection by design and by default: appropriate technical and organisational measures, both when the means of processing are determined and during the processing itself, and by default no wider accessibility than necessary. In Azure, part of this shows in how storage accounts, databases and networks are configured, for example whether data is publicly exposed by default.

Article 32 lists measures to implement as appropriate to the risk, among them the pseudonymisation and encryption of personal data; the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services; the ability to restore the availability of and access to personal data in a timely manner in the event of a physical or technical incident; and a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures.

What Equalis OpsReg checks

74 rules, applied to every connected subscription on every scan. The areas below are the main ones.

Encryption at rest

Storage accounts, databases and disks, including key management settings.

Encryption in transit

Minimum TLS versions and HTTPS-only settings on exposed services.

Public exposure

Public network access and firewall rules on data services.

Logging

Diagnostic settings and log retention on data services such as storage accounts and databases.

Backup and restore

Backup configuration that supports the ability to restore personal data required by Article 32(1)(c).

Access

Role assignments and access settings on data resources.

What remains your responsibility

Equalis OpsReg evaluates technical configuration in Azure. The following obligations are organisational and are not scored by the platform.

  • Records of processing activities (Article 30)
  • Data protection impact assessments (Article 35)
  • Legal bases, information notices and data subject requests
  • Breach notification procedures (Articles 33 and 34)
  • Contracts with processors (Article 28)

Key facts

Legal instrument
Regulation (EU) 2016/679
Applies since
25 May 2018
Who it applies to
Controllers and processors established in the EU, whether or not the processing takes place in the EU, and those outside the EU that offer goods or services to, or monitor the behaviour of, people in the EU (Article 3)
Supervisors
National data protection authorities, such as the CNIL in France, the APD/GBA in Belgium, the CNPD in Luxembourg and the DPC in Ireland
Administrative fines
Up to €10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year (Article 83(4), which covers among others Articles 25 and 32), and up to €20 million or 4% for infringements of, among others, the basic principles, data subjects' rights, transfer rules or orders of a supervisory authority (Article 83(5) and (6)), whichever is higher

Contact

Demonstrations are run in French or English, in thirty minutes, by the people who build the platform.

EqualisTech OpsReg Limited
The Black Church, St. Mary's Place
Dublin 7, D07 P4AX, Ireland
contact@equalistech.com
Request a demonstration (opens in a new tab)