Zero Trust Engineering — Enterprise risk and threat-model integration

archimatev1

/01 Views

Capability definition and hierarchyarchimate
Operational activity sequencearchimate
Exception and recovery activity sequencearchimate
Conformant decision brancharchimate
Denied, conditional or degraded brancharchimate
Identity-scoped information exchangec4
Context and decision inputarchimate
Policy authority and evaluationsecurity
Decision distribution and resource mediationsecurity
Enforcement decision evidencesecurity
Policy ownershiparchimate
Security control and protected resourcesecurity
Control and failure risksecurity
Conformance obligationarchimate
Capability assurancearchimate
Resource trust boundarysecurity
Activity-to-capability realizationarchimate
Logical service capability realizationarchimate
Independent authorization and accountabilityarchimate
Exception expirationarchimate
Governed risk authorityarchimate

/02 About

Governance and assurance engineering reference for enterprise risk and threat-model integration, including policy, logical interfaces, recovery and assurance.

Purpose: Enterprise risk and threat-model integration. Domain: Governance and assurance. Family: governance. Scenario trigger: Evaluate threat scenario affecting Zero Trust resource. Input assurance: Threat actor capability, asset exposure and policy boundaries. Evaluation: Analyze attack path likelihood, impact and mitigating controls. Governing policy: Enterprise threat modeling, risk scoring and treatment policy. Resource-side obligation: Bind actionable risk treatment to specific security controls. Protected concern: Enterprise threat and risk register. Logical interface: Threat actor attack precondition asset impact control and acceptance. Evidence: Threat scenario affected control assurance and residual risk. Failure: Control gap underestimated or risk acceptance unowned. Required recovery: Escalate design remediation and authorize explicit residual risk. Architectural invariant: Security controls must mitigate documented threat paths, not generic labels Adoption: replace reference roles with concrete owner-controlled services. Specify exact provider/consumer identities, schema fields and classifications, signal provenance and freshness, idempotency, authorization lifetime, timeout/retry limits, observation and tamper evidence. A denied or failed operation must not silently become a permitted one. Scope: original vendor-neutral, implementation-agnostic technical reference model. Illustrative logical components and behaviors are neither a deployed system nor evidence of regulatory compliance. Package identities remain stable within the package; cross-package semantic reconciliation requires separate explicit registry support.

Curated · other · unspecified · Published by Lattix · 29 elements · 34 relationships · validated on publish

/03 Contents

Capability
Governance and assurance, Enterprise risk and threat-model integration
Role
Governance and assurance owner, Independent risk or control reviewer
Business Actor
Accountable enterprise stakeholder
Activity
Evaluate threat scenario affecting Zero Trust resource, Verify: Threat actor capability, asset exposure and policy boundaries, Assess: Analyze attack path likelihood, impact and mitigating controls, Execute: Bind actionable risk treatment to specific security controls, Exception: Control gap underestimated or risk acceptance unowned, Recover: Escalate design remediation and authorize explicit residual risk, Independently approve or reject proposal, Expire and reconcile exceptions
Application Component
Threat actor capability, asset exposure and policy boundaries, Analyze attack path likelihood, impact and mitigating controls, Bind actionable risk treatment to specific security controls
Application
Enterprise threat and risk register
Policy
Enterprise threat modeling, risk scoring and treatment policy
API
Enterprise risk and threat-model integration logical interface
Message/Event Schema
Threat actor attack precondition asset impact control and acceptance
Data Store
Threat scenario affected control assurance and residual risk
Control
Enterprise risk and threat-model integration enforcement assurance
Risk
Control gap underestimated or risk acceptance unowned risk
Requirement
Security controls must mitigate documented threat paths, not generic labels
Measure
Enterprise risk and threat-model integration assurance completeness
Trust Boundary
Enterprise risk and threat-model integration authority boundary
State
Governance approval recorded, Exception or rejection recorded
Business Object
Governance proposal and rationale