Skip to main content
Ankra has a compliance management layer built into the platform. It continuously measures your clusters against recognised benchmarks, governs the exceptions you grant against them, and exports the result as evidence. That combination is what an information security management system needs from a technical control: not a one-off scan, but a control that is monitored on a cadence, exceptions that carry an owner and an expiry, and a record that survives the audit. This page covers the compliance layer as a management system. The interface mechanics live in Cluster Security.

Continuous control monitoring

Ankra reads four benchmark specifications from every managed cluster that runs the scanner. For each cluster and benchmark Ankra keeps the pass count, the fail count and the failed checks, with the configuration-audit failures beside them. The portal has no page for the benchmark results. Read them with the CLI, or from an MCP client with get_security_compliance_overview (the whole fleet) and get_compliance_reports (one cluster):
A cluster the scanner does not run on, or whose agent could not be reached, reads not_available with the reason, never as passing, and the summary line counts it as without compliance data. To an assessor an unscanned cluster is a coverage gap, so it is shown as one. In the portal, Security → Coverage shows which clusters have a current scan and which need a fresh report.
Scanning runs inside your cluster through Trivy Operator and only findings metadata reaches the platform. Ankra is the aggregation and retention layer, not the scanner.

Framework evidence

Ankra maps what it observes to control frameworks and records the result every day. Open Security → Evidence (/next/security?tab=evidence). The Frameworks table lists each framework with three counts: Needs review, Needs your evidence and Passed. HIPAA collects no evidence: its row opens a mapping guide in place of a report. Turn a framework on. A framework records nothing until someone with security.manage turns it on. Click Enable ISO 27001 evidence (the button names the framework), then Enable evidence collection in the dialog. A member without the permission reads “A security manager can enable collection.” The CLI twin is ankra security compliance frameworks enable <framework-key>. From then on Ankra records one snapshot a day, and the Evidence period list offers Current observations and every month with a recorded snapshot. Read a control. Each control has a status: The automated checks behind the controls are these. Each control in a framework report names the checks it uses. Export it. Click Export evidence, pick the Export framework and the Export period, then download: The export holds the selected framework period and the current page of the SBOM image inventory, with its search filters. The screen states what it holds: “Observed metadata only, not raw logs or credentials.” A download records no delivery. Send it to a destination. To have Ankra deliver the evidence and record each send, open Connect a destination, choose a Destination type (Signed webhook or Wazuh relay), give it a Name and an HTTPS endpoint, and click Connect destination. The webhook signing secret or relay bearer token is stored in the platform’s secret store and never shown again. Each delivery reads Queued, Retrying, Accepted by the receiver, Failed or Stopped after retries. Connecting destinations and sending evidence needs security.manage. A Vanta document as a destination is closed beta; the PDF download works without it.
The evidence export is not the compliance report below. The evidence export carries one framework’s controls and the image inventory; the compliance report carries posture, findings, dispositions, the audit summary and the attestation for a date window.

Governed exceptions

Every real control set has exceptions. What separates a managed exception from an unmanaged one is that somebody owns it, justified it, and agreed to look at it again. Ankra enforces that shape rather than leaving it to convention. Findings carry two distinct dispositions: Accepting risk requires a reason, an actor recorded in the audit trail, and a review deadline of at most one year. You can also have the acceptance expire automatically the moment a fix becomes available, so an exception granted because nothing could be done ends as soon as something can. This is the behaviour a risk register is supposed to have. The register cannot silently accumulate permanent exceptions, because the platform will not accept one without an expiry. An accepted risk with no deadline is refused with “Accepted risk requires a review deadline”, and one further out than a year with “Accepted risk review deadline cannot exceed one year”. The register is Security → Accepted risks (/next/security?tab=decisions): who accepted each risk, why, and when the decision comes back. Each entry is marked Accepted risk or Acknowledged, and a member with security.manage can Extend, Revoke, Reopen for fixing or keep it (Keep accepted, Keep acknowledged).

Policy lifecycle

Accepted risks become organisation-wide policies with a lifecycle you can review, rather than one-off suppressions that are impossible to audit later. Policies are tracked as active, expiring, fix-available, mitigated, unmatched, expired or revoked, and the Security overview surfaces those nearing review so the next review is prompted rather than remembered. Matching is deterministic - organisation, add-on, CVE, package type and package name - and creating a policy always shows a server-side preview of exactly which findings it will affect before you commit. Policies are never hard-deleted. They are revoked, they expire, they mitigate when no matches remain, or they reopen if the findings return. That means the history of what was excluded, and when, stays intact. The register is reachable without the browser: ankra security dispositions lists the policies by lifecycle state, ankra security dispositions preview and create write a decision after showing the server-side match preview, and update / revoke carry the lifecycle - every one against the token API, so an auditor’s script and an engineer’s terminal see the same record the portal does. From chat or the MCP server the tools are list_security_dispositions, preview_security_disposition, create_security_disposition, update_security_disposition and revoke_security_disposition; the writes are confirmed before they run and enforce the same three permissions.
Expiry or a newly available fix can make findings actionable again and may fire threshold alerts. This is the control working as intended, but plan for it: a batch of acceptances expiring in the same week produces a spike in actionable findings.

Segregation of duties

Three permissions separate looking from triaging from accepting risk, so the person who grants an exception need not be the person who investigates one. All three can be attached to custom roles. Enforcement is server-side, and every disposition change is written to the audit trail in the same transaction as the change itself, so the record cannot drift from the action.

The compliance report

The report is the export that carries the state above out of the platform in one document. The portal has no button for it: download it with the API or the CLI, or pull it on a schedule:
Both json (default) and csv are supported, and the date range bounds the audit-activity section. The same download is ankra security compliance export --format json --start-date 2026-07-01 --end-date 2026-07-31 --output-file compliance-report-july.json from the terminal; the framework switches and reports behind it are ankra security compliance frameworks, frameworks enable|disable <key> and frameworks report <key> --month 2026-07.
The report requires both the security read and audit read permissions, and names the missing one in the 403 if you hold only one. That is deliberate: it combines posture with audit activity, so it should not be obtainable with half the access.

How this maps to an ISMS

If you run a management system to ISO/IEC 27001 or an equivalent framework, the compliance layer supplies specific inputs to it. It does not replace the system. What remains yours: the scope statement, the risk assessment methodology, the Statement of Applicability, policy documents, internal audit, and management review. Ankra evidences a set of technical controls well; it is not the management system itself.

Building an audit response

1

Establish coverage

Show which clusters are managed and which are reporting. Non-reporting clusters are visible in Security → Coverage, in ankra security compliance and in the attestation section. Coverage gaps are the first thing an assessor tests.
2

Show the controls are configured

Point at the attestation flags, the benchmark results and the framework report in Security → Evidence. This demonstrates control design.
3

Show they operated across the period

Attach posture snapshots over the audit window and the audit export for the same window. Configuration proves design; the trail proves operation.
4

Show exceptions were governed

The dispositions section records what was accepted, by whom, and when it expires. A managed exception has an owner and a review date. An unexplained open finding does not.

Limits worth stating up front

  • Ankra evidences the clusters it manages. Clusters outside Ankra are outside this evidence, and an assessor will ask about them.
  • Benchmark results come from the scanner. Ankra ingests and retains Trivy Operator’s output; it does not grade it. The authority for a check is the benchmark specification, and a cluster without the scanner produces no result.
  • Benchmarks are not your whole control set. CIS, NSA/CISA and PSS cover Kubernetes configuration. They say nothing about your application controls, your suppliers, or your people.
  • Nothing here certifies your environment. The platform produces evidence; your assessor draws the conclusion.

Ankra’s own compliance posture

Everything above concerns your environment. A separate question comes up in procurement: what is Ankra’s own certification status? Ankra runs an internal information security management system covering the platform. The current, honest state of that work is published at ankra.ai/trust, alongside the sub-processor and hosting list.
Take Ankra’s certification status from ankra.ai/trust or from us directly, never from this documentation. That page is the single source of truth and it changes as the programme progresses.
For how Ankra’s posture does and does not affect the scope of your own certification, see Shared Responsibility.

Cluster Security

The Security Center interface, findings and dispositions.

Security Reports

Scheduled posture reports as review evidence.

Audit Export

The administrative trail for the same period.

Change Management

Pre-approved standard changes for control 8.32.

Shared Responsibility

What Ankra is and is not accountable for.