Skip to content
AFAAQ / Capability / 05

Cybersecurity

A property of the architecture, applied across every layer at once.

Cross-cutting control1 industries require it2 published systems

Argument

Security is the one capability that adds no node. It is not a final layer and not a gate at the end — it is a boundary that crosses everything already there.

Role in the system

Cross-cutting by construction.

Every other capability contributes a node to a layer. Security contributes a boundary instead. Identity, encryption, application security, configuration, audit, delivery and resilience each cross the layers they apply to and stop where they do not.

That is what makes coverage a fact about the architecture rather than a claim about the team: the question is not whether a control exists, but which layers it crosses.

System effect

No new node. A boundary instead.

The composition below is the only one on this site where selecting a capability changes nothing in the layer stack and everything about the shape around it.

AFAAQ / System effectCybersecurity
  • Audience: Users
  • Application: API platform
  • Data: Data
  • Existing layer
  • Control boundary
Selecting this capability adds no node to the layer stack. It draws a control boundary across the 3 layers a composed system already has.
Layers
3
Nodes contributed
None — boundary
Connections
2
Disciplines
4

Context

Evidence

AFAAQ / Next

Start a project

Tell us what you are trying to build, improve or replace.

Start a project