Security posture

Security unknown

<forma-security-unknown>

Represents unknown security state explicitly instead of collapsing it into failure or success.

Authoring tag
<forma-security-unknown>
Behavior owner
Aegis / application
Canonical source
patterns/security-unknown.html

Purpose

A security unknown records a security effect that has not been established: what is unknown, the consequence of not knowing, the evidence needed to resolve it and, where one exists, the obligation to obtain that evidence. It gives unknowns their own first-class record with a stable ID, so they are never quietly counted as passes or folded into failures. Tutela decides that something is unknown and what it blocks; the application or Ordo owns any obligation or task. Forma presents the record.

Use when

  • Tutela reports an unknown security effect that a posture, blocker list or invariant links to.
  • Reviewers need to know what evidence would resolve the unknown and who owes it.
  • An unknown must be shown with the same seriousness as a finding.

Avoid when

Behavior to know

  • An article with an "Unknown security effect" eyebrow, the stable ID as heading and a plain statement of what is unknown.
  • Consequence and evidence needed are always listed as terms in a description list.
  • The article id is the stable unknown ID for deep links from postures and blockers.
  • Terms reflow into one column on phones.

Basic example

The smallest correct markup: the canonical pattern from patterns/security-unknown.html inside its public tag. Copy this first, then adapt labels, names and state.

Canonical

Minimal security unknown

Rendered from the canonical pattern file.

Unknown security effect

SEC-UNK-003

Runtime egress behavior has not been established.

Consequence
Release posture cannot be established for the network boundary.
Evidence needed
Observed egress policy test against the release artifact.
HTML · Minimal security unknown Raw HTML for HTML · Minimal security unknown
<forma-security-unknown class="forma-component-tag">
<article class="forma-security-unknown" id="SEC-UNK-003"><header><p>Unknown security effect</p><h3>SEC-UNK-003</h3></header><p>Runtime egress behavior has not been established.</p>
<dl><div><dt>Consequence</dt><dd>Release posture cannot be established for the network boundary.</dd></div><div><dt>Evidence needed</dt><dd>Observed egress policy test against the release artifact.</dd></div></dl></article>
</forma-security-unknown>

Click or tap the code once to select all of it, then copy.

Examples

Scenario

Unknown with an assigned obligation

An unknown that blocks release, with the obligation to obtain the missing evidence linked by ID. The owner and due date come from the application's obligation record.

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.

Unknown security effect

SEC-UNK-004

The DNS resolution path used by the release artifact has not been observed.

Consequence
Blocks release: egress controls cannot be shown to cover name resolution.
Evidence needed
Packet capture from the staging runtime against this artifact.
Obligation
OBL-118, platform team, due
HTML · Unknown with an assigned obligation Raw HTML for HTML · Unknown with an assigned obligation
<forma-security-unknown class="forma-component-tag">
  <article class="forma-security-unknown" id="security-unknown-with-obligation-SEC-UNK-004" aria-labelledby="security-unknown-with-obligation-title">
    <header><p>Unknown security effect</p><h3 id="security-unknown-with-obligation-title">SEC-UNK-004</h3></header>
    <p>The DNS resolution path used by the release artifact has not been observed.</p>
    <dl>
      <div><dt>Consequence</dt><dd>Blocks release: egress controls cannot be shown to cover name resolution.</dd></div>
      <div><dt>Evidence needed</dt><dd>Packet capture from the staging runtime against this artifact.</dd></div>
      <div><dt>Obligation</dt><dd><a href="#OBL-118">OBL-118</a>, platform team, due <time datetime="2026-10-03">3 Oct 2026</time></dd></div>
    </dl>
  </article>
</forma-security-unknown>

Click or tap the code once to select all of it, then copy.

Scenario

Unknown outside the release scope

An unknown that Tutela reports as not blocking this release scope. It is still recorded and visible; the consequence states the limit explicitly, and no obligation exists yet.

Unknown security effect

SEC-UNK-009

Behavior of the offline export feature on shared devices has not been established.

