Third-party security assessment brief

This is an engagement packet for an independent firm. It is not a completed assessment and does not substitute for one.

Scope (proposed)

In scope:

Out of scope unless contracted separately:

What to start from

ArtifactWhere
Control mapGET /api/trust/status and trust.py
Coordinated disclosureSECURITY.md
Known residual riskREADME "Security Audit" + CHANGELOG
Dependency posture.github/workflows/dependency-audit.yml
Test gate.github/workflows/test.yml, tests/
Self-scanaegis . — current numbers are in README, not marketing

Rules of engagement

  1. Do not treat README historical claims as evidence. Prefer tests and live endpoints.
  2. SAML: if components.saml.backend is builtin, Exclusive C14N is not in play.
  3. Dynamic scanning (AEGIS_ENABLE_DYNAMIC_SCANS) is off by default and must stay off on the web tier.
  4. Demo credentials in flask seed-demo are published; they must never appear in a production evidence sample.

Deliverable we want back

A written report with severity, reproduction, and a retest plan. We will publish a summary at /security once one exists. Until then that page must say the assessment has not been commissioned.