Comparison · register 09

SHA-256 / FIPS 180-4 vs FIPS 140-3.

Two regulatory anchors. Planisphere's evidence record maps both controls. This page is the comparison query's canonical destination.

01 ·

When to lead with SHA-256 / FIPS 180-4.

Use SHA-256 / FIPS 180-4 as the primary anchor when the evaluator is shaped this way.

Audience. hash algorithm · per-file pinning primitive.

Shape. hash glyph # · 2 brass slants · 2 ink crossbars.

Where it lives in the record. The SHA-256 / FIPS 180-4 cite-anchor pins next to every artifact in ATTESTATION.json. See the SHA-256 / FIPS 180-4 brief for the field-level mapping.

02 ·

When to lead with FIPS 140-3.

Use FIPS 140-3 as the primary anchor when the evaluator is shaped this way.

Audience. crypto module validation · 4 security levels.

Shape. padlock + brass keyhole + brass shackle band.

Where it lives in the record. The FIPS 140-3 cite-anchor pins next to every artifact in ATTESTATION.json. See the FIPS 140-3 brief for the field-level mapping.

03 ·

Both at once.

The evidence record maps both anchors for review — you don't have to pick.

Planisphere's evidence record is multi-control by construction. SHA-256 / FIPS 180-4 and FIPS 140-3 are both keys in the record's requirement list; the same SHA-pinned, Merkle-rooted artifact gives both evaluators a shared review record.

The requirement list is open — add any standard the regulator names. See the full compliance-control register.

Compare AI options for compliance