Security
Every control on this page is one of three things. Live means built and proven by the Aegis change named in its evidence column. Building means in progress. Planned means not built yet. Anodyne is engineered to NIST 800-53 and NIST CSF technical controls. It is not certified against either.
14 of 19 capabilities are Live today.
Capabilities
| Capability | Status | Aegis evidence |
|---|---|---|
| Single enforced path to every model | Live | Aegis #106 |
| Model allowlist per gate | Live | Aegis #48, #93 |
| Inline redaction of secrets and personal data | Live | Aegis #89 |
| Daily spend and call ceilings | Live | Aegis #92, #105 |
| Signed-code enforcement on both gates | Live | Aegis #114, #115 |
| Content screening, monitor mode (edge) | Live | Aegis #90 |
| Budget alerts by business domain | Live | Aegis #91 |
| Content screening (private gate) | Planned | Not built yet |
| Category blocking with an explicit fail mode | Planned | Not built yet |
| Per-call records, queryable in SQL | Live | Aegis #82, #93 |
| Cloud audit trail for every private call | Live | Aegis #112 |
| Cost attribution by business domain | Live | Aegis #85, #91 |
| NIST 800-53 control mapping, verified on every change | Live | Aegis #63 |
| Tamper-evident records | Planned | Not built yet |
| Authenticated caller identity | Planned | Not built yet |
| Policy as code, versioned per gate | Live | Aegis #93 |
| Compliance profiles per client | Planned | Not built yet |
| Edge gate | Live | Aegis #46, #89 |
| Private gate | Live | Aegis #94 |
How to read this page
- The status here is the same status shown on the home page.
- A capability moves to Live only in an Aegis change that proves it, and the evidence column names that change.
- Protected routes use one security cookie, set at sign-in. Anodyne sets no tracking or advertising cookies. See the privacy notice.