Skip to content
CTG GmbH
Scales on a law book representing regulation

Regulation: understand requirements and implement them in practice

Legal requirements influence how an organisation provides services, handles information and assigns responsibility. The first question is which rules actually apply. A collection of legislation titles alone does not answer it.

Connect regulation with the business model: what services are offered, to whom and in what role? A manufacturer of a digital product can have different duties from its distributor or an organisation that merely uses it.

Why accurate classification matters

An unclear assessment can cause important duties to be missed or unnecessary work to be undertaken. Organisations need a traceable connection between the rule, their own activities and implementation. Customer requirements should also be examined to distinguish statutory obligations from contractual ones.

The type of legal instrument matters. European Union (EU) regulations are binding legal acts; directives set objectives that Member States implement through national law. For a directive, the relevant national implementation must therefore be examined as well. The EU explains the distinction.

What we examine

The focus is the material and territorial scope, the organisation’s role and when and to what extent duties apply. Depending on the instrument, sector, company size, product type or relationships with other organisations may matter. These criteria must be checked individually rather than inferred from a familiar headline.

Next, requirements become tasks. Who must decide? What records are needed? Who tracks the deadline? Deputies, reporting routes and cooperation with suppliers matter too. An abstract obligation becomes a process that a responsible employee can understand and carry out.

Particularly relevant frameworks

Germany’s legislation implementing the second Network and Information Security Directive (NIS2) entered into force on 6 December 2025. Section 28 of the German BSI Act (BSIG) sets out criteria for essential and important entities. Whether an organisation falls within them depends on its actual circumstances. German government, BSIG, section 28.

The Digital Operational Resilience Act (DORA) has applied since 17 January 2025 to the digital resilience of the financial entities it covers. Dependencies on information technology (IT) suppliers also matter. A project must establish its own role and links to the financial sector. European Securities and Markets Authority: DORA

The Cyber Resilience Act (CRA) has different application dates. Since 11 September 2026, manufacturers of covered products with digital elements have had certain reporting duties for actively exploited vulnerabilities and severe security incidents. Most other requirements apply from 11 December 2027. Reporting duties already in force must be distinguished from later product requirements. Reporting, implementation.

The EU Artificial Intelligence Act also has staged application. The European Commission’s current timetable lists 2 December 2027 for certain high-risk applications and 2 August 2028 for corresponding systems embedded in regulated products. Other provisions already apply. Assess the actual use, organisational role and relevant provision together. Commission timetable

Classification must remain connected with the business model. Personal data requirements are also examined under privacy and data protection. Several instruments may affect the same project from different perspectives.

Turning a requirement into operational work

Consider a business supplying a connected application under its own name to a financial-sector customer. Record its product role, any direct security obligations and the customer’s requirements separately. This reveals which tasks overlap and where distinct evidence or reporting routes are required.

A useful starting point is an inventory of affected activities and roles. Assign an owner, deadline and expected evidence to each relevant requirement. Changes to products, services or legislation trigger reassessment. Classification then becomes an ongoing task with clear responsibility.

Our other regulatory topics address specific starting questions. Standards and security explain the connection to practical implementation.

Information date: 6 November 2026.

Knowledge and practice overview

Related knowledge and practice

One practical area is applications created within business departments and later used in daily operations. Grassroot IT on compliance for departmental applications explains how to carry the relevant requirements through an application’s lifecycle.