Technical and organisational measures in accordance with the GDPR

Technical and organisational measures (TOM) are the safeguards with which controllers and processors protect personal data under Art. 32 GDPR. They include technical means such as encryption, firewalls and access restrictions, as well as organisational arrangements such as internal policies, clear responsibilities and staff training.

For companies in Ukraine without an establishment in the EU that process personal data of individuals in the EU, this raises practical questions: Which measures are considered appropriate? How do you meet your accountability obligations and provide evidence? What belongs in complete TOM documentation, and what role does the risk analysis play? Our consulting services are aimed at small and medium-sized companies from Ukraine without a location in the EU that want to clarify these questions in a structured and comprehensible way.

Server room with a digital padlock icon representing security

Which technical and organisational measures does the GDPR require from companies outside the EU, such as companies in Ukraine?

The GDPR applies to companies without an EU establishment under Art. 3(2) GDPR if they offer goods or services to individuals in the EU or monitor their behaviour in the EU. In that case, Art. 32 GDPR requires them to implement appropriate technical and organisational measures that are suited to the risk for the data subjects. The GDPR takes a risk-based approach: it names no fixed products, and the measures must take into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing.

Technical protection mechanisms include encryption and access controls, organisational processes include binding policies and regular staff training. The risk of data breaches is assessed systematically and the measures are documented. Supervisory authorities can require companies to demonstrate that their safeguards are effective and appropriate. Structured measures and their documentation reduce liability risks and provide clear evidence during official inspections. Recognised standards such as ISO/IEC 27001 can serve as a point of reference for the structure of measures. They are not mandatory under the GDPR, and whether and to what extent they are suitable depends on the individual case.

What the GDPR requires: appropriate technical and organisational measures

Anyone covered by Art. 3(2) GDPR must implement effective technical and organisational measures even without an establishment in the EU. The core aim is a level of protection appropriate to the risk for data security, together with a procedure for regularly testing, assessing and evaluating the effectiveness of the measures taken (Art. 32(1)(d) GDPR). The core requirements include concrete safeguards under Art. 32 GDPR (such as access restrictions and backups), documentation that is comprehensible and regularly reviewed, clearly assigned responsibilities for data protection and data security, a risk analysis with suitable countermeasures, and training and awareness-raising for staff.

The requirements depend on the scope, context and sensitivity of the data processed. Where appropriate TOM are missing, data protection infringements and fines may come into consideration. Under Art. 32(1) GDPR, the obligation to implement suitable TOM applies equally to controllers and processors. Because there is no adequacy decision by the European Commission for Ukraine, engaging a Ukrainian company constitutes a transfer to a third country (Art. 44 GDPR). A data processing agreement under Art. 28(3)(c) GDPR alone is not sufficient for this. Appropriate safeguards in the form of the EU standard contractual clauses (SCCs) must be agreed (Art. 46(2)(c) GDPR). The technical and organisational measures owed under the contract must be specified in detail in Annex II of the SCCs and, where necessary, supplemented by additional safeguards (supplementary measures) in order to ensure a level of protection equivalent to that in the EU.

The EU representative under Art. 27 GDPR is the point of contact for supervisory authorities and data subjects. It does not monitor compliance with data security and data protection requirements; responsibility for the TOM remains with the company. You can find more under EU Representative Duties and Responsibilities.

Questions about your specific case?Request a free initial consultation

How we document your TOM together with you

TOM documentation must reflect the actual technical and organisational day-to-day reality of your business. As part of our consulting, we work with you in four building blocks. The results also feed into the record of processing activities; we cover the connection with the other data protection documents in the GDPR compliance system for Ukrainian companies.

1. Risk analysis

Together with you, we assess your data processing and clarify:

  • Which personal data is processed?
  • Where are the weak points?
  • How high are the risks for data subjects?

The result is the basis for deciding which specific TOM to apply.

2. Technical measures

With you, we record the technical measures you have in place, for example:

  • Encryption of sensitive data in transit and at rest
  • Firewalls and intrusion detection systems
  • Access control through authentication and user rights
  • Regular system and security updates

The documentation describes how and why the measures were selected and which systems are affected.

3. Organisational measures

We also record the organisational measures together with you, for example:

  • Internal data protection policies (e.g. handling of emails, password management)
  • Training and awareness-raising for staff
  • Definition of responsibilities, emergency plans and reporting channels
  • Regular review of processes through audits

Structured process documentation makes procedures traceable for authorities and in the event of a data protection incident.

4. Ongoing review

Technology and the legal position change. We therefore review the TOM with you at regular intervals, adjust them where necessary and record the changes in the TOM directory. Details of the support available are on the page GDPR consulting Ukraine: Compliance packages for the EU market.

Conclusion

Complete TOM documentation meets your legal obligations and shows business partners and supervisory authorities how you protect personal data.

Summary

Companies outside the EU, such as companies in Ukraine, that fall under Art. 3(2) GDPR must implement and document technical and organisational measures. Up-to-date TOM documentation is the basis for effective data security and for evidence towards authorities and business partners. We support you in setting up the TOM in a way that works in practice and in documenting them so that they stand up to review.

Further information

Frequently asked questions (FAQ)

1. What are technical and organisational measures (TOM)?

Technical and organisational measures (TOM) are safeguards that companies must put in place under the GDPR to protect personal data. They include technical measures such as encryption, firewalls and access restrictions, as well as organisational arrangements such as internal policies, assignment of responsibilities and staff training. The aim of the TOM is to ensure an appropriate level of data protection and data security and to act in compliance with the GDPR. Under Art. 32 GDPR, the technical and organisational measures required by the GDPR follow a risk-based approach and take into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing. They must be adapted individually to the size of the company and its risk situation and reviewed regularly.

