- SourceAegis
- ObservationSEC-EVD-042
- InvariantSEC-INV-014
- StateViolated
Security evidence chain
<forma-security-evidence-chain>
Shows the provenance chain supporting a security conclusion.
- Authoring tag
<forma-security-evidence-chain>- Category
- Security posture
- Behavior owner
- Aegis / application
- Canonical source
patterns/security-evidence-chain.html
Purpose
A security evidence chain shows the path from an evidence source through an observation to the invariant it supports and the resulting state, for example Aegis → SEC-EVD-042 → SEC-INV-014 → Violated. Each step is labelled with its role and, where it is a record, links to it by stable ID. The chain lets a reviewer check that a conclusion rests on a real observation rather than proximity or assumption. Tutela supplies the relationships; Forma lays them out in order and never infers a link that was not supplied.
Use when
- A security conclusion must be traceable to its source and observation.
- Reviewers need to open each record in the chain by stable ID.
- A missing observation must be visible as a gap in the chain.
Avoid when
- The provenance is for analytics or report values rather than security conclusions: use Provenance trail.
- You need to show whether evidence is current or stale: use Security evidence age.
- You need to state a general claim and its supporting evidence type (supports, contradicts): use Evidence relationship.
Behavior to know
- A captioned
figurewrapping an ordered list, so step order is part of the markup. - Each step shows a bold role label (Source, Observation, Invariant, State) above its value.
- Steps flow in an auto-fit grid on wide screens and stack in one column below 30rem.
- There are no drawn connectors: order comes from the list, and each step names its role in text.
Basic example
The smallest correct markup: the canonical pattern from patterns/security-evidence-chain.html inside its public tag. Copy this first, then adapt labels, names and state.
Minimal security evidence chain
Rendered from the canonical pattern file.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
- SourceAegis
- ObservationSEC-EVD-042
- InvariantSEC-INV-014
- StateViolated
<forma-security-evidence-chain class="forma-component-tag">
<figure class="forma-security-evidence-chain" aria-labelledby="evidence-chain-title"><figcaption id="evidence-chain-title">Evidence chain for SEC-INV-014</figcaption>
<ol><li><strong>Source</strong><span>Aegis</span></li><li><strong>Observation</strong><a href="#SEC-EVD-042">SEC-EVD-042</a></li><li><strong>Invariant</strong><a href="#SEC-INV-014">SEC-INV-014</a></li><li><strong>State</strong><span>Violated</span></li></ol></figure>
</forma-security-evidence-chain>
Click or tap the code once to select all of it, then copy.
Examples
Chain ending in a verified state
A complete chain for an authorization invariant, from a CI source through a linked observation to a Verified state.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
- SourceCI policy tests, run 1042
- ObservationSEC-EVD-044
- InvariantSEC-INV-003
- StateVerified
<forma-security-evidence-chain class="forma-component-tag">
<figure class="forma-security-evidence-chain" aria-labelledby="security-evidence-chain-verified-caption">
<figcaption id="security-evidence-chain-verified-caption">Evidence chain for SEC-INV-003</figcaption>
<ol>
<li><strong>Source</strong><span>CI policy tests, run 1042</span></li>
<li><strong>Observation</strong><a href="#SEC-EVD-044">SEC-EVD-044</a></li>
<li><strong>Invariant</strong><a href="#SEC-INV-003">SEC-INV-003</a></li>
<li><strong>State</strong><span>Verified</span></li>
</ol>
</figure>
</forma-security-evidence-chain>
Click or tap the code once to select all of it, then copy.
Chain with a missing observation
No observation exists for the invariant, so the Observation step says so in text and the state is Unknown. The gap is shown rather than skipped, which would make the chain look complete.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
- SourceRuntime egress monitor
- ObservationNone recorded for this artifact
- InvariantSEC-INV-021
- StateUnknown
<forma-security-evidence-chain class="forma-component-tag">
<figure class="forma-security-evidence-chain" aria-labelledby="security-evidence-chain-missing-observation-caption">
<figcaption id="security-evidence-chain-missing-observation-caption">Evidence chain for SEC-INV-021</figcaption>
<ol>
<li><strong>Source</strong><span>Runtime egress monitor</span></li>
<li><strong>Observation</strong><span>None recorded for this artifact</span></li>
<li><strong>Invariant</strong><a href="#SEC-INV-021">SEC-INV-021</a></li>
<li><strong>State</strong><span>Unknown</span></li>
</ol>
</figure>
</forma-security-evidence-chain>
Click or tap the code once to select all of it, then copy.
Mobile
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
Evidence chain on a phone
A chain with long source text at phone width.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
What changes at narrow widths
- Below 30rem the steps stack in a single column, preserving the Source → Observation → Invariant → State order top to bottom.
- Each step is bordered and padded, and its content breaks anywhere, so long source names never overflow.
- Record links are block-level inside each step, which makes each one a full-width tap target.
- Forma does not reset the browser's default figure margins, so at 320px the chain is inset by roughly 40px on each side and steps are correspondingly narrower.
<forma-security-evidence-chain class="forma-component-tag">
<figure class="forma-security-evidence-chain" aria-labelledby="security-evidence-chain-mobile-caption">
<figcaption id="security-evidence-chain-mobile-caption">Evidence chain for SEC-INV-014</figcaption>
<ol>
<li><strong>Source</strong><span>Aegis authorization audit, production mirror environment</span></li>
<li><strong>Observation</strong><a href="#SEC-EVD-042">SEC-EVD-042</a></li>
<li><strong>Invariant</strong><a href="#SEC-INV-014">SEC-INV-014</a></li>
<li><strong>State</strong><span>Violated</span></li>
</ol>
</figure>
</forma-security-evidence-chain>
Click or tap the code once to select all of it, then copy.
Mobile · 320px
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
API and configuration
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-labelledby | figure | id of figcaption | — | Names the figure by its caption, which should identify the conclusion the chain supports. |
href | a | stable record URL or #ID | — | Deep link to the observation or invariant record. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-security-evidence-chain | Block class | — | Root figure: bordered, padded primary surface. Its ordered list is an unstyled auto-fit grid of steps at least 9rem wide (one column below 30rem); each step is bordered and padded, with its strong, span and link children displayed as blocks. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves between record links in chain order. |
| Enter | Follows the focused link. |
| Event | Description |
|---|---|
— | No events. |
Form behavior
Not a form control.
States
| State | How it is expressed | Presentation |
|---|---|---|
| Complete | every step has a value or link | Source, observation, invariant and state are all present. |
| Gap | a step's text states that nothing exists | The missing link is written out, and the state is usually Unknown. |
| Resulting state | text in the State step | Verified, Violated, Unknown, Stale or N/A as supplied by Tutela. |
Accessibility
Forma provides
- Uses an ordered list inside a captioned figure, so order and count are available to assistive technology.
- Labels every step's role in visible text rather than relying on arrows or color.
- Stacks steps at 320px without horizontal scrolling.
Your application supplies
- Caption the chain with the conclusion it supports.
- Write gaps explicitly; do not leave a step empty or remove it.
- Some browser and screen-reader pairings (notably Safari with VoiceOver) drop list semantics when list-style is none; if step count matters to your users, add role="list" to the ol.
- Redact sensitive source details before rendering.
Responsive behavior
- Steps use
repeat(auto-fit, minmax(9rem, 1fr)), so four steps sit in a row on wide screens and wrap to fewer columns as space shrinks. - Below a 30rem viewport the steps are a single column.
- Content wraps anywhere inside each step.
- The root is a native figure and keeps the browser's default figure margins, which reduce available width on phones.
Motion
- No animation: the chain is static and nothing animates between steps.
Usage guidance
Do
- Keep the step order Source → Observation → Invariant → State.
- Link every record step to its stable ID.
Avoid
- Adding decorative arrows as the only indication of direction.
- Hiding a missing observation by skipping the step.
Verification specimens
Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.