Sphinx HTML and 17-page LaTeX PDF for the audit-ready pack
Some checks are pending
ci / markdown (push) Waiting to run

source/ is the Sphinx tree. Companion PDF hrefs are relative, not Markdown.
This commit is contained in:
George Lambert 2026-09-15 23:59:54 -04:00
parent afa270a141
commit da60402e88
104 changed files with 16818 additions and 0 deletions

View file

@ -0,0 +1,195 @@
<!DOCTYPE html>
<html lang="en" data-content_root="./">
<head>
<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>Peergos verification (what was actually audited) &#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=27fed22d" />
<script src="_static/documentation_options.js?v=5929fcd5"></script>
<script src="_static/doctools.js?v=fd6eb6e6"></script>
<script src="_static/sphinx_highlight.js?v=6ffebe34"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Architecture (audit interview)" href="architecture.html" />
<link rel="prev" title="Making yourself audit-ready with Verae DataCubes" href="index.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
</head><body>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<section id="peergos-verification-what-was-actually-audited">
<h1>Peergos verification (what was actually audited)<a class="headerlink" href="#peergos-verification-what-was-actually-audited" title="Link to this heading"></a></h1>
<p>This chapter records <strong>sourced</strong> facts. It does <strong>not</strong> turn Peergos, Verae,
or DataCubes into a HIPAA, SOC 2, or ISO 27001 certificate.</p>
<section id="claim-to-check">
<h2>Claim to check<a class="headerlink" href="#claim-to-check" title="Link to this heading"></a></h2>
<p>Data at rest is stored in an encrypted append-only Peergos filesystem;
backup/restore is managed via a distributed, hashed, encrypted Peergos
IPFS system, designed and evaluated in the EU as an audited secure
filesystem.</p>
</section>
<section id="independent-security-audits-europe">
<h2>Independent security audits (Europe)<a class="headerlink" href="#independent-security-audits-europe" title="Link to this heading"></a></h2>
<p><strong>2019 — Cure53 (Berlin, Germany).</strong>
Pentest, source-code audit, <strong>crypto/design review</strong> (MayJune 2019).
No fundamental architectural or cryptographic problems; issues fixed.
Cure53: the platform <strong>passed this evaluation</strong>.</p>
<p><strong>2024 — Radically Open Security B.V. (Amsterdam, Netherlands).</strong>
Crystal-box pentest + code audit of Peergos web-ui (SepNov 2024).
<strong>0</strong> extreme / high / elevated; <strong>2</strong> moderate, <strong>6</strong> low; Peergos
states all fixed; no data exposure or integrity compromise (mostly UI
crashes).</p>
<p>Both firms are <strong>EU-based</strong>. Both full reports are <strong>public</strong>. That is a
<strong>security evaluation of the Peergos protocol/implementation</strong>, not a
HIPAA/SOC 2/ISO management-system certificate.</p>
<p>Primary sources:</p>
<ul class="simple">
<li><p><a class="reference external" href="https://peergos.org/posts/security-audit">https://peergos.org/posts/security-audit</a></p></li>
<li><p><a class="reference external" href="https://cure53.de/pentest-report_peergos.pdf">https://cure53.de/pentest-report_peergos.pdf</a></p></li>
<li><p><a class="reference external" href="https://peergos.org/posts/security-audit-2024">https://peergos.org/posts/security-audit-2024</a></p></li>
<li><p><a class="reference external" href="https://github.com/Peergos/Peergos/tree/master/audits">https://github.com/Peergos/Peergos/tree/master/audits</a></p></li>
</ul>
</section>
<section id="eu-funding-nlnet">
<h2>EU funding / NLnet<a class="headerlink" href="#eu-funding-nlnet" title="Link to this heading"></a></h2>
<ul class="simple">
<li><p>Peergos received funding from the <strong>European Union Horizon 2020</strong>
programme under <strong>NGI-POINTER</strong>, grant <strong>871528</strong> (stated on the 2024
audit post).</p></li>
<li><p>The 2024 audit was supported by <strong>NLnet</strong> (Netherlands).</p></li>
</ul>
</section>
<section id="hosted-instance-location">
<h2>Hosted instance location<a class="headerlink" href="#hosted-instance-location" title="Link to this heading"></a></h2>
<p>Peergoss hosted privacy notice states peergos.net uses servers in
<strong>Germany</strong>. <strong>Self-hosted ns1 / customer cryptree is a different
processing location</strong> and must be documented in <em>your</em> RoPA / BAA pack.</p>
</section>
<section id="encrypted-filesystem-hashed-ipfs-design">
<h2>Encrypted filesystem + hashed IPFS (design)<a class="headerlink" href="#encrypted-filesystem-hashed-ipfs-design" title="Link to this heading"></a></h2>
<ul class="simple">
<li><p><strong>Cryptree</strong>: tree of symmetric keys; fine-grained read/write caps;
sibling names hidden; writes <strong>signed</strong>.</p></li>
<li><p><strong>Chunks</strong>: up to 5 MiB, padded, independently encrypted
(Salsa20-Poly1305); random 256-bit keys (not convergent).</p></li>
<li><p><strong>IPFS</strong>: content-addressed blocks. Peergos <strong>verifies the hash</strong> of
every block read from or written to IPFS. Clients verify hashes and
signatures from a Peergos server.</p></li>
<li><p><strong>CHAMP</strong>: encrypted cryptree nodes under <strong>random 32-byte labels</strong>.</p></li>
<li><p>Sharing: hybrid <strong>X25519 + ML-KEM-1024</strong>.</p></li>
</ul>
<p>“Append-only” in Verae DataCubes is the <strong>cube chain JSONL</strong> (application
integrity). Peergos uses signed updates and immutable blocks. Do not
conflate the two layers in an audit interview.</p>
</section>
<section id="not-verified-do-not-claim">
<h2>Not verified / do not claim<a class="headerlink" href="#not-verified-do-not-claim" title="Link to this heading"></a></h2>
<ul class="simple">
<li><p>“Peergos is HIPAA certified” — <strong>false.</strong> HIPAA is not a product certificate.</p></li>
<li><p>“Peergos is SOC 2 / ISO 27001 certified” — <strong>not shown.</strong> Published
work is pentest/code audit, not Type II or ISO registrar.</p></li>
<li><p>“EU certified Peergos as a government-standard filesystem” —
<strong>overstated.</strong> What exists: EU grant funding, NLNet-funded ROS
pentest, Cure53 Berlin design+code audit.</p></li>
<li><p>“Hosts with disk/backup never need a BAA/DPA” — <strong>legal conclusion,
not a technical fact.</strong> See <a class="reference internal" href="baa-dpa.html"><span class="doc">BAAs and DPAs when ciphertext has no host keys</span></a>.</p></li>
</ul>
</section>
</section>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="Main">
<div class="sphinxsidebarwrapper">
<h1 class="logo"><a href="index.html">Making yourself audit-ready with Verae DataCubes</a></h1>
<search id="searchbox" style="display: none" role="search">
<div class="searchformwrapper">
<form class="search" action="search.html" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false" placeholder="Search"/>
<input type="submit" value="Go" />
</form>
</div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script><h3>Navigation</h3>
<ul class="current">
<li class="toctree-l1 current"><a class="current reference internal" href="#">Peergos verification (what was actually audited)</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#claim-to-check">Claim to check</a></li>
<li class="toctree-l2"><a class="reference internal" href="#independent-security-audits-europe">Independent security audits (Europe)</a></li>
<li class="toctree-l2"><a class="reference internal" href="#eu-funding-nlnet">EU funding / NLnet</a></li>
<li class="toctree-l2"><a class="reference internal" href="#hosted-instance-location">Hosted instance location</a></li>
<li class="toctree-l2"><a class="reference internal" href="#encrypted-filesystem-hashed-ipfs-design">Encrypted filesystem + hashed IPFS (design)</a></li>
<li class="toctree-l2"><a class="reference internal" href="#not-verified-do-not-claim">Not verified / do not claim</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="architecture.html">Architecture (audit interview)</a></li>
<li class="toctree-l1"><a class="reference internal" href="baa-dpa.html">BAAs and DPAs when ciphertext has no host keys</a></li>
<li class="toctree-l1"><a class="reference internal" href="checklist.html">Audit-ready checklist</a></li>
<li class="toctree-l1"><a class="reference internal" href="howto.html">How to use this pack</a></li>
</ul>
<div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.html">Documentation overview</a><ul>
<li>Previous: <a href="index.html" title="previous chapter">Making yourself audit-ready with Verae DataCubes</a></li>
<li>Next: <a href="architecture.html" title="next chapter">Architecture (audit interview)</a></li>
</ul></li>
</ul>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
&#169;2026, Verae.
|
Powered by <a href="https://www.sphinx-doc.org/">Sphinx 9.1.0</a>
&amp; <a href="https://alabaster.readthedocs.io">Alabaster 1.0.0</a>
|
<a href="_sources/verification.rst.txt"
rel="nofollow">Page source</a>
</div>
</body>
</html>