Skip to content

Security: state what dynamic testing actually runs, and what still doesn't #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wshallwshall merged 1 commit into from
Jul 31, 2026
Merged

Security: state what dynamic testing actually runs, and what still doesn't #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion security.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ <h3>NIST SSDF — built securely</h3>
</div>
<div class="card">
<h3>NIST 800-115 — tested in CI</h3>
<p>Security testing follows <b>NIST SP 800-115</b>: automated SAST, software-composition analysis, and secret-scanning on every build, plus a full functional and integration suite exercised against the running engine. <b>Dynamic application security testing (DAST) has not been performed</b>, and neither has an independent external review or penetration test — both are planned after Early Access.</p>
<p>Security testing follows <b>NIST SP 800-115</b>: automated SAST, software-composition analysis, and secret-scanning on every build, plus a full functional and integration suite exercised against the running engine. Dynamic testing is <b>limited to an automated authorization sweep</b> — on every build, a live instance is probed over a real network socket to confirm that gated endpoints refuse unauthenticated and under-privileged callers. It does not cover the non-HTTP ingress listeners, the browser console, or TLS, and <b>no independent DAST, external code review, or penetration test has been performed</b> — all planned after Early Access.</p>
</div>
<div class="card">
<h3>NIST 800-66 Rev. 2 — HIPAA-mapped</h3>
Expand Down