peergos-making-yourself-aud.../build/html/_sources/checklist.rst.txt
George Lambert da60402e88
Some checks are pending
ci / markdown (push) Waiting to run
Sphinx HTML and 17-page LaTeX PDF for the audit-ready pack
source/ is the Sphinx tree. Companion PDF hrefs are relative, not Markdown.
2026-09-15 23:59:54 -04:00

62 lines
2 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Audit-ready checklist
=====================
Use this as a working list. Check items only when **evidence exists**
(screenshot, log export, signed policy, ticket). This list is not a
certificate.
A. Scope and data map
---------------------
* Named legal entity and systems in scope (console, Drive, NATS, IPFS, ns1)
* Data-flow diagram: endpoint → HPKE/NATS → cryptree/IPFS
* What is PHI / personal data vs ciphertext vs routing metadata
* Peergos verification chapter attached (:doc:`verification`)
B. Keys and encryption
----------------------
* Customer holds Peergos/Drive keys; not on storage host
* NPE/HPKE endpoint keys in directory; private 0600; no xor content
* Signed Ed25519 config; unsigned rejected; admin-history prev+new+diff
* HSM or documented lab-to-HSM path
C. Access
---------
* Console ``PFC_REQUIRE_AUTH=1``, TOTP; Drive login separate
* Inspect k-of-n; author is not an officer; log-before-reveal
* Joiner / mover / leaver for console users
* Google SSO does **not** unwrap cubes
D. Integrity and backup
-----------------------
* Cube chain append-only JSONL; dual hash
* Hash registry: first SHA-256 and receipt win
* Peergos/IPFS: hash-verified encrypted blocks (restore = re-fetch CIDs)
* Restore test: recover a cube from content-addressed ciphertext without
plaintext backup tapes
E. Logging
----------
* Inspect audit events
* SM summaries: codes + lookup_id only (no bodies)
* Admin-history cube for config
F. Contracts (counsel)
----------------------
* Written BA / not-a-BA determination for disk, VM, backup, IPFS
* DPA Art. 28 where usernames/logs/IPs are processed
* NATS operator: metadata vs content in the annex
* Peergos component assurance: attach Cure53 2019 + ROS 2024 PDFs
(public; not your orgs ISO/SOC report)
G. Independent audit of *you*
-----------------------------
* SOC 2 Type I/II engagement **or** ISO 27001 registrar **or** HIPAA
risk analysis + policies (pick the program you actually need)
* Evidence window (Type II / surveillance) if applicable