Put the executive summary on page 2, before the table of contents.
Some checks are pending
ci / markdown (push) Waiting to run
Some checks are pending
ci / markdown (push) Waiting to run
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:
parent
5df7ed87d5
commit
8496ef8338
23 changed files with 759 additions and 723 deletions
|
|
@ -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>9. Write-once Iceberg archive — Making yourself audit-ready with Verae DataCubes</title>
|
||||
<title>8. Write-once Iceberg archive — 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="10. Architecture for an audit interview" href="architecture.html" />
|
||||
<link rel="prev" title="8. Verae global timestamping — a cross-blockchain receipt" href="global-timestamping.html" />
|
||||
<link rel="next" title="9. Architecture for an audit interview" href="architecture.html" />
|
||||
<link rel="prev" title="7. Verae global timestamping — a cross-blockchain receipt" href="global-timestamping.html" />
|
||||
|
||||
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
|
||||
|
||||
|
|
@ -61,38 +61,37 @@
|
|||
<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"><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 current"><a class="current reference internal" href="#">9. Write-once Iceberg archive</a><ul>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#the-deletion-problem">9.1. The deletion problem</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-write-once-iceberg-means-in-this-solution">9.2. What “write-once Iceberg” means in this solution</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#how-cubes-move-into-the-archive">9.3. How cubes move into the archive</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#relation-to-classical-worm">9.4. Relation to classical WORM</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-this-does-and-does-not-satisfy">9.5. 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"><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 current"><a class="current reference internal" href="#">8. Write-once Iceberg archive</a><ul>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#the-deletion-problem">8.1. The deletion problem</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-write-once-iceberg-means-in-this-solution">8.2. What “write-once Iceberg” means in this solution</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#how-cubes-move-into-the-archive">8.3. How cubes move into the archive</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#relation-to-classical-worm">8.4. Relation to classical WORM</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-this-does-and-does-not-satisfy">8.5. What this does, and does not, satisfy</a></li>
|
||||
</ul>
|
||||
</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="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="global-timestamping.html" title="previous chapter"><span class="section-number">8. </span>Verae global timestamping — a cross-blockchain receipt</a></li>
|
||||
<li>Next: <a href="architecture.html" title="next chapter"><span class="section-number">10. </span>Architecture for an audit interview</a></li>
|
||||
<li>Previous: <a href="global-timestamping.html" title="previous chapter"><span class="section-number">7. </span>Verae global timestamping — a cross-blockchain receipt</a></li>
|
||||
<li>Next: <a href="architecture.html" title="next chapter"><span class="section-number">9. </span>Architecture for an audit interview</a></li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
@ -113,9 +112,9 @@
|
|||
<div class="body" role="main">
|
||||
|
||||
<section id="write-once-iceberg-archive">
|
||||
<h1><span class="section-number">9. </span>Write-once Iceberg archive<a class="headerlink" href="#write-once-iceberg-archive" title="Link to this heading">¶</a></h1>
|
||||
<h1><span class="section-number">8. </span>Write-once Iceberg archive<a class="headerlink" href="#write-once-iceberg-archive" title="Link to this heading">¶</a></h1>
|
||||
<section id="the-deletion-problem">
|
||||
<h2><span class="section-number">9.1. </span>The deletion problem<a class="headerlink" href="#the-deletion-problem" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">8.1. </span>The deletion problem<a class="headerlink" href="#the-deletion-problem" title="Link to this heading">¶</a></h2>
|
||||
<p>Encryption at rest stops a disk operator from <strong>reading</strong>.
|
||||
Hash verification stops a replica from <strong>substituting</strong>.
|
||||
Timestamped receipts stop a custodian from <strong>back-dating</strong>.
|
||||
|
|
@ -131,7 +130,7 @@ that cannot be produced.</p>
|
|||
administrative power does not include delete</strong>.</p>
|
||||
</section>
|
||||
<section id="what-write-once-iceberg-means-in-this-solution">
|
||||
<h2><span class="section-number">9.2. </span>What “write-once Iceberg” means in this solution<a class="headerlink" href="#what-write-once-iceberg-means-in-this-solution" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">8.2. </span>What “write-once Iceberg” means in this solution<a class="headerlink" href="#what-write-once-iceberg-means-in-this-solution" title="Link to this heading">¶</a></h2>
|
||||
<p>DataCubes — the encrypted, hash-chained containers — are
|
||||
<strong>archived</strong> into an <strong>external, write-once file-storage
|
||||
solution</strong> built on the <strong>Iceberg</strong> table/file model (a
|
||||
|
|
@ -159,7 +158,7 @@ require it — not because it is a convenient backup.</p></li>
|
|||
</ul>
|
||||
</section>
|
||||
<section id="how-cubes-move-into-the-archive">
|
||||
<h2><span class="section-number">9.3. </span>How cubes move into the archive<a class="headerlink" href="#how-cubes-move-into-the-archive" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">8.3. </span>How cubes move into the archive<a class="headerlink" href="#how-cubes-move-into-the-archive" title="Link to this heading">¶</a></h2>
|
||||
<p>A live DataCube is an operational object: it receives new
|
||||
writes, it is replicated as encrypted IPFS blocks, it is
|
||||
readable by holders of the right capabilities. On a schedule
|
||||
|
|
@ -207,7 +206,7 @@ legally permitted at all.</p></li>
|
|||
retention schedule. Counsel and the records officer do that.</p>
|
||||
</section>
|
||||
<section id="relation-to-classical-worm">
|
||||
<h2><span class="section-number">9.4. </span>Relation to classical WORM<a class="headerlink" href="#relation-to-classical-worm" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">8.4. </span>Relation to classical WORM<a class="headerlink" href="#relation-to-classical-worm" title="Link to this heading">¶</a></h2>
|
||||
<p>Broker-dealer Rule 17a-4 and similar texts speak of
|
||||
non-rewriteable, non-erasable media, originally meaning
|
||||
optical WORM, later allowing disk with object-lock semantics
|
||||
|
|
@ -221,7 +220,7 @@ receipt even if they do not trust the vendor’s “WORM was
|
|||
on” screenshot.</p>
|
||||
</section>
|
||||
<section id="what-this-does-and-does-not-satisfy">
|
||||
<h2><span class="section-number">9.5. </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">8.5. </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>This is the <strong>technical portion</strong> of retention and
|
||||
production: committed cubes are not under a single delete
|
||||
key, they are hash-checkable, and they carry a time of
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue