AA-sec
Articles, guides, and technical resources for product teams building continuous security and traceable evidence.
Learn what CRA Article 13 requires when a manufacturer finds a vulnerability in an integrated component, including upstream notification, remediation, fix sharing, and evidence.
Read article
Learn how the CRA connects vulnerability documentation with the cybersecurity risk assessment, when reassessment is needed, and what lifecycle evidence manufacturers should retain.
Read article
Learn who qualifies as an open-source software steward under the CRA, what Article 24 requires, when reporting starts, and what evidence stewards should prepare.
Read article
Learn what the CRA requires products to record and monitor, how to scope security-relevant activity, and what evidence product teams should retain.
Read article
Learn how the CRA treats access control, authentication and identity management, and what product teams should implement and retain as security evidence.
Read article
Learn when CRA remote data processing rules pull cloud backends, APIs and manufacturer-controlled services into a product's cybersecurity scope and evidence model.
Read articlePractical guidance on CRA scope, obligations, timelines, and product readiness.
Learn who qualifies as an open-source software steward under the CRA, what Article 24 requires, when reporting starts, and what evidence stewards should prepare.
Learn when CRA remote data processing rules pull cloud backends, APIs and manufacturer-controlled services into a product's cybersecurity scope and evidence model.
Learn what the CRA requires when a manufacturer ceases operations, who must be informed, how importers and distributors are affected, and what evidence to prepare.
Learn what a CRA authorised representative can do, which manufacturer duties cannot be delegated, what the written mandate must cover, and what evidence must remain available.
A practical CRA distributor checklist covering due care, CE marking and information checks, non-conformity holds, corrective action, vulnerabilities, and authority requests.
A practical CRA importer checklist covering pre-market verification, CE marking, manufacturer evidence, corrective action, authority requests, and role changes.
A release-focused CRA checklist for preparing the EU declaration of conformity, applying CE marking, linking supporting evidence, and retaining the final conformity package.
A practical guide to CRA corrective measures for non-conforming products: when to restore conformity, withdraw supply-chain stock, recall products, and retain evidence.
The CRA does not give all open-source software a blanket exemption. Learn how commercial activity, responsibility and the steward role change the legal analysis.
A practical guide to CRA harmonised standards in 2026, covering M/606 deliverables, Official Journal citation, presumption of conformity, and what manufacturers should track.
A practical guide to choosing the CRA conformity assessment route for default, Class I, Class II and critical products, including Modules A, B+C and H.
A practical guide to CRA product classification: how core functionality separates the default category from important Class I, Class II and critical products.
A practical guide to CRA substantial modification, including software updates, repairs, risk changes, manufacturer obligations, conformity assessment, and release evidence.
A practical guide to CRA support period requirements, including the five-year minimum, longer-lived products, shorter-use exceptions, documentation, and update retention.
A practical guide to deciding whether hardware, software, components and manufacturer-controlled remote processing fall within the Cyber Resilience Act, including common exclusions.
A practical starting point for Cyber Resilience Act readiness, covering product scope, risk assessment, vulnerability handling, evidence, and reporting preparation.
Software bill of materials practices for product visibility and vulnerability response.
CycloneDX and SPDX can both support CRA SBOM workflows. Compare their data models, lifecycle fit, tooling and interoperability before choosing a release format.
A practical CI/CD workflow for generating release-specific SBOMs, validating the result, binding it to the shipped artifact, and retaining evidence for later vulnerability work.
A practical guide to improving SBOM quality through explicit completeness, reliable component identity, dependency accuracy, release binding, validation, and retained evidence.
A practical guide to CRA SBOM requirements, including minimum dependency coverage, machine-readable format, technical documentation, disclosure boundaries, and lifecycle maintenance.
Repeatable vulnerability intake, assessment, remediation, and disclosure workflows.
Learn what CRA Article 13 requires when a manufacturer finds a vulnerability in an integrated component, including upstream notification, remediation, fix sharing, and evidence.
A practical guide to the information manufacturers must publish about fixed vulnerabilities under the CRA and how to build a useful security advisory workflow.
A practical guide for manufacturers building a CRA coordinated vulnerability disclosure policy, covering contact channels, intake, triage, researcher coordination, remediation, publication and evidence.
A practical guide to using VEX for product-specific vulnerability impact decisions, with scoped status, supporting rationale, release traceability, and retained evidence for CRA readiness.
A practical explanation of the CRA severe-incident threshold, the two Article 14 severity tests, reporting deadlines, user communication, and evidence to retain.
A practical guide to building a CRA vulnerability handling process that connects intake, triage, remediation, disclosure, updates, component coordination, and evidence.
A practical guide to CRA security update requirements, covering remediation, secure distribution, automatic updates, user notices, availability, and release evidence.
A practical guide to the CRA definition of an actively exploited vulnerability, the reliable-evidence threshold, awareness timing, and defensible triage records.
A practical preparation guide for the CRA Single Reporting Platform, covering EU Login, assigned representatives, reporting data, evidence, and internal workflow.
A practical explanation of CRA reporting duties for actively exploited vulnerabilities and severe incidents, including deadlines, routing, evidence, and preparation.
Traceable evidence that supports product security decisions and compliance work.
Learn how the CRA connects vulnerability documentation with the cybersecurity risk assessment, when reassessment is needed, and what lifecycle evidence manufacturers should retain.
A practical guide to the production, development and vulnerability-handling evidence manufacturers should retain to show that CRA controls keep working over time.
A practical response playbook for CRA market-surveillance requests: scope the authority’s question, retrieve release-specific evidence, and preserve a defensible response trail.
A practical manufacturer checklist for CRA Annex II user information, covering product identity, vulnerability contacts, support dates, secure-use instructions and release evidence.
A practical CRA readiness checklist for product-security evidence, covering scope, risk assessment, SBOM, testing, vulnerability decisions, releases, user information and retention.
A practical guide to CRA technical documentation, covering Annex VII evidence, risk assessment, vulnerability handling, test reports, retention and lifecycle updates.
Security engineering practices across product design, development, release, and maintenance.
Learn what the CRA requires products to record and monitor, how to scope security-relevant activity, and what evidence product teams should retain.
Learn how the CRA treats access control, authentication and identity management, and what product teams should implement and retain as security evidence.
Learn how CRA availability requirements apply to essential and basic functions, denial-of-service resilience, connected-service impact, testing and release evidence.
Learn how CRA secure-decommissioning requirements connect permanent data removal, reset behavior, user instructions, lifecycle testing and retained product evidence.
The CRA allows unfinished alpha, beta and release-candidate software to be offered for testing under specific conditions. Learn what controls and evidence manufacturers should retain.
A practical guide to designing effective and regular CRA security testing, selecting test depth by risk, and retaining evidence that supports product and vulnerability-handling decisions.
A practical guide to deciding whether a known exploitable vulnerability blocks CRA market placement, with product-specific triage, release-gate evidence, and documented decisions.
A practical guide to CRA third-party component due diligence, covering component selection, integration risk, vulnerability handling, support signals, and retained evidence.
A practical guide to using ENISA's SME cyber-resilience maturity model to identify product-security gaps, prioritise improvements, and avoid treating a maturity score as proof of CRA compliance.
A practical guide to translating CRA secure-by-design and secure-by-default requirements into engineering actions, release evidence, and repeatable product-security checks.
A practical guide to CRA cybersecurity risk assessment, covering product scope, intended and foreseeable use, threats, Annex I mapping, evidence, and reassessment triggers.
Product updates and practical workflows supported by the AA-sec platform.
A practical framework for evaluating CRA compliance software by lifecycle traceability, risk assessment, SBOM, vulnerability evidence, audit history and workflow fit.