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

71
build/html/data-in-transit.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>4. Secure communications — data in transit &#8212; Making yourself audit-ready with Verae DataCubes</title>
<title>3. Secure communications — data in transit &#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="5. Encryption at rest — IPFS blocks and Peergos" href="data-at-rest.html" />
<link rel="prev" title="3. The Verae DataCube Server Solution" href="datacube-server.html" />
<link rel="next" title="4. Encryption at rest — IPFS blocks and Peergos" href="data-at-rest.html" />
<link rel="prev" title="2. The Verae DataCube Server Solution" href="datacube-server.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
@ -61,39 +61,38 @@
<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 current"><a class="current reference internal" href="#">4. Secure communications — data in transit</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="#point-to-point-encryption">4.2. Point-to-point encryption</a></li>
<li class="toctree-l2"><a class="reference internal" href="#visible-routing">4.3. Visible routing</a></li>
<li class="toctree-l2"><a class="reference internal" href="#error-handling-without-leaking-content">4.4. Error handling without leaking content</a></li>
<li class="toctree-l2"><a class="reference internal" href="#the-public-key-directory">4.5. The public-key directory</a></li>
<li class="toctree-l2"><a class="reference internal" href="#what-this-does-and-does-not-satisfy">4.6. 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 current"><a class="current reference internal" href="#">3. Secure communications — data in transit</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#the-problem">3.1. The problem</a></li>
<li class="toctree-l2"><a class="reference internal" href="#point-to-point-encryption">3.2. Point-to-point encryption</a></li>
<li class="toctree-l2"><a class="reference internal" href="#visible-routing">3.3. Visible routing</a></li>
<li class="toctree-l2"><a class="reference internal" href="#error-handling-without-leaking-content">3.4. Error handling without leaking content</a></li>
<li class="toctree-l2"><a class="reference internal" href="#the-public-key-directory">3.5. The public-key directory</a></li>
<li class="toctree-l2"><a class="reference internal" href="#what-this-does-and-does-not-satisfy">3.6. What this does, and does not, satisfy</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="data-at-rest.html">5. Encryption at rest — IPFS blocks and Peergos</a></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="data-at-rest.html">4. Encryption at rest — IPFS blocks and Peergos</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="datacube-server.html" title="previous chapter"><span class="section-number">3. </span>The Verae DataCube Server Solution</a></li>
<li>Next: <a href="data-at-rest.html" title="next chapter"><span class="section-number">5. </span>Encryption at rest — IPFS blocks and Peergos</a></li>
<li>Previous: <a href="datacube-server.html" title="previous chapter"><span class="section-number">2. </span>The Verae DataCube Server Solution</a></li>
<li>Next: <a href="data-at-rest.html" title="next chapter"><span class="section-number">4. </span>Encryption at rest — IPFS blocks and Peergos</a></li>
</ul></li>
</ul>
</div>
@ -114,9 +113,9 @@
<div class="body" role="main">
<section id="secure-communications-data-in-transit">
<h1><span class="section-number">4. </span>Secure communications — data in transit<a class="headerlink" href="#secure-communications-data-in-transit" title="Link to this heading"></a></h1>
<h1><span class="section-number">3. </span>Secure communications — data in transit<a class="headerlink" href="#secure-communications-data-in-transit" title="Link to this heading"></a></h1>
<section id="the-problem">
<h2><span class="section-number">4.1. </span>The problem<a class="headerlink" href="#the-problem" title="Link to this heading"></a></h2>
<h2><span class="section-number">3.1. </span>The problem<a class="headerlink" href="#the-problem" title="Link to this heading"></a></h2>
<p>A message that leaves one machine and arrives at another crosses
infrastructure the endpoints do not own: routers, load balancers,
message brokers, TLS terminators, packet-capture appliances, and
@ -129,7 +128,7 @@ they see, and <strong>what</strong> will they be able to do with it.”</p>
that <strong>routing must be visible</strong>.</p>
</section>
<section id="point-to-point-encryption">
<h2><span class="section-number">4.2. </span>Point-to-point encryption<a class="headerlink" href="#point-to-point-encryption" title="Link to this heading"></a></h2>
<h2><span class="section-number">3.2. </span>Point-to-point encryption<a class="headerlink" href="#point-to-point-encryption" title="Link to this heading"></a></h2>
<p>“Best in class” here is not a slogan; it names a concrete choice.
Production content is sealed with <strong>HPKE</strong> (Hybrid Public Key
Encryption, RFC 9180), in the HPKE-Base mode, using a suite such as
@ -152,7 +151,7 @@ configurations reject it.</p></li>
</ul>
</section>
<section id="visible-routing">
<h2><span class="section-number">4.3. </span>Visible routing<a class="headerlink" href="#visible-routing" title="Link to this heading"></a></h2>
<h2><span class="section-number">3.3. </span>Visible routing<a class="headerlink" href="#visible-routing" title="Link to this heading"></a></h2>
<p>A network that cannot see a destination cannot deliver a message.
The DataCube Server Solution therefore does <strong>not</strong> claim
anonymous, metadata-free messaging. The following remain visible
@ -171,7 +170,7 @@ broker forwards what it is given; it is <strong>not</strong> trusted with
content, and it is <strong>not</strong> trusted not to log destinations.</p>
</section>
<section id="error-handling-without-leaking-content">
<h2><span class="section-number">4.4. </span>Error handling without leaking content<a class="headerlink" href="#error-handling-without-leaking-content" title="Link to this heading"></a></h2>
<h2><span class="section-number">3.4. </span>Error handling without leaking content<a class="headerlink" href="#error-handling-without-leaking-content" title="Link to this heading"></a></h2>
<p>Failures have to be reported. A bounce that includes the original
body would undo the encryption. The design therefore returns
<strong>error metadata</strong>: an error code, a lookup identifier, a
@ -183,7 +182,7 @@ without broadcasting the payload to operators who should never see
it.</p>
</section>
<section id="the-public-key-directory">
<h2><span class="section-number">4.5. </span>The public-key directory<a class="headerlink" href="#the-public-key-directory" title="Link to this heading"></a></h2>
<h2><span class="section-number">3.5. </span>The public-key directory<a class="headerlink" href="#the-public-key-directory" title="Link to this heading"></a></h2>
<p>Point-to-point encryption is only as good as the lookup of public
keys. The server solution publishes a <strong>directory of public keys</strong>
so that availability of those keys is visible to all E2E services.
@ -194,7 +193,7 @@ never returned by the public listing API.</p>
never be given a private key.</p>
</section>
<section id="what-this-does-and-does-not-satisfy">
<h2><span class="section-number">4.6. </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">3.6. </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 Security Rule addressable encryption of ePHI <strong>in
transit</strong>, for SOC 2 CC6 cryptographic transmission, and for
ISO 27001 Annex A transmission security, this design is the