Articles

EU AI Act and CRA: how much groundwork does a good ISMS provide?

How an effective ISMS supports EU AI Act and CRA implementation, and how to distinguish reusable processes from additional work.

New regulatory requirements prompt a practical question: must we start again, or can we build on our existing information security work?

At SITsolutions, we are exploring how the EU AI Act and Cyber Resilience Act (CRA) can be connected to an existing ISO/IEC 27001 information security management system. This includes asking how much of the work a well-designed ISMS that is used in practice has already completed.

Existing structures provide valuable groundwork. The benefit depends on the ISMS scope, its effectiveness and the products and AI applications involved. A reliable general percentage cannot currently be inferred.

A good ISMS makes implementation easier. An ISO 27001 certificate alone does not demonstrate CRA or AI Act conformity.

The CRA concerns cybersecurity of products with digital elements. The AI Act distinguishes between roles, applications and risks. Organisations must establish which obligations actually apply. A software manufacturer faces different tasks from a business using a third-party AI application internally. European Commission: CRA, European Commission: AI Act.

What an ISMS already provides

An effective ISMS establishes responsibilities, repeatable processes and verifiable evidence. These foundations can support further requirements:

  • Recording requirements: incorporate new obligations into existing identification and assessment of legal requirements.
  • Managing risks: inventories, risk assessments and action plans provide a starting point for product and AI assessments.
  • Assigning responsibility: existing roles, approvals and escalation routes help allocate new tasks.
  • Implementing security: access, supplier, change, secure development and vulnerability processes may be reusable where suitable for the product or AI system.
  • Demonstrating effectiveness: documentation, training, internal audits and management reviews support sustained implementation.

Actual scope is crucial. An ISMS covering internal IT does not automatically cover development and support of software sold to customers. Documented processes must also be checked and, where needed, extended for new use cases.

The CRA still requires product-specific work

Although closely related to information security, the CRA requires more than a securely operated business site to demonstrate product security. Product classification, product security assessments, technical evidence and support over the declared support period need attention alongside management processes.

Depending on the applicable obligations, this includes secure product characteristics, vulnerability and component handling, a software bill of materials (SBOM), security updates, technical documentation, conformity assessment and CE marking. Existing development or incident processes can help, but the required results must exist for each product. European Commission: CRA requirements and implementation.

The AI Act goes beyond information security

Secure data processing and protection against tampering are important overlaps. The AI Act also addresses impacts on people, safety and fundamental rights. High-risk AI requirements include data quality, human oversight, technical documentation, accuracy and robustness. Duties depend on role and classification. These tasks can be organised alongside the ISMS but require additional specialist assessments. European Commission: the AI Act’s risk-based approach.

An existing risk register can include AI risks. However, a conventional information security assessment alone cannot determine whether an AI system unfairly disadvantages people or whether a decision receives sufficient oversight.

What percentage of the work is already done?

Three questions must be kept separate: which processes exist, which specific obligations are demonstrably fulfilled, and how much additional effort is avoided?

Consider a purely illustrative calculation, not a measured result. A defined use case is estimated to require 100 person-days without reusable work. If applicable ISMS outputs demonstrably account for 30 person-days, 70 remain. If adapting that work needs a further ten person-days, the remaining effort is 80 person-days: a net saving of 20 per cent.

This does not mean “20 per cent legally compliant”, nor is it transferable to other organisations. Substantial product testing or AI assessment work may remain even where many processes already exist.

For a reliable organisation-specific estimate, we map each applicable requirement to existing evidence, a remaining gap, an owner and estimated outstanding effort. CRA and AI Act obligations are assessed separately. Only then does a percentage become meaningful.

What is already relevant in September 2026?

CRA duties to report actively exploited vulnerabilities and severe incidents have applied to affected manufacturers since 11 September 2026. They include an early warning within 24 hours and notification within 72 hours of becoming aware, followed by further reports. The main requirements apply from 11 December 2027. Existing incident processes should therefore be checked against the specific channels and deadlines. CRA reporting, CRA application dates.

Some AI Act provisions already apply, including prohibited practices and, generally from 2 August 2026, transparency rules, subject to transitional provisions. According to the Commission timetable referenced in this article, high-risk rules for Annex III systems apply from 2 December 2027, and for covered product-related Annex I systems from 2 August 2028. This timetable incorporates AI Omnibus changes. EU AI Act implementation timetable.

Our approach at SITsolutions

We aim to reuse sound existing work and identify the remaining tasks precisely. The ISMS can bring together requirements, risks, responsibilities and evidence. Product management, development and the relevant departments must provide specialist outputs; management must clarify ownership and resources.

The key distinction is: What is already reliably in place, what needs adapting, and what additional work is required? This turns a general percentage question into a transparent implementation plan.

As at 27 September 2026. The effort assessment is professional judgement; the calculation is illustrative, not a research finding.

← Latest articles