Consequence
Does not block this release; offline export is outside the assessed scope.
Evidence needed
Device-sharing test on the supported mobile platforms.
Obligation
None assigned
HTML · Unknown outside the release scope Raw HTML for HTML · Unknown outside the release scope
<forma-security-unknown class="forma-component-tag">
  <article class="forma-security-unknown" id="security-unknown-non-blocking-SEC-UNK-009" aria-labelledby="security-unknown-non-blocking-title">
    <header><p>Unknown security effect</p><h3 id="security-unknown-non-blocking-title">SEC-UNK-009</h3></header>
    <p>Behavior of the offline export feature on shared devices has not been established.</p>
    <dl>
      <div><dt>Consequence</dt><dd>Does not block this release; offline export is outside the assessed scope.</dd></div>
      <div><dt>Evidence needed</dt><dd>Device-sharing test on the supported mobile platforms.</dd></div>
      <div><dt>Obligation</dt><dd>None assigned</dd></div>
    </dl>
  </article>
</forma-security-unknown>

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.

Mobile example

Unknown effect on a phone

An unknown with long consequence text at phone width.

Viewport width

Frames narrower than the selected width show the component at the width available.

What changes at narrow widths

  • The description list auto-fits columns of at least min(12rem, 100%), so at 320px each term/value pair stacks in one column.
  • The statement and values wrap anywhere; nothing scrolls horizontally.
  • The eyebrow, ID heading and statement keep the same order in every orientation.
  • Links in values are inline text; keep one per value so tap targets stay distinct.
HTML · Unknown effect on a phone Raw HTML for HTML · Unknown effect on a phone
<forma-security-unknown class="forma-component-tag">
  <article class="forma-security-unknown" id="security-unknown-mobile-SEC-UNK-003" aria-labelledby="security-unknown-mobile-title">
    <header><p>Unknown security effect</p><h3 id="security-unknown-mobile-title">SEC-UNK-003</h3></header>
    <p>Runtime egress behavior has not been established.</p>
    <dl>
      <div><dt>Consequence</dt><dd>Release posture cannot be established for the network boundary, including traffic initiated by agent tools and scheduled jobs.</dd></div>
      <div><dt>Evidence needed</dt><dd>Observed egress policy test against the release artifact.</dd></div>
    </dl>
  </article>
</forma-security-unknown>

Click or tap the code once to select all of it, then copy.

Baseline

Mobile · 320px

The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.

Viewport width

Frames narrower than the selected width show the component at the width available.

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.

Native and ARIA attributes
AttributeOnValuesDefaultDescription
idarticlestable unknown ID—Deep-link target; use the stable Tutela ID such as SEC-UNK-003.
aria-labelledbyarticleid of the heading—Optional. Names the article by its unknown ID.
hrefastable record URL or #ID—Links to the obligation or related records.
datetimetimeISO 8601 date—Machine-readable obligation due date.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-security-unknownBlock class—Root article: bordered, padded primary surface. The header's paragraph is a small uppercase eyebrow; the description list is an auto-fit grid of at least 12rem columns with secondary-colored bold terms and values that wrap anywhere.
Keyboard interaction
KeysResult
Tab / Shift+TabMoves between links in the record.
EnterFollows the focused link.
Events
EventDescription
—No events.

Form behavior

Not a form control.

States

Security unknown states
StateHow it is expressedPresentation
BlockingConsequence text states that it blocksThe unknown prevents a posture or transition for its scope.
Non-blockingConsequence text states the limitRecorded and visible, but outside the blocking scope.
With obligationObligation term with a linkSomeone owes the evidence; owner and due date shown.
Without obligationObligation term says None assignedExplicitly unowned rather than blank.

Accessibility

Forma provides

  • Labels the record as an unknown in visible text; no color or icon is needed to tell it apart from a finding.
  • Uses a description list so consequence and evidence needed are announced as pairs.
  • Reflows to one column at 320px.

Your application supplies

  • Always include the consequence and the evidence needed.
  • State explicitly when no obligation exists.
  • Link the unknown from every posture or blocker list it affects, using its stable ID.
  • Never present an unknown as a pass or a failure.

Responsive behavior

  • The article has zero minimum inline size.
  • Terms auto-fit into columns of at least min(12rem, 100%), one column on narrow screens.
  • Values wrap anywhere. No breakpoints are needed.

Motion

  • No animation: the record is static.

Usage guidance

Do

  • Write the statement as what is not known, not as a suspected failure.
  • Name the specific evidence that would resolve the unknown.

Avoid

  • Styling unknowns as warnings to make them look less serious than violations.
  • Omitting the consequence because it is uncertain; say what cannot be established.

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.