Business & Policy
Current and emerging legislation
Product-security, resilience, safety and sector rules increasingly place lifecycle obligations on manufacturers and service providers.
Why it matters
Teams need a maintained obligations register that translates applicable law into engineering, evidence, disclosure, update and governance requirements.
In brief
Product-security, resilience, safety and sector rules increasingly place lifecycle obligations on manufacturers and service providers. CHERI may help meet technical risk-reduction goals, but obligations attach to the product and organisation rather than to a single processor feature.
Key considerations
1. Applicability
Map jurisdictions, product categories, customer types and effective dates with qualified legal advice.
2. Control mapping
Connect each obligation to secure development, vulnerability handling, update support, assurance and supplier controls; record where CHERI contributes.
3. Evidence
Retain architecture decisions, threat models, test results, software inventories and lifecycle commitments in a form that survives audit and product change.
Evidence and caveats
Legislation changes, guidance evolves and legal interpretation depends on facts. This page is not legal advice; verify the current text and obtain specialist counsel.
Show assumptions, ranges, dates and owners for economic or policy claims. Recheck legislation, guidance, product status and prices at the decision date.