Show contents
Technical and organisational measures, commonly shortened to TOMs, are the safeguards organisations use to protect personal data. Under Article 32 GDPR, controllers and processors must select measures that provide a level of security appropriate to the risk. There is no universal checklist that makes every processing activity compliant.
What are technical and organisational measures?
Technical measures are implemented through technology or physical safeguards. Examples include encryption, multi-factor authentication, network segmentation, backups and access-control systems.
Organisational measures define how people and processes handle personal data. Examples include access policies, role assignments, staff training, incident procedures, supplier reviews and scheduled access-right reviews.
The distinction is useful, but the measures work together. An access-control system is ineffective if accounts are not removed when people change roles. A documented incident process is ineffective if monitoring does not detect an incident.
What Article 32 GDPR requires
Article 32 GDPR requires controllers and processors to consider:
- the state of the art
- implementation costs
- the nature, scope, context and purposes of the processing
- the likelihood and severity of risks to people’s rights and freedoms
Depending on the risk, appropriate measures may include pseudonymisation and encryption; measures for ongoing confidentiality, integrity, availability and resilience; the ability to restore access after an incident; and a process for regularly testing and evaluating security controls.
This is a risk-based obligation. Cost is relevant, but it does not override the need for a level of protection appropriate to the risk. A small organisation processing sensitive health data may need stronger safeguards than a larger organisation handling low-risk business contact details.
The security objectives behind TOMs
The European Data Protection Board groups the core security risks around three objectives:
- Confidentiality: personal data is not disclosed or accessed without authorisation.
- Integrity: personal data is not changed accidentally or without authorisation.
- Availability: authorised people can access the data and systems when needed.
Article 32 also refers to the resilience of processing systems and services. Measures should therefore address not only prevention but also detection, response and recovery.
Examples of technical measures
The appropriate controls depend on the processing and its risks. Common examples include:
- encryption for data in transit and at rest, with managed encryption keys
- multi-factor authentication and secure authentication methods
- role-based access controls and the principle of least privilege
- network segmentation, firewalls and protected remote access
- logging and monitoring of security-relevant activity
- secure configuration, vulnerability management and timely updates
- tested backups and documented recovery procedures
- pseudonymisation where direct identification is not required
- secure deletion and disposal of devices, storage media and paper records
- physical access controls for offices, archives and server rooms
Encryption and pseudonymisation reduce risk, but neither automatically removes data from the scope of the GDPR. The design, configuration and operational use of a control determine whether it is effective.
Examples of organisational measures
Organisational safeguards can include:
- a security and data-protection policy with clear responsibilities
- documented onboarding, role-change and offboarding procedures
- regular reviews of accounts, privileges and physical access rights
- training that reflects employees’ roles and the actual risks
- confidentiality obligations and need-to-know rules
- incident detection, escalation and response procedures
- supplier selection, processor agreements and security reviews
- rules for remote work, mobile devices and removable media
- retention and deletion procedures
- business-continuity and disaster-recovery exercises
- regular tests, audits and follow-up of corrective actions
A policy alone is not an effective TOM. Organisations should be able to show that the measure is implemented, used and reviewed.
How to select appropriate TOMs
1. Describe the processing
Record the purpose, data categories, affected people, systems, recipients, locations, retention periods and responsible roles. Existing records of processing activities are a useful starting point.
2. Identify realistic threats and impacts
Consider accidental and deliberate events: unauthorised access, incorrect changes, loss, ransomware, unavailable systems, disclosure to the wrong recipient or failure of a service provider. Assess how each event could affect the people whose data is processed.
3. Review existing safeguards
Document which measures are already in place and where gaps remain. The description should be specific enough to verify: “access control” is less useful than the system, role model, approval process and review interval used.
4. Select and assign improvements
Choose safeguards that reduce the identified risks, assign an owner and set a target date. High-risk gaps should not disappear into a general improvement list.
5. Evaluate residual risk
After considering the safeguards, reassess likelihood and impact. If a processing operation is likely to result in a high risk, a data protection impact assessment may be required under Article 35 GDPR.
6. Test and review
Article 32 expressly includes regular testing, assessment and evaluation. Review TOMs after significant system or process changes, incidents, new threats and supplier changes, as well as at an appropriate periodic interval.
How to document TOMs
Good documentation links each measure to the processing and risk it addresses. It commonly records:
- the measure and its security objective
- the affected processing activities, systems and locations
- the owner responsible for implementation and operation
- implementation status and supporting evidence
- review or test date, result and next action
- accepted residual risk and the person who approved it
This evidence helps controllers demonstrate accountability under Article 5(2) and Article 24 GDPR. Processors also need to provide sufficient guarantees and support the controller’s compliance under Article 28. Documentation does not prove effectiveness on its own; test results, logs, approvals and completed actions make the control verifiable.
A practical TOM checklist
Use these questions as a starting point rather than as a universal compliance certificate:
- Are processing activities, systems, data flows and responsible roles known?
- Are access rights approved, limited and reviewed?
- Are strong authentication and encryption used where the risk requires them?
- Are vulnerabilities, updates and secure configurations managed?
- Are backups protected and restoration procedures tested?
- Can security events be detected, escalated and investigated?
- Are retention periods and secure deletion implemented?
- Are processors and other suppliers assessed and monitored?
- Do employees understand the rules relevant to their work?
- Are measures tested and improvement actions followed to completion?
Managing TOMs with ComplianceOS
When TOMs are kept in separate spreadsheets, policies and supplier files, it becomes difficult to see which measures apply, who owns them and whether evidence is current. ComplianceOS helps teams connect processing activities, risks, measures, responsibilities and supporting records in one structured workflow.
The software does not decide which safeguard is legally sufficient for a particular processing activity. It makes the assessment, implementation status and evidence easier to organise and review. In a discovery call, we can examine which workflow fits your organisation and existing documentation.
Frequently asked questions about TOMs
When are TOMs required?
Controllers and processors must implement appropriate technical and organisational measures whenever they process personal data. The scope and strength of those measures depend on the specific risks.
Does the GDPR contain a complete list of TOMs?
No. Article 32 names examples and assessment criteria, not a closed catalogue. Each organisation must select safeguards for its processing context and keep them effective over time.
Are TOMs only an IT responsibility?
No. IT teams are central to many technical controls, but effective TOMs also require management decisions, process owners, procurement, HR, legal or data-protection expertise and trained users.
How often should TOMs be reviewed?
The GDPR does not prescribe one fixed interval for every measure. Reviews should be risk-based and occur regularly, as well as after relevant changes, incidents or new threats.
Must every processor provide its TOMs?
Before appointing a processor, the controller needs sufficient guarantees that appropriate measures are implemented. The processing agreement must address security obligations, and the level of detail and evidence should reflect the risk and the service.
This article provides general information and does not replace legal or security advice for a specific processing operation.