ISO/IEC 27001:2022
93 Annex A controls across 4 themes. Certification scope profiles let the score match the engagement: the denominator is what you actually committed to.
Every framework in PolicyLenz is a catalog of enumerated controls in a common three-level structure: functions, categories, and controls. Only the labels differ between regimes. The engine iterates whatever catalog it is given; it has no idea which acronym it is scoring, and it does not need one.
Catalogs ship through the signed update pipeline: Ed25519-verified bundles, hash-checked files, atomic install, one-click rollback. Adding a framework is a data delivery, not a software release. Your deployment stays sealed and your code stays untouched.
Runs record the exact framework version they assessed. Update a catalog and history stays exactly as it was; scope profiles, crosswalks, and exports all carry the version with them. A framework can evolve without ever rewriting your past.
93 Annex A controls across 4 themes. Certification scope profiles let the score match the engagement: the denominator is what you actually committed to.
61 criteria across all five Trust Services Categories, not just Security. Select the categories in scope and the rest leave the report entirely.
36 obligations across 4 areas, expressed as assessable controls. Proof that the engine handles law-shaped requirements, not only control-shaped ones.
106 subcategories across 6 functions, shipped as verbatim official text. The reference case for what a fully licensed catalog looks like in PolicyLenz.
62 requirements across the 5 DORA pillars: ICT risk management, incident reporting, resilience testing, third-party risk and information sharing. Built for financial entities and the ICT providers that serve them.
Catalog wording is disclosed honestly: NIST is verbatim, the other three are complete-coverage paraphrases with a verbatim overlay path for licensed deployers.Details on the Security & Trust page.
The framework is expressed as a structured catalog: every control enumerated, hierarchy mapped, wording sourced or paraphrased depending on licensing.
The catalog passes the same completeness checks as the shipped five: every control assessable, one result per control guaranteed, ids stable.
The catalog ships to your deployment as a signed content bundle. From that moment it scopes, scores, crosswalks, and exports like any other framework.
Custom framework onboarding is exactly the kind of work our design partner program exists for. Tell us which regime you need on the demo call, and we will tell you honestly what authoring it takes.
Fig. 5 Schematic. Arc sizes and the mapping count for each pair are real; chord positions are illustrative.
Ask about it on the demo call and get a straight answer about what onboarding it takes.