The conditions for protected handler execution.
Existing clients → HTTPS/TLS → FastAPI → Gateway → ODRE v3 → Core → Protected Handler. Clients keep their API contract; ODRE v3 runs between Gateway and Core, not between mobile devices and the server.
Security architecture
ML-KEM-768 and ML-DSA-65 are used in the server-side ODRE v3 boundary. Session, sequence, replay and authenticated request/response checks gate Protected Handler execution. Fail-Closed blocks the unverifiable request, not the whole server.
- AdmissionValidates message shape, required fields, encoding, aggregate size, and supported response forms.
- Handshake & sessionBinds protocol version, algorithm set, endpoint materials, transcript, route meaning, and session identifier.
- Sequence & replayRequires exactly the next sequence value and rejects duplicates, rollback, gaps, and concurrent double execution.
- Semantic bindingBinds method, normalized path and query, security-relevant headers, payload, session, sequence, protocol, and message type.
- Response bindingProtects supported status, content type, selected headers, cookies, response body, and request relationship.
Cryptographic roles
ML-KEM-768
Encapsulates and recovers shared secret material for the protocol.
ML-DSA-65
Authenticates handshake material and transcript integrity.
Hybrid handshake
Binds the required cryptographic components to the same peer, session, and route meaning.
Fail closed without a silent classical-only downgrade.
If runtime identity, provider or dependency trust, PQC self-tests, handshake transcript, active session, strict sequence, semantic binding, worker ownership, or safe recovery cannot be established, a protected route does not enter its handler.
Public routes may remain available under application policy. This distinction lets operators preserve an explicitly public health surface without treating an unavailable protection runtime as permission to bypass protected controls.
Threat boundary and limitations
| Surface | Representative condition | Control location |
|---|---|---|
| Admission | Malformed, oversized, or smuggling-shaped input | Admission gate |
| Session | Expired or cross-session reuse | Session engine |
| Sequence | Duplicate, rollback, gap, or race | Atomic sequence gate |
| Native files | TOCTOU, symlink, junction, reparse, dependency injection | Platform adapter and runtime trust |
| Lifecycle | Stale lease, crash, early shutdown | Lifecycle controller |
Release & verification
The security model above is tied to a specific verified release scope, not every environment.
Current artifact identity, supported platforms, SHA-256 values, validation results, advisories, and maintenance status are maintained in the Trust Center.
Continue from the security review.
Read the operating documentation, explore the 14-day free trial, or review commercial licensing.