marchon/peergos-making-yourself-audit-ready-with-verae-datacubes
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Put the executive summary on page 2, before the table of contents.
Some checks are pending
ci / markdown (push) Waiting to run
Details

Browse source 
The cover stays page 1. Numbered chapters now start at What Verae
provides. The TOC lists Executive summary at page 2.
This commit is contained in:
George Lambert 2026-09-16 01:21:05 -04:00
parent 5df7ed87d5
commit 8496ef8338
23 changed files with 759 additions and 723 deletions
Download patch file Download diff file Expand all files Collapse all files

75
build/html/data-at-rest.html
View file

@ -5,19 +5,19 @@
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>5. Encryption at rest — IPFS blocks and Peergos &#8212; Making yourself audit-ready with Verae DataCubes</title>
<title>4. Encryption at rest — IPFS blocks and Peergos &#8212; Making yourself audit-ready with Verae DataCubes</title>
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=5ecbeea2" />
<link rel="stylesheet" type="text/css" href="_static/basic.css?v=b08954a9" />
<link rel="stylesheet" type="text/css" href="_static/alabaster.css?v=2a97f0c7" />
<link rel="stylesheet" type="text/css" href="_static/verae.css?v=050b9d5b" />
<link rel="stylesheet" type="text/css" href="_static/verae.css?v=2d7b7068" />
<script src="_static/documentation_options.js?v=250a654d"></script>
<script src="_static/doctools.js?v=fd6eb6e6"></script>
<script src="_static/sphinx_highlight.js?v=6ffebe34"></script>
<link rel="icon" href="_static/VeraeFullLogo.png"/>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="6. Global timestamped receipts" href="timestamped-receipts.html" />
<link rel="prev" title="4. Secure communications — data in transit" href="data-in-transit.html" />
<link rel="next" title="5. Global timestamped receipts" href="timestamped-receipts.html" />
<link rel="prev" title="3. Secure communications — data in transit" href="data-in-transit.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
@ -61,40 +61,39 @@
<script>document.getElementById('searchbox').style.display = "block"</script><h3>Navigation</h3>
<p class="caption" role="heading"><span class="caption-text">Contents</span></p>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="executive.html">1. Executive summary</a></li>
<li class="toctree-l1"><a class="reference internal" href="what-verae-provides.html">2. What Verae provides — and what it does not</a></li>
<li class="toctree-l1"><a class="reference internal" href="datacube-server.html">3. The Verae DataCube Server Solution</a></li>
<li class="toctree-l1"><a class="reference internal" href="data-in-transit.html">4. Secure communications — data in transit</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">5. Encryption at rest — IPFS blocks and Peergos</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#the-problem">5.1. The problem</a></li>
<li class="toctree-l2"><a class="reference internal" href="#content-addressed-blocks">5.2. Content-addressed blocks</a></li>
<li class="toctree-l2"><a class="reference internal" href="#peergos-on-top-of-ipfs">5.3. Peergos on top of IPFS</a></li>
<li class="toctree-l2"><a class="reference internal" href="#tamper-evident-restore">5.4. Tamper-evident restore</a></li>
<li class="toctree-l2"><a class="reference internal" href="#append-only-at-the-cube-layer">5.5. Append-only at the cube layer</a></li>
<li class="toctree-l2"><a class="reference internal" href="#what-a-disk-operator-sees">5.6. What a disk operator sees</a></li>
<li class="toctree-l2"><a class="reference internal" href="#what-this-does-and-does-not-satisfy">5.7. What this does, and does not, satisfy</a></li>
<li class="toctree-l1"><a class="reference internal" href="what-verae-provides.html">1. What Verae provides — and what it does not</a></li>
<li class="toctree-l1"><a class="reference internal" href="datacube-server.html">2. The Verae DataCube Server Solution</a></li>
<li class="toctree-l1"><a class="reference internal" href="data-in-transit.html">3. Secure communications — data in transit</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">4. Encryption at rest — IPFS blocks and Peergos</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#the-problem">4.1. The problem</a></li>
<li class="toctree-l2"><a class="reference internal" href="#content-addressed-blocks">4.2. Content-addressed blocks</a></li>
<li class="toctree-l2"><a class="reference internal" href="#peergos-on-top-of-ipfs">4.3. Peergos on top of IPFS</a></li>
<li class="toctree-l2"><a class="reference internal" href="#tamper-evident-restore">4.4. Tamper-evident restore</a></li>
<li class="toctree-l2"><a class="reference internal" href="#append-only-at-the-cube-layer">4.5. Append-only at the cube layer</a></li>
<li class="toctree-l2"><a class="reference internal" href="#what-a-disk-operator-sees">4.6. What a disk operator sees</a></li>
<li class="toctree-l2"><a class="reference internal" href="#what-this-does-and-does-not-satisfy">4.7. What this does, and does not, satisfy</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="timestamped-receipts.html">6. Global timestamped receipts</a></li>
<li class="toctree-l1"><a class="reference internal" href="peergos-eu-evaluations.html">7. Peergos security evaluations in Europe</a></li>
<li class="toctree-l1"><a class="reference internal" href="global-timestamping.html">8. Verae global timestamping — a cross-blockchain receipt</a></li>
<li class="toctree-l1"><a class="reference internal" href="iceberg-archive.html">9. Write-once Iceberg archive</a></li>
<li class="toctree-l1"><a class="reference internal" href="architecture.html">10. Architecture for an audit interview</a></li>
<li class="toctree-l1"><a class="reference internal" href="baa-dpa.html">11. BAAs, DPAs, and ciphertext without host keys</a></li>
<li class="toctree-l1"><a class="reference internal" href="checklist.html">12. Audit-ready checklist</a></li>
<li class="toctree-l1"><a class="reference internal" href="howto.html">13. How to use this briefing</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-james-garfinkel.html">14. James H. Garfinkel</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-stuart-haber.html">15. Stuart Haber</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-george-lambert.html">16. George Lambert</a></li>
<li class="toctree-l1"><a class="reference internal" href="contact.html">17. Verae Inc — contact</a></li>
<li class="toctree-l1"><a class="reference internal" href="timestamped-receipts.html">5. Global timestamped receipts</a></li>
<li class="toctree-l1"><a class="reference internal" href="peergos-eu-evaluations.html">6. Peergos security evaluations in Europe</a></li>
<li class="toctree-l1"><a class="reference internal" href="global-timestamping.html">7. Verae global timestamping — a cross-blockchain receipt</a></li>
<li class="toctree-l1"><a class="reference internal" href="iceberg-archive.html">8. Write-once Iceberg archive</a></li>
<li class="toctree-l1"><a class="reference internal" href="architecture.html">9. Architecture for an audit interview</a></li>
<li class="toctree-l1"><a class="reference internal" href="baa-dpa.html">10. BAAs, DPAs, and ciphertext without host keys</a></li>
<li class="toctree-l1"><a class="reference internal" href="checklist.html">11. Audit-ready checklist</a></li>
<li class="toctree-l1"><a class="reference internal" href="howto.html">12. How to use this briefing</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-james-garfinkel.html">13. James H. Garfinkel</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-stuart-haber.html">14. Stuart Haber</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-george-lambert.html">15. George Lambert</a></li>
<li class="toctree-l1"><a class="reference internal" href="contact.html">16. Verae Inc — contact</a></li>
</ul>
<div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.html">Documentation overview</a><ul>
<li>Previous: <a href="data-in-transit.html" title="previous chapter"><span class="section-number">4. </span>Secure communications — data in transit</a></li>
<li>Next: <a href="timestamped-receipts.html" title="next chapter"><span class="section-number">6. </span>Global timestamped receipts</a></li>
<li>Previous: <a href="data-in-transit.html" title="previous chapter"><span class="section-number">3. </span>Secure communications — data in transit</a></li>
<li>Next: <a href="timestamped-receipts.html" title="next chapter"><span class="section-number">5. </span>Global timestamped receipts</a></li>
</ul></li>
</ul>
</div>
@ -115,9 +114,9 @@
<div class="body" role="main">
<section id="encryption-at-rest-ipfs-blocks-and-peergos">
<h1><span class="section-number">5. </span>Encryption at rest — IPFS blocks and Peergos<a class="headerlink" href="#encryption-at-rest-ipfs-blocks-and-peergos" title="Link to this heading"></a></h1>
<h1><span class="section-number">4. </span>Encryption at rest — IPFS blocks and Peergos<a class="headerlink" href="#encryption-at-rest-ipfs-blocks-and-peergos" title="Link to this heading"></a></h1>
<section id="the-problem">
<h2><span class="section-number">5.1. </span>The problem<a class="headerlink" href="#the-problem" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.1. </span>The problem<a class="headerlink" href="#the-problem" title="Link to this heading"></a></h2>
<p>Bytes that are no longer moving still have to live somewhere: a
disk, a replica, a backup, a cold archive. The people who operate
those surfaces — hosting providers, backup operators, someone
@ -132,7 +131,7 @@ even if it keeps confidentiality.</p>
verifying hashes on the way in and the way out.</p>
</section>
<section id="content-addressed-blocks">
<h2><span class="section-number">5.2. </span>Content-addressed blocks<a class="headerlink" href="#content-addressed-blocks" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.2. </span>Content-addressed blocks<a class="headerlink" href="#content-addressed-blocks" title="Link to this heading"></a></h2>
<p>IPFS names a block by a cryptographic hash of its contents (a
Content Identifier, or CID). Two properties follow immediately:</p>
<ul class="simple">
@ -148,7 +147,7 @@ prevent a hostile replica from refusing to serve a block
serving a substitute and hoping nobody notices (integrity).</p>
</section>
<section id="peergos-on-top-of-ipfs">
<h2><span class="section-number">5.3. </span>Peergos on top of IPFS<a class="headerlink" href="#peergos-on-top-of-ipfs" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.3. </span>Peergos on top of IPFS<a class="headerlink" href="#peergos-on-top-of-ipfs" title="Link to this heading"></a></h2>
<p>Peergos is not “IPFS with a folder UI.” It is an encrypted
filesystem — a <strong>cryptree</strong> — whose nodes and file chunks are
stored as IPFS blocks. The properties that matter for an
@ -177,7 +176,7 @@ without placing the chunk key on the server.</p></li>
</ul>
</section>
<section id="tamper-evident-restore">
<h2><span class="section-number">5.4. </span>Tamper-evident restore<a class="headerlink" href="#tamper-evident-restore" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.4. </span>Tamper-evident restore<a class="headerlink" href="#tamper-evident-restore" title="Link to this heading"></a></h2>
<p>“Backup” in this architecture does not mean a second plaintext
copy in a different building. It means:</p>
<ol class="arabic simple">
@ -194,7 +193,7 @@ plaintext it had. Helpfulness of that kind is how silent
corruption and silent substitution enter an evidence set.</p>
</section>
<section id="append-only-at-the-cube-layer">
<h2><span class="section-number">5.5. </span>Append-only at the cube layer<a class="headerlink" href="#append-only-at-the-cube-layer" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.5. </span>Append-only at the cube layer<a class="headerlink" href="#append-only-at-the-cube-layer" title="Link to this heading"></a></h2>
<p>Peergos itself uses signed updates and immutable blocks. The
Verae DataCube adds an <strong>application-level chain</strong>: a JSONL
history in which each record hashes the previous record. Dual
@ -212,7 +211,7 @@ of writes is append-only at the application layer.</p></li>
<p>Both are needed. Neither is a SOC 2 report.</p>
</section>
<section id="what-a-disk-operator-sees">
<h2><span class="section-number">5.6. </span>What a disk operator sees<a class="headerlink" href="#what-a-disk-operator-sees" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.6. </span>What a disk operator sees<a class="headerlink" href="#what-a-disk-operator-sees" title="Link to this heading"></a></h2>
<p>If keys never leave the client or the customer’s HSM, a disk
operator, a VM snapshot operator, and an offsite replica operator
see <strong>opaque hashed ciphertext</strong>. They do not see PHI, they do
@ -224,7 +223,7 @@ addresses, billing identity, and support logs can still be
personal data. Chapter 11 takes that up.</p>
</section>
<section id="what-this-does-and-does-not-satisfy">
<h2><span class="section-number">5.7. </span>What this does, and does not, satisfy<a class="headerlink" href="#what-this-does-and-does-not-satisfy" title="Link to this heading"></a></h2>
<h2><span class="section-number">4.7. </span>What this does, and does not, satisfy<a class="headerlink" href="#what-this-does-and-does-not-satisfy" title="Link to this heading"></a></h2>
<p>For HIPAA encryption of ePHI <strong>at rest</strong>, for SOC 2 CC6
encryption of stored data, and for ISO 27001 Annex A cryptography
and storage, this is the <strong>technical control</strong>: ciphertext on