Skip to content

docs(compliance): CRA Annex I Part I requirements and the release assessed - #16320

Draft
devGregA wants to merge 1 commit into
devfrom
docs/cra-annex-i-part-i
Draft

devGregA wants to merge 1 commit into
devfrom
docs/cra-annex-i-part-i

Conversation

@devGregA

Copy link
Copy Markdown
Contributor

Description

Documents the EU CRA Annex I Part I requirements in the CRA and DORA Evidence Packs page (docs/content/federal_compliance/eu_evidence_packs.md, English only; the page has no translations).

  • The CRA catalog now includes the 13 Annex I Part I product security requirements (PI-1, PI-2(a) to PI-2(m)). New CRA assessments include them, and existing CRA assessments pick them up on their next recompute.
  • How an assessor records applicability: Not Applicable with the justification (the reason field is labeled "Why This Requirement Does Not Apply"), or a state plus an implementation narrative, which is required before a Part I requirement can be set to Satisfied or Partially Satisfied by hand, plus supporting files.
  • What automation does: PI-2(a) checks open and risk-accepted findings flagged as known exploited (CISA KEV); the ten CWE-mapped requirements can only flag gaps and are never marked met; findings without a CWE are counted for coverage. The CWE sets are listed.
  • The new "Release Assessed" field, how to set and edit it, and where it appears in the evidence pack (workbook Cover and the OSCAL result).
  • Two troubleshooting rows, and the start-dialog text updated for the release field.

The Pro change is a private PR; merge the two together.

🤖 Generated with Claude Code

…essed

Describe the Annex I Part I requirements now in the CRA catalog: how an
assessor records applicability, the narrative required before a requirement is
marked met, what PI-2(a) checks, the CWE sets that can only flag gaps, and the
Release Assessed field and where it appears in the evidence pack.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devGregA devGregA added this to the 3.4.200 milestone Oct 13, 2026
@github-actions github-actions Bot added the docs label Oct 13, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant