Last updated: 2026-02-24
Provide a deterministic, evidence-backed submission package positioning Sentinel Protocol as a practical local AI governance reference implementation aligned to OWASP LLM Top 10 controls.
- Only in-repo, reproducible metrics are claimed.
- Unknown or non-reproduced competitor metrics stay
not_measured. - Coverage claims are mapped to concrete engine modules and config paths.
Use docs/owasp/submission-manifest.json as the single source of truth for immutable artifact hashes.
Core artifacts include:
docs/OWASP_LLM_TOP10_SENTINEL_MAP.mddocs/OWASP-HARDENING.mddocs/openapi.yamldocs/SECURITY_RELIABILITY_EVIDENCE_V4_PHASEA.mddocs/benchmarks/METHODOLOGY.mddocs/benchmarks/results/standard-datasets.jsonREADME.mdCHANGELOG.md
npm run lint
npm test -- --runInBand
npm run openapi:validate
npm run benchmark:gate
npm run benchmark:datasets
node ./scripts/prepare-owasp-submission-pack.js- Verify all CI gates are green for the target branch/tag.
- Re-generate
docs/owasp/submission-manifest.jsonand commit if hashes changed. - Confirm OWASP mapping file references current engine names and control paths.
- Include benchmark methodology and scope limitations verbatim in submission notes.
- Attach manifest and evidence links in the OWASP issue/PR description.
- Project: Sentinel Protocol
- Version: 1.0.0
- Type: Local-first AI governance firewall and policy perimeter
- Primary interfaces: HTTP proxy, websocket interception, embed middleware, control-plane APIs
- OWASP mapping:
docs/OWASP_LLM_TOP10_SENTINEL_MAP.md - Evidence manifest:
docs/owasp/submission-manifest.json - Repro command set: from this document
- Scope note: adversarial benchmark pack is mini-fixture based for deterministic local CI execution
Sentinel does not claim certified compliance status. It provides deterministic controls, mappings, and verifiable evidence artifacts to accelerate independent security review and governance workflows.