2. Which technical measures are part of the TOM?

Technical measures within the TOM include encryption technologies, firewalls, access restrictions, two-factor authentication, regular software updates and secure passwords. Securing networks, automatic data backups and the physical protection of server rooms and IT infrastructure are also part of them. These measures protect personal data against unauthorised access, loss and manipulation.

3. Which organisational measures are part of the TOM?

Organisational measures include introducing and implementing internal data protection policies, clearly defining responsibilities, regular training for staff, and monitoring and documenting processes relevant to data protection. The aim of the organisational measures is to secure compliance with data protection requirements in day-to-day business and to ensure processes that comply with the GDPR. Data processing agreements under Art. 28 GDPR and data protection impact assessments under Art. 35 GDPR are separate compliance instruments and not themselves technical or organisational measures within the meaning of Art. 32 GDPR.

4. How do I implement TOM in my company in compliance with the GDPR?

For a GDPR-compliant implementation of TOM, companies should first carry out a risk analysis, define relevant protective measures and implement them according to the specific risk situation. Clear documentation of all measures, regular review of their effectiveness and adaptation to new technical and legal developments are also important. Awareness-raising and training of staff are central to embedding data protection and data security permanently.

5. What documentation obligations apply to the implementation of TOM?

Where possible, a general description of the technical and organisational measures must expressly be included in the record of processing activities: for controllers under Art. 30(1)(g) GDPR, for processors under Art. 30(2)(d) GDPR. The record must be kept in writing or electronically and made available to the supervisory authority on request (Art. 30(3) and (4) GDPR). In addition, the controller must be able to demonstrate that its measures are appropriate to the risk and that the processing complies with the GDPR (Art. 5(2), Art. 24(1) and Art. 32(1) GDPR). A processor must make available to its client the information necessary for this (Art. 28(3)(h) GDPR). The law prescribes no particular form for this evidence. In practice, however, it can only be provided with documentation that records the risk assessment, the measures chosen, responsibilities and the regular review under Art. 32(1)(d) GDPR in a comprehensible way.

6. What is the proportionality principle for TOM?

The proportionality principle means that the scope and intensity of the technical and organisational measures must be adapted to the nature, scope, circumstances and purposes of the data processing and to the risk to the rights of the data subjects. Companies must choose measures that protect personal data adequately and at an economically justifiable cost. Excessive or insufficient measures should be avoided in order to achieve efficient, risk-oriented data security.

7. How is a risk analysis carried out to select suitable TOM?

The risk analysis assesses possible dangers and risks in the processing of personal data. Companies should analyse which data is processed, how sensitive it is and which potential threats exist. On this basis, appropriate technical and organisational measures are selected to reduce the risks identified. The risk analysis should be repeated regularly, in particular when processing or business operations change.

8. Who is responsible for implementing and monitoring the TOM?

Company management coordinates and is responsible for implementing the TOM. A data protection officer advises on and monitors compliance with the GDPR (Art. 39(1) GDPR). The individual departments should also be involved in the implementation so that data security is ensured throughout the company. Management is accountable to the supervisory authorities and must ensure that the data protection measures are properly implemented. Within the company, management steers the security measures while the departments implement them operationally. A data protection officer advises and reviews independently, where there is an obligation to designate one under Art. 37 GDPR.

9. What are the consequences of infringing the requirements on technical and organisational measures?

Where technical and organisational measures are inadequate, the law does provide a corresponding range of fines (Art. 83(4) GDPR). Supervisory authorities, however, always decide in the individual case and are bound by the principle of proportionality (Art. 83(1) and (2) GDPR). The primary aim of documentation is therefore not to avoid theoretical maximum penalties, but to show in a structured way that the company meets its responsibility and has established an appropriate level of protection in a solution-oriented manner.

10. What are examples of technical and organisational measures?

Examples of technical measures are data encryption, firewalls, access controls, antivirus programs and secure Wi-Fi networks. Organisational measures include defining clear access rights, data protection training, emergency and deletion concepts, and regular audits of the existing measures. Together, these measures help to meet GDPR requirements in the company on a lasting basis and to ensure a high level of data protection.

11. Are certifications such as ISO/IEC 27001 or SOC 2 recognised as evidence of TOM?

Not as legally conclusive evidence. ISO/IEC 27001 and SOC 2 are not officially approved GDPR certification mechanisms. They are therefore not legally regarded as blanket evidence of sufficient guarantees within the meaning of Art. 28(5) GDPR. In practice, however, such certificates are a strong indication of an appropriate level of protection under Art. 32 GDPR. The EU client must still review the specific technical and organisational measures (TOM) and agree them in a binding contract.

12. Must Ukrainian processors allow on-site inspections of their TOM?

Yes. Under Art. 28(3)(h) GDPR, the data processing agreement must provide that the service provider allows for and contributes to audits, expressly including inspections (on-site checks), conducted by the client or an auditor mandated by the client. This statutory obligation to tolerate audits applies regardless of whether the service provider is based in the EU or in a third country such as Ukraine.

13. What additional technical safeguards do EU clients require for data transfers to Ukraine?

Since there is no EU adequacy decision for Ukraine, data transfers are generally based on standard contractual clauses (SCCs) for third countries (Art. 46(2)(c) GDPR). If the transfer impact assessment (TIA), which must be carried out, shows a risk of access to the data by public authorities, additional safeguards (supplementary measures) must be taken. In such cases, EU clients ask above all for strong end-to-end encryption or pseudonymisation, with key management remaining exclusively in the EU. This ensures technically that no access to plaintext data is possible in the third country.

Still have questions?

In a short introductory call in German, English or Ukrainian, we clarify which requirements apply to your company.

Request a free initial consultation

Scroll to Top