Before you start
- Permissions. Turning a framework on needs
security.manage. The compliance report needs bothsecurity.readandaudit.read, and the audit log export needsaudit.read; owners and admins hold all of them. A compliance function can get them through a custom role without broader admin access. - Clusters connected and scanned. The vulnerability checks read the findings of the security baseline. A framework report for an organisation with no scanned cluster fails those checks rather than passing them.
- The Ankra CLI, version 0.74.0 or later, if you want the command-line steps. See Ankra CLI.
1. Turn on ISO 27001 and SOC 2 evidence
A framework records nothing until it is turned on, and the record starts on that day: turn it on before the audit period starts.- Portal
- CLI
Open Security → Evidence (
/next/security?tab=evidence). The Frameworks table lists ISO 27001, SOC 2, NIST CSF, GDPR and HIPAA. On the ISO 27001 row click Enable ISO 27001 evidence, then Enable evidence collection in the dialog. Do the same for SOC 2.2. See which controls Ankra gives evidence for
Click ISO 27001 in the Frameworks table. The report leads with the controls that need review; Controls by category holds the rest. A control backed by automated checks reads Automated checks passed, Needs review or Evidence gap. A control with no automated check reads Owner evidence needed: Ankra lists it, and you attach the evidence in your audit system.
What each check measures is in Compliance Management.
Check: every control in the report has one of the statuses above. A control that reads Not recorded has no snapshot for the period you chose.
3. Close the gaps the checks found
Open each control under the review list: it names the first check that failed and what that check found. Fix it where the setting lives, or accept the risk with an owner and a date.
A finding you decide not to fix is accepted with a reason and a review deadline of at most one year. It then appears under Security → Accepted risks with who accepted it, why, and when it comes back. See Governed exceptions.
Check: click Refresh evidence on the framework report. The controls you fixed read Automated checks passed.
4. Export the framework evidence for the period
Do this once the audit period has closed, for each month in it.- Portal
- CLI
On the framework report click Export evidence. Pick the Export framework (ISO 27001 or SOC 2) and the Export period (a recorded month, or Current observations), then click Download PDF for a document to attach, or Download JSON for your archive.
5. Export the compliance report and the audit log for the same window
The framework report shows the controls. The compliance report and the audit log show they operated: cluster posture, findings, accepted risks, the attestation (MFA required, SOPS initialised, baseline on, which clusters are scanned), and every administrative action in the window.6. Keep the record
The audit log is kept for a year. An audit that looks further back needs your own copy, so run step 5 on a schedule, with a service token that holdssecurity.read and audit.read, into storage you control.
For framework evidence, connect a destination under Security → Evidence → Export evidence → Connect a destination (Signed webhook or Wazuh relay). Each send is then recorded with its retries and outcome. From a scheduled job:
What an auditor asks, and where the answer is
What can go wrong
- “A security manager can enable collection.” Your role lacks
security.manage. Ask an owner or admin to turn the framework on. - A month is missing from Evidence period. No snapshot was recorded in that month, usually because the framework was turned on later. Evidence starts on the day you turn a framework on and cannot be backfilled.
- HIPAA shows a guide, not a report. HIPAA collects no evidence in Ankra; its row opens a mapping guide.
- The compliance report is refused with a
403. It needs bothsecurity.readandaudit.read, and the error names the one you lack. - Vulnerability checks fail on a quiet estate. A check with nothing scanned fails on purpose: an instrument that never measured is not a clean result. Turn on the security baseline on each cluster.
Next steps
- Compliance Management - the controls, statuses and exports in detail.
- Audit Export - every column of the audit export, and feeding it to a SIEM.
- Security Reports - scheduled posture reports for management review.
- Shared Responsibility - where Ankra’s responsibility ends and yours begins.