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>3. The Verae DataCube Server Solution — Making yourself audit-ready with Verae DataCubes</title>
|
||||
<title>2. The Verae DataCube Server Solution — 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="4. Secure communications — data in transit" href="data-in-transit.html" />
|
||||
<link rel="prev" title="2. What Verae provides — and what it does not" href="what-verae-provides.html" />
|
||||
<link rel="next" title="3. Secure communications — data in transit" href="data-in-transit.html" />
|
||||
<link rel="prev" title="1. What Verae provides — and what it does not" href="what-verae-provides.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 current"><a class="current reference internal" href="#">3. The Verae DataCube Server Solution</a><ul>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#purpose">3.1. Purpose</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#the-datacube-as-a-container">3.2. The DataCube as a container</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#two-information-states-one-operational-picture">3.3. Two information states, one operational picture</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-server-means-in-practice">3.4. What “server” means in practice</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-the-server-solution-is-not">3.5. What the server solution is not</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 current"><a class="current reference internal" href="#">2. The Verae DataCube Server Solution</a><ul>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#purpose">2.1. Purpose</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#the-datacube-as-a-container">2.2. The DataCube as a container</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#two-information-states-one-operational-picture">2.3. Two information states, one operational picture</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-server-means-in-practice">2.4. What “server” means in practice</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#what-the-server-solution-is-not">2.5. What the server solution is not</a></li>
|
||||
</ul>
|
||||
</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"><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-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"><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="what-verae-provides.html" title="previous chapter"><span class="section-number">2. </span>What Verae provides — and what it does not</a></li>
|
||||
<li>Next: <a href="data-in-transit.html" title="next chapter"><span class="section-number">4. </span>Secure communications — data in transit</a></li>
|
||||
<li>Previous: <a href="what-verae-provides.html" title="previous chapter"><span class="section-number">1. </span>What Verae provides — and what it does not</a></li>
|
||||
<li>Next: <a href="data-in-transit.html" title="next chapter"><span class="section-number">3. </span>Secure communications — data in transit</a></li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
@ -113,9 +112,9 @@
|
|||
<div class="body" role="main">
|
||||
|
||||
<section id="the-verae-datacube-server-solution">
|
||||
<h1><span class="section-number">3. </span>The Verae DataCube Server Solution<a class="headerlink" href="#the-verae-datacube-server-solution" title="Link to this heading">¶</a></h1>
|
||||
<h1><span class="section-number">2. </span>The Verae DataCube Server Solution<a class="headerlink" href="#the-verae-datacube-server-solution" title="Link to this heading">¶</a></h1>
|
||||
<section id="purpose">
|
||||
<h2><span class="section-number">3.1. </span>Purpose<a class="headerlink" href="#purpose" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">2.1. </span>Purpose<a class="headerlink" href="#purpose" title="Link to this heading">¶</a></h2>
|
||||
<p>A Verae DataCube Server Solution is the on-premises or
|
||||
customer-hosted assembly that gives an organization a place to put
|
||||
sensitive digital objects, a way to move them, a way to prove when
|
||||
|
|
@ -129,7 +128,7 @@ not a single binary, and it is not a cloud folder with a padlock
|
|||
icon.</p>
|
||||
</section>
|
||||
<section id="the-datacube-as-a-container">
|
||||
<h2><span class="section-number">3.2. </span>The DataCube as a container<a class="headerlink" href="#the-datacube-as-a-container" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">2.2. </span>The DataCube as a container<a class="headerlink" href="#the-datacube-as-a-container" title="Link to this heading">¶</a></h2>
|
||||
<p>A <strong>DataCube</strong> is a customer-controlled container for digital
|
||||
objects and for the metadata that makes those objects examinable.
|
||||
Typical contents include:</p>
|
||||
|
|
@ -150,7 +149,7 @@ records stay in <strong>storage the customer controls</strong>; Verae seals a
|
|||
that split operational rather than rhetorical.</p>
|
||||
</section>
|
||||
<section id="two-information-states-one-operational-picture">
|
||||
<h2><span class="section-number">3.3. </span>Two information states, one operational picture<a class="headerlink" href="#two-information-states-one-operational-picture" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">2.3. </span>Two information states, one operational picture<a class="headerlink" href="#two-information-states-one-operational-picture" title="Link to this heading">¶</a></h2>
|
||||
<p>Classical security training divides information into <strong>data in
|
||||
transit</strong> and <strong>data at rest</strong>. The DataCube Server Solution is
|
||||
built around that division.</p>
|
||||
|
|
@ -174,7 +173,7 @@ receipts (Chapter 6) and the cross-blockchain timestamping
|
|||
architecture (Chapter 8) address that.</p>
|
||||
</section>
|
||||
<section id="what-server-means-in-practice">
|
||||
<h2><span class="section-number">3.4. </span>What “server” means in practice<a class="headerlink" href="#what-server-means-in-practice" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">2.4. </span>What “server” means in practice<a class="headerlink" href="#what-server-means-in-practice" title="Link to this heading">¶</a></h2>
|
||||
<p>In a typical deployment the organization runs, or links:</p>
|
||||
<ul class="simple">
|
||||
<li><p>a <strong>Peergos</strong> instance (or equivalent cryptree client) that
|
||||
|
|
@ -200,7 +199,7 @@ serves a wrong block (detected by hash), a timestamping link that
|
|||
is down, an archive job that did not run.</p>
|
||||
</section>
|
||||
<section id="what-the-server-solution-is-not">
|
||||
<h2><span class="section-number">3.5. </span>What the server solution is not<a class="headerlink" href="#what-the-server-solution-is-not" title="Link to this heading">¶</a></h2>
|
||||
<h2><span class="section-number">2.5. </span>What the server solution is not<a class="headerlink" href="#what-the-server-solution-is-not" title="Link to this heading">¶</a></h2>
|
||||
<p>It is not a substitute for workforce training. It is not a
|
||||
substitute for a Business Associate Agreement analysis. It is not a
|
||||
substitute for access reviews. It is not, by itself, “the HIPAA
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue