ASD Essentials Makes Security Scope an Architecture Relationship

The Essentials guidance places assets in every relevant security domain and separates implementation phases from maturity. EA repositories need to preserve functions, responsibilities and evidence.

In this analysis

• Scope follows function and consequence
• Choose chapters by responsibility
• Use phases to sequence work
• Make the architecture handoff explicit
• Reuse evidence without carrying over the rating

Evaluate the relationships your architecture platform must hold

Related analysis

• Application Portfolio Management: A Rationalization Playbook
• From Strategy to Execution: The Traceability Spine Your EA Tool Must Hold
• Can Your Architecture Repository Keep Conflicting Evidence? A PPMN 1.0 Test

ASD Essentials: Map Asset Scope and Security Dependencies — Vantograph