Security
Scoped access, evidenced action, and isolated runtime environments, built into the constitutional runtime and evidence control layer.
ETHRAEON operates as a constitutional runtime and evidence control layer over intelligence infrastructure. Security is the governance boundary built into that runtime. It separates ungoverned inference from evidenced, scoped, replayable action, so every model call runs inside the controls that produce the audit record.
Access Control
Scoped Credentials
Every credential is scoped to the minimum surface it needs. No shared root tokens. No pan-account bearers. Rotation cadence and revocation authority named per credential class.
Multi-Factor Authentication
MFA enforced on operator surfaces, admin dashboards, and any credential mint or rotation. Sovereign clicks and biometric gates preserved as irreducible acts.
Least Privilege
Runtime processes receive the narrowest capability set that satisfies their function. Broad grants are rejected in review. Widening a grant is an evidenced event.
Audit and Evidence Layer
The evidence ledger is append-only. It records every governed action, every runtime state transition, and every artifact hash under a chain root anchor. Evidence is the primary security control, captured as each action happens and verifiable from the ledger.
- Append-only receipts on the evidence chain, one receipt per governed action, hash-linked to prior state.
- Artifact SHA-256 capture on every published asset, worker deployment, and evidence file.
- Merkle-verified periodic anchoring across major cycles, verifier reruns on every governance CI pass.
- Structured redaction rules for private and personal content prior to publication.
Secret Management
Environment Isolation
Production, staging, and local secrets are strictly partitioned. No cross-environment reuse. Environment variables are the only injection surface; no secrets embedded in source or committed artifacts.
Rotation and Revocation
Rotation runs on a scheduled cadence as routine operational discipline. Revocation on credential compromise executes as a single action. Both are evidenced under the same append-only ledger.
Sovereign Vault
Long-lived operator credentials live in a biometric-gated sovereign vault. Extraction of a credential is an evidenced act with a per-item scope.
Deployment Review
Every deployment path enforces a governance boundary. Nothing reaches a public surface without passing content-safety, compliance, and evidence-capture gates. Deployments are reversible by construction: previous versions remain retrievable, and rollbacks are one action.
- Governance CI gates: forbidden-phrase scans, patent-count consistency (16 filed U.S. provisional applications / 75 technical specifications / 9 families), stale-data detection, evidence-chain health.
- Preview and production separation. Preview URLs are non-official and time-limited.
- Signed and hash-anchored artifacts for downloadable materials.
- Deploy verify: post-deploy live-body checks, not preview URL assumptions.
Runtime and Environment Isolation
Private Boundary
Private runtime environments are isolated from public surfaces. Every boundary crossing is governed and evidenced, and public deployments cannot read private state.
Edge Enforcement
Edge workers enforce content and access boundaries before origin. Rate limits, header enforcement, and route-level authentication live at the edge, closest to the caller.
AI Governance Boundary
Model calls are wrapped by the governance layer. Prompt-injection attempts and tool-abuse patterns are detected and refused at the governance wrapper, before any request reaches the model.
Incident Response
Incident response is a defined operational discipline. Classification, containment, evidence capture, remediation, and post-incident review are all evidenced under the same append-only ledger.
- Immediate containment: credential revocation, deploy freeze, edge rule tightening.
- Evidence preservation: no in-place mutation of affected artifacts, hash-anchored snapshots.
- Root cause: reproduction in an isolated environment before remediation is drafted.
- Post-incident receipt written to the evidence ledger, with named failed tests and remediation actions.
Report a suspected security issue via contact.ethraeon.ai (topic: security). Responsible disclosure appreciated; safe-harbor for good-faith research.
Compliance Mapping
SOC 2
Self-certified against SOC 2 Trust Services Criteria. No third-party audit claim. Public posture updated as external attestation completes.
ISO 42001
Readiness-mapped against the AI Management System standard. The governance boundary, evidence ledger, and environment isolation align to the standard's control families.
Schedule A+
Enhanced IP Firewall applied across all published materials, patent-count consistency enforced at governance CI, ORCID-anchored provenance.
Learn More
Compliance surface for the readiness-mapped standards inventory. SLA for the operational commitments. Trust center for the public governance stance. Papers for the architectural rationale.