← Back to catalogue
Published

Risk and compliance landscape

EM-LND-15 · em-lnd-15

Links between requirements, risks, controls, assessments and findings over an explicit perimeter.

Enterprise profiles Enterprise landscape EnterpriseLND

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 8 questions

Perimeter and requirements Which requirements apply to which part of the organisation.

Applicability

Requirements matched to an explicit perimeter.

Requirement applicability

Whether and where each requirement applies.

  1. Which requirements apply to this perimeter, and on what basis?
  2. Which requirements have no recorded applicability?

Coverage

Requirements and risks linked to controls.

  1. Which requirements or risks have no control linked to them?
  2. Does a linked control show coverage only, or tested effectiveness?
Assurance Evidence, findings and exceptions over time.

Evidence and findings

Assertions backed by evidence and their current validity.

Evidenced assertion

Each claim of compliance with its evidence.

  1. What evidence supports this assertion of compliance?
  2. Has this control actually been executed in the period?

Expiry

Exceptions and conclusions that lapse.

  1. Which exceptions have expired or are about to expire?
  2. Which conclusions no longer apply after a change?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise landscape
Entry kind
landscape
Domain
EnterpriseLND
Industry
Cross-industry
Tags
EM-LND-15W2landscapeRiskLandscapeAssuranceCoverageView

What it is Filled

Links between requirements, risks, controls, assessments and findings over an explicit perimeter.

Why it exists Filled

Links between requirements, risks, controls, assessments and findings over an explicit perimeter.

Distinguishing features Filled

  • Coverage shows that a control is linked; it does not show that the organisation complies.
  • Every assertion of compliance points to evidence.
  • Exceptions keep their expiry date and lapse when it passes.
  • Distinct from the risk and audit contours; this view maps coverage across them.

What robots and AI may and may not do Filled

Must not

  • Treat 100 percent completed records as proof of full compliance.
  • Record an assertion of compliance without evidence.
  • Extend an expired exception without an approval.
  • Present the map as an audit opinion.

Only with a human decision

  • Granting or extending an exception.
  • Accepting residual risk where coverage is missing.
  • Signing a statement of compliance.

May

  • Show requirements without applicability and controls without execution.
  • Flag expired exceptions and conclusions that no longer apply.
  • Summarise coverage per perimeter with evidence links.

Moral aspects Filled

  • False assurance can expose customers, staff and the public to harms the controls were meant to prevent.
  • Accountability for compliance decisions must stay with named people.

Who is affected

  • Customers and data subjects
  • Compliance and risk teams
  • Regulators and auditors

Owners Filled

Steward

The curator of the meta-model catalogue who decides which landscape views are assembled and from which sources.

Master systems

  • Model registry
  • Source manifest
  • Version lock file
  • Policy repository

Links to other meta-models Filled

references

  • WM-XCT-027 - conceptual-candidate
  • WM-KNW-015 - conceptual-candidate
  • WM-ACT-033 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by a coverage view identifier, perimeter and as-of date.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A map linking requirements, risks, controls, assessments and findings for a perimeter.
  • Often confused with a compliance checklist or a risk register.

Capabilities and actions required Filled

  • Coverage gaps and lapsed exceptions can be listed automatically.
  • Assertions can be traced to their evidence.

Hazards and failure modes required Filled

  • False assurance from document counts instead of tested controls.
  • Expired exceptions silently treated as valid.

Standards and interfaces required Filled

  • ISO 31000 for risk management principles and process.
  • ISO/IEC 27001 for information security management controls.
  • NIST OSCAL for machine-readable control catalogues and assessment results.

Context of use required Filled

  • Used in compliance programmes, internal audit planning and regulatory reporting.
  • Relevant for organisations under several overlapping standards or regulations.

Sources Filled

  1. Vercy composition and whole-object: a separate landscape object and delegation
  2. ArchiMate/ISO 42010: views, questions and representation rules
  3. Compare participant subject models and the practical assembly of a permitted context
  4. Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
  5. NIST Open Security Controls Assessment Language - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • Where is coverage by a requirement or a control missing?
  • How to distinguish having a document from being effective?
  • Which conclusions are no longer applicable?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-lnd-15/brief.json, ver-cy/world-models/card-supplements/em-lnd-15.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.