Regulatory · European Union

EU Cyber Resilience Act and NIS2

Attestkeep maps what your cluster's admission control and image scanning recorded in a period to 34 clauses of Regulation (EU) 2024/2847 and Directive (EU) 2022/2555. 26 are assessed from those records; 8 are marked outside scope, each with the reason.

What the framework asks

26 clauses a cluster can answer.

Citations and titles as the report prints them. Open a clause to read what it asks, restated close to the instrument's own words.

Cyber Resilience Act

Regulation (EU) 2024/2847

Annex I Part I (essential cybersecurity requirements) and Part II (vulnerability handling requirements)

NIS2 Directive

Directive (EU) 2022/2555

Article 21(2) cybersecurity risk-management measures

CitationClauseReport sections
Annex I, Part I (1)
Appropriate level of cybersecurity based on the risks

Products shall be designed, developed and produced in such a way that they ensure an appropriate level of cybersecurity based on the risks.

Control statementAdmission decisions
Annex I, Part I (2)
Made available without known exploitable vulnerabilities

Products with digital elements shall be made available on the market without known exploitable vulnerabilities.

CoverageAdmission decisionsOutcomes
Annex I, Part I (3)(a)
Secure by default configuration

Products shall be made available with a secure by default configuration, including the possibility to reset the product to its original state.

Control statementAdmission decisions
Annex I, Part I (3)(b)
Vulnerabilities can be addressed through security updates

Products shall ensure that vulnerabilities can be addressed through security updates, including, where applicable, automatic updates.

Control statementCoverage
Annex I, Part I (3)(c)
Protection from unauthorised access

Products shall ensure protection from unauthorised access by appropriate control mechanisms, including but not limited to authentication, identity or access management systems.

Control statementEvidence chain
Annex I, Part I (3)(d)
Confidentiality of stored, transmitted or processed data

Products shall protect the confidentiality of stored, transmitted or otherwise processed data, personal or other, such as by encrypting relevant data at rest or in transit by state of the art mechanisms.

Control statement
Annex I, Part I (3)(e)
Integrity of data, commands, programs and configuration

Products shall protect the integrity of stored, transmitted or otherwise processed data, commands, programs and configuration against any manipulation or modification not authorised by the user, and report on corruptions.

Supply chain
Annex I, Part I (3)(g)
Availability of essential and basic functions

Products shall protect the availability of essential and basic functions, also after an incident, including through resilience and mitigation measures against denial-of-service attacks.

Availability
Annex I, Part I (3)(h)
Minimise negative impact on other devices or networks

Products shall minimise their own negative impact on the availability of services provided by other devices or networks.

Control statement
Annex I, Part I (3)(i)
Limit attack surfaces

Products shall be designed, developed and produced to limit attack surfaces, including external interfaces.

Control statement
Annex I, Part I (3)(j)
Reduce the impact of an incident

Products shall be designed, developed and produced to reduce the impact of an incident using appropriate exploitation mitigation mechanisms and techniques.

Control statement
Annex I, Part I (3)(k)
Security-related information by recording and monitoring

Products shall provide security related information by recording and monitoring relevant internal activity, including the access to or modification of data, services or functions.

Evidence chainAdmission decisions
Annex I, Part II (1)
Identify and document vulnerabilities and components (SBOM)

Manufacturers shall identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the product.

CoverageSupply chain
Annex I, Part II (2)
Address and remediate vulnerabilities without delay

Manufacturers shall address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, new security updates shall be provided separately from functionality updates.

Control statementTriage decisions
Annex I, Part II (3)
Effective and regular tests and reviews

Manufacturers shall apply effective and regular tests and reviews of the security of the product with digital elements.

Coverage
Annex I, Part II (5)
Coordinated vulnerability disclosure policy

Manufacturers shall put in place and enforce a policy on coordinated vulnerability disclosure.

Organisation
Annex I, Part II (6)
Facilitate sharing of information about potential vulnerabilities

Manufacturers shall take measures to facilitate the sharing of information about potential vulnerabilities in their product as well as in third party components contained in that product, including by providing a contact address.

Organisation
Annex I, Part II (7)
Secure distribution of updates

Manufacturers shall provide for mechanisms to securely distribute updates to ensure that vulnerabilities are fixed or mitigated in a timely manner.

Control statement
Article 21(2)(a)
Policies on risk analysis and information system security

Measures shall include policies on risk analysis and information system security.

Control statement
Article 21(2)(b)
Incident handling

Measures shall include incident handling.

Admission decisionsBreak-glass events
Article 21(2)(d)
Supply chain security

Measures shall include supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers.

Supply chainControl statement
Article 21(2)(e)
Security in acquisition, development and maintenance, including vulnerability handling

Measures shall include security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure.

CoverageAdmission decisionsTriage decisions
Article 21(2)(f)
Assessing the effectiveness of the measures

Measures shall include policies and procedures to assess the effectiveness of cybersecurity risk-management measures.

Admission decisionsAvailability
Article 21(2)(h)
Policies on the use of cryptography and encryption

Measures shall include policies and procedures regarding the use of cryptography and, where appropriate, encryption.

Supply chainControl statement
Article 21(2)(i)
Human resources security, access control policies and asset management

Measures shall include human resources security, access control policies and asset management.

OutcomesEvidence chain
Article 21(2)(j)
Multi-factor authentication and secured communications

Measures shall include the use of multi-factor or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems within the entity.

Evidence chain
8 clauses marked outside scope, and why
CitationClause and reason
Annex I, Part I (3)(f) Data minimisation

what data a workload processes is a property of that workload's code, which admission control does not read. For this operator's own processing: query statements are recorded for tracing and their arguments never are, and no image layer content is stored.

Annex I, Part I (3)(l) Secure and permanent removal of data and settings

data retention and deletion in a workload is a property of that workload and its storage, which admission control does not reach.

Annex I, Part II (4) Publicly disclose information about fixed vulnerabilities

publication is an act of the manufacturer's release process. The per-image finding history recorded here is the input a disclosure note would be written from, not the disclosure.

Annex I, Part II (8) Disseminate security patches without delay

dissemination is an act of the manufacturer's release process. This cluster records when a fixed image arrived, not when it was published.

Article 14 Reporting actively exploited vulnerabilities and severe incidents

notifying a CSIRT and ENISA is an organisational act with a legal deadline. What this document supplies is the moment the clock starts: every finding carries the timestamp at which this cluster first became aware of it, in the chain section.

Article 21(2)(c) Business continuity, backup management and crisis management

backup, recovery and crisis management are platform and organisational programmes. The availability section of this document records only the availability of this control itself, which is one input and not the measure.

Article 21(2)(g) Basic cyber hygiene practices and cybersecurity training

training and awareness are organisational programmes; no cluster control observes them.

Article 23 Incident reporting to the CSIRT or competent authority

reporting to a national CSIRT is an organisational act with a legal deadline. What this document supplies is the moment of awareness each deadline is measured from: every refusal, finding and break-glass activation carries its own timestamp in the chain section.

What Attestkeep produces

Evidence from records the cluster already keeps.

Nothing is filled in by hand. Each clause's answer carries a status (met, partial, gap or outside scope), a note with the period's own numbers, and the report sections those numbers come from.

Each EU CRA and NIS2 clause is assessed by a rule of its own, written for that clause, against the report sections below.

The package

What the report contains.

Every package carries the same sections, whatever the framework. The ones marked are those EU CRA and NIS2 answers cite, with the number of clauses citing each.

More on the package

  1. Organisation2
  2. Framework mapping
  3. Cluster
  4. Control statement13
  5. Coverage5
  6. Vulnerability findings
  7. Outcomes2
  8. Admission decisions7
  9. Supply chain4
  10. Triage decisions2
  11. Break-glass events1
  12. Availability2
  13. Evidence chain4
  14. Deployment context
  15. Issues
  16. Ledger
  17. Population
  18. Runtime events
  19. Producer statements (VEX)
Scope

The scope paragraph, as the report states it.

This document reports what one Kubernetes cluster's admission control and image scanning recorded during the period, mapped onto two instruments that bind different subjects. NIS2 Article 21(2) binds the entity, and these records are evidence for the subset of its measures that concern container workloads. The Cyber Resilience Act binds the manufacturer of a product with digital elements; the mapping below is usable where the container images covered here are that product or part of it, and is not usable as a statement about products this cluster merely runs. Neither mapping is a conformity assessment. No clause is marked met because a feature exists — only because the period's own records show the control operating. Clauses marked outside_scope are duties no cluster control can discharge; they are listed rather than omitted so the reader can see exactly where this document stops.

Questions

About EU CRA and NIS2 and Attestkeep

Is this a EU CRA and NIS2 certification?

No. The package is evidence produced from your cluster's own records. It is not a certification, and no auditor is obliged to accept it. The scope paragraph on this page is the one the report itself carries.

Why are 8 of the clauses outside scope?

They ask about things one cluster's admission and scanning records cannot show. They are listed with the reason rather than left out, so whoever reads the report can see the gap is deliberate.

Which plan includes EU CRA and NIS2?

Every plan can report against it. Community and Team include one framework of your choice, Business three, Enterprise every one. Prices are on the pricing page.

How does an auditor check the package?

In a browser at attestkeep.com/verify.html, where nothing is uploaded, or with the short script on the documentation site. Neither needs us. For auditors has the details.

Install it yourself.

Create an account, confirm your e-mail with the code we send, take the free Community key from the Licenses page, and install with Helm.

Create an account