Compliance & audit.
SOC 2 / ISO 27001 controls, evidence assembly and an immutable audit trail with provenance.
Turn compliance from a fire drill into a feature — mapped controls, automatic evidence assembly and an immutable, queryable audit trail that answers an auditor's “why” directly.
- Category
- Identity & security
- Deployment
- Managed → air-gapped
- Governance
- IAM · encryption · audit
Compliance is a fire drill because the evidence is scattered.
The work in an audit isn't usually the controls — it's proving they were in place, every day, with evidence pulled from a dozen systems the week before the auditor arrives. Screenshots, exports, spreadsheets, a scramble. Aether collects the evidence continuously and maps it to the controls (SOC 2, ISO 27001, NIST), so the audit is a query against an always-current record rather than a month of preparation.
An immutable trail that answers 'why', not just 'what'.
The audit log isn't an afterthought; it's a tamper-evident record of every privileged action, with provenance that ties each result back to the data, the model version and the approval behind it. When an auditor — or an incident responder — asks why the system did something, the answer is a query, not an archaeology project. Because it's immutable, it's evidence, not a log that could have been edited.
On the platform, so the evidence is real, not asserted.
Most compliance tools sit outside your stack and ingest signals through connectors, attesting to what they're told. Aether's compliance runs on the same platform as the workloads, so the evidence is generated where the work happens — the access that occurred, the encryption that applied, the policy that blocked a deploy — not a second-hand claim. Controls map to real resources, and a gap is a fact about your estate, not a checkbox someone forgot to tick.
Ask the audit trail a question and get an evidence-backed answer — not a folder of screenshots.
-- Who accessed customer PII last quarter, and was it encrypted?
SELECT actor, resource, action, encryption, model_version, ts
FROM audit.events
WHERE resource LIKE 'lake.customer_pii%'
AND ts >= '2026-04-01'
ORDER BY ts; -- immutable, provenance on every rowEvery row ties an action to who did it, whether encryption applied, and which model version was involved — collected continuously, on the platform, and immutable. The auditor's question is a query; the evidence was already there.
Three steps to running.
SOC 2, ISO 27001 and NIST mapped to your resources.
Continuously, instead of a screenshot hunt before the audit.
An immutable, queryable trail with provenance for every action.
Compliance & audit, in full.
SOC 2, ISO 27001, NIST and more mapped to your resources.
Continuously collected evidence instead of a screenshot hunt.
Tamper-evident trail of every privileged action.
Every result traces to data, version and approval.
Provision it in a few lines.
Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.
# Provision compliance & audit on Aether Cloud
aether identity-security create \
--service compliance-audit \
--name app \
--region us-1 \
--deploy managed # or vpc | on-prem | air-gappedAt a glance.
- Frameworks
- SOC 2 · ISO 27001 · NIST
- Evidence
- Continuously collected
- Audit trail
- Immutable, tamper-evident
- Provenance
- Data · version · approval
- Export
- Audit-ready reports
Built for real work.
Audit readiness
Continuous compliance
Evidence for certifications
On one model, not stitched together.
The usual stack runs compliance & audit in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.
No stitching a vector DB to one place, a warehouse to another and a model to a third — compliance & audit sits next to the rest of the catalog, one identity, one bill.
The provider that runs Aether runs your compliance & audit — so the data and the model never leave the same governed boundary to talk to each other.
Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.
Good to know.
Control mapping and continuous evidence — with an immutable audit trail that traces every result to its source.
Yes — evidence is collected continuously instead of scrambled together before each audit.
Yes — provenance answers 'why' directly for every action.
Your boundary, your choice.
Pairs well with.
Fine-grained identity and access management with SSO, SCIM and short-lived credentials.
Centralized secrets with rotation, scoped access and full audit of every read.
Managed and customer-managed keys, HSM-backed, for encryption across every service.
Encryption in transit and at rest by default, with bring-your-own-key and envelope encryption.
Continuous posture management, findings and recommendations across your cloud footprint.
Policy-as-code guardrails and capability gating enforced across accounts and deployments.
Run Compliance & audit on Aether Cloud.
SOC 2 / ISO 27001 controls, evidence assembly and an immutable audit trail with provenance. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.