Security Guide¶
J7M places enforcement at the host, transport, application boundary and durable-resource boundary. An application annotation describes a requirement or selects an authorized policy; it cannot manufacture trust, credentials or isolation.
Start with identity and trust, configure TLS and certificates, then establish application signing and secret handling. Review isolation and audit against the actual deployment boundary.
| Boundary | What must be established |
|---|---|
| Transport | Authenticated peer, appropriate confidentiality and a bounded protocol |
| Registry | Expected context plus valid, live publisher records under a configured verifier |
| Application activation | Verified artifact, allowed capabilities, policy identities and module origins |
| Invocation | Authenticated caller, required role/permission/trust domain and current context |
| Native resource | Server-bound principal/scope, current receipt/fence/epoch and permitted operation |
| Administration | Explicit administrative admission and permission, separate from application service access |
Security controls must remain active on cache hits, replayed durable results and generated adapter paths. A previously successful result does not grant a newly unauthorized caller access to it. Likewise, transport authentication does not prove application-artifact provenance.
The deployment owner must choose trust roots, credential sources, key rotation procedures and host/process isolation. Development defaults are not a production security profile. The examples explain the middleware mechanisms; they do not replace an environment-specific security assessment.
Operational security¶
- Production hardening: validate declared deployment controls against observed configuration.
- Administrative PINs: source selection, protected verifier persistence, throttling and confirmation.
- Credential rotation: provider notifications, transport refresh and rollback.
- Isolation providers: actual enforced, policy-only and advisory boundaries.
- Audit verification and retention: retained-chain checks and external immutable storage.
- Security incident recovery: registry poisoning, emergency deny and restored trust.
- Enterprise integrations: evidence, crypto, external policy and approval contracts.