Content Revisions
Every correction to our compliance, vendor, and migration data is reviewed, logged, and shown here — this is how we keep the data you rely on trustworthy and auditable. See our editorial-independence policy for how changes are approved.
In plain terms: if a fact on this site turned out to be wrong or out of date, what changed, who reviewed it, and why is recorded below — nothing gets corrected silently.
199 reviewed updates in the last 30 days — 62 module · 58 tool · 27 migrate
What this means for you
- Executive / Business Leader
- A correction log for the data your reports are built on: if a number changed, the reason and the date are here.
- GRC / Risk & Compliance
- Every change to a compliance obligation, deadline or certification record is dated and attributed — audit evidence for the data itself.
- Developer / Engineer
- Vendor and migration records change as roadmaps ship; the domain chips narrow the feed to what moved since you last checked.
- Security Architect
- Algorithm and protocol records carry their revision history; a design decision made on an old value can be re-checked here.
- Researcher / Academic
- This is the site's own errata: what was wrong, what it was corrected to, and when.
- Certification & Validation Engineer
- Every correction to a certification record is dated and attributed here — the audit trail behind each status on Product Records.
- IT Ops / DevOps
- Use the Migrate chip to see which product support claims were corrected — those are the ones to re-verify before a cutover.
- Curious Explorer
- Facts on this site get corrected in public; this page is the list of corrections.
Content edit: iot-pqc, ot-pqc
Content edit: merkle-tree-certs
Content edit: homomorphic-encryption
Content edit: homomorphic-encryption — new module, split out of confidential-computing: five learn sections, the FHE + HSM Flows workshop, exercises, quiz topic, poster (LM-076)
Content edit: confidential-computing — the FHE section and workshop step moved to the new homomorphic-encryption module; back to its five TEE steps and 60 minutes
Position only, no content change: eight Hardware Infrastructure track modules each move down one place after the new homomorphic-encryption module
Content edit: quantum-threats
Content edit: confidential-computing
Content edit: aerospace-pqc, ai-security-pqc, emv-payment-pqc, healthcare-pqc, pqc-risk-management
Content edit: confidential-computing
Content edit: quantum-threats
Content edit: quantum-threats
Content edit: automotive-pqc, crypto-mgmt-modernization
Content edit: confidential-computing
Content edit: confidential-computing
Library: restore fhe.rs v0.1.1 reference row (held in 4.144.0), evidence re-captured from docs.rs
Content edit: confidential-computing
Content edit: confidential-computing
Content edit: api-security-jwt
Content edit: api-security-jwt
Content edit: 5g-security, automotive-pqc, digital-assets, emv-payment-pqc, government-defense-pqc, healthcare-pqc, iot-pqc, ot-pqc, secure-boot-pqc, trust-services-pqc
content review, no change required (iot-pqc, ot-pqc) — Owner reviewed both split modules (LM-074, LM-075) in the browser on the dev build (port 5175) on 1 Oct 2026 and replied "looks good"; asked on 2 Oct whether that counts as a recorded r
Content edit: iot-pqc
Library r66: new row NIST-IR-8259r1; 11 rows linked to new trusted sources (owner-approved, Codex cross-checked)
Raw feed: /data/revisions.jsonl
Related content
Next step
Release notesThe changelog lists what each release changed, beyond the data corrections here.