Frameworks

One engine. Any framework you can put in a catalog.

PolicyLenz does not contain five hard-coded assessments. It contains one assessment engine and five catalogs of structured content. That distinction is the whole story of this page: frameworks are data, so the engine can adapt to almost any cybersecurity framework you need.
CatalogFunctionsCategoriesControlsISO/IEC 27001F1F2F3F4Same structure. Different labels.93 Annex A controls
§ 01Why it adapts

Frameworks are content, not code.

  1. 01

    Frameworks are structured catalogs

    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.

  2. 02

    New frameworks arrive as content

    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.

  3. 03

    Every catalog is versioned forever

    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.

§ 02Shipped today

Five very different regimes, one engine.

The five catalogs in the box were chosen to prove generality: a certification standard, an attestation framework, a privacy regulation, a voluntary framework, and a financial-sector resilience regulation. They differ in shape, language, and legal weight, and the engine treats them identically: 358 controls, enumerated completely, every run.
Certification standard01

ISO/IEC 27001:2022

93Annex A controls

93 Annex A controls across 4 themes. Certification scope profiles let the score match the engagement: the denominator is what you actually committed to.

Attestation framework02

SOC 2

61criteria

61 criteria across all five Trust Services Categories, not just Security. Select the categories in scope and the rest leave the report entirely.

Privacy regulation03

GDPR

36obligations

36 obligations across 4 areas, expressed as assessable controls. Proof that the engine handles law-shaped requirements, not only control-shaped ones.

Voluntary framework04

NIST CSF 2.0

106subcategories

106 subcategories across 6 functions, shipped as verbatim official text. The reference case for what a fully licensed catalog looks like in PolicyLenz.

Financial-sector regulation05

DORA

62requirements

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.

§ 03Bring your own

If it is a list of controls, PolicyLenz can assess against it.

Sector regulations, national schemes, benchmark catalogs, or the internal control baseline your organization already runs on: if the framework can be expressed as a structured catalog of enumerable controls, the engine can scope it, score it, and audit-trail it like the five in the box.
  • NIS2Candidate
  • PCI DSSCandidate
  • HIPAACandidate
  • CIS ControlsCandidate
  • ISO/IEC 27701Candidate
  • ISO/IEC 42001Candidate
  • CMMCCandidate
  • BSI IT-GrundschutzCandidate
  • Your internal control baseline
  1. 01

    Author

    The framework is expressed as a structured catalog: every control enumerated, hierarchy mapped, wording sourced or paraphrased depending on licensing.

  2. 02

    Validate

    The catalog passes the same completeness checks as the shipped five: every control assessable, one result per control guaranteed, ids stable.

  3. 03

    Deliver

    The catalog ships to your deployment as a signed content bundle. From that moment it scopes, scores, crosswalks, and exports like any other framework.

Design partner program

Need a framework we have not shipped?

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.

§ 04Crosswalks

Frameworks that know about each other.

408 curated mappings connect related controls across the shipped frameworks, so an ISO gap can show you the SOC 2 coverage you already have, a DORA requirement can point at the NIST subcategory that already covers it, and a GDPR scope can seed an ISO one. Crosswalks are deliberately report-only: a mapping surfaces a connection and a human decides what it means. It never changes a verdict and never moves a score.
ISO/IEC 27001 · 93SOC 2 · 61GDPR · 36NIST CSF 2.0 · 106DORA · 62408Report-only mappings

Fig. 5  Schematic. Arc sizes and the mapping count for each pair are real; chord positions are illustrative.

Next step

Which framework do you need?

Ask about it on the demo call and get a straight answer about what onboarding it takes.