> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit-Ready Evidence for ISO 27001 and SOC 2

> Collect ISO 27001 and SOC 2 evidence from Ankra - turn on framework evidence, close the gaps it finds, and export what an auditor asks for.

An ISO 27001 or SOC 2 audit asks two things of your Kubernetes estate: that the technical controls are designed right, and that they operated over the audit period. Ankra already records much of the answer - who signed in and changed what, which clusters are scanned, which risks were accepted and until when. This tutorial turns that record into an evidence pack.

You end up with ISO 27001 and SOC 2 evidence collecting every day, the gaps it found closed or owned, and one folder per audit period: the framework report, the compliance report and the audit log for the same window. Plan about 30 minutes for the first pass.

> [!WARNING]
>
> Ankra produces evidence about the infrastructure it manages. It does not certify your environment, and it does not cover your application controls, suppliers or people. The portal says the same: "Recorded infrastructure observations support an audit. They do not establish certification or application-level controls." For Ankra's own certification status, see [ankra.ai/trust](https://ankra.ai/trust).

## Before you start

* **Permissions.** Turning a framework on needs `security.manage`. The compliance report needs both `security.read` and `audit.read`, and the audit log export needs `audit.read`; owners and admins hold all of them. A compliance function can get them through a [custom role](https://docs.ankra.ai/guides/roles-and-access.md) without broader admin access.
* **Clusters connected and scanned.** The vulnerability checks read the findings of the [security baseline](https://docs.ankra.ai/guides/cluster-security.md#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](https://docs.ankra.ai/integrations/ankra-cli.md).

## 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.

> [tab] Portal
>
> 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.

> [tab] CLI
>
> ```bash theme={null}
> ankra security compliance frameworks enable iso27001
> ankra security compliance frameworks enable soc2
> ankra security compliance frameworks
> ```

**Check:** the two rows now show the counts **Needs review**, **Needs your evidence** and **Passed** instead of **Not collecting**. From now on Ankra records one snapshot a day, and each month with a snapshot becomes a choice under **Evidence period**.

## 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.

| ISO 27001:2022 control | Ankra's automated checks |
| - | - |
| A.5.7 Threat intelligence | Exploit intelligence feed is current |
| A.5.25 Assessment of security events | Severe findings triaged within 30 days |
| A.5.28 Collection of evidence | Audit trail actively recording |
| A.8.2 Privileged access rights | Multi-factor authentication required, No dormant API tokens |
| A.8.5 Secure authentication | Multi-factor authentication required, Every member enrolled in multi-factor |
| A.8.7 Protection against malware | Security baseline enforced |
| A.8.8 Management of technical vulnerabilities | Critical vulnerabilities remediated, Known-exploited vulnerabilities remediated, Vulnerability scanning covers every cluster |
| A.8.13 Information backup | Verified backup vault available |
| A.8.15 Logging | Audit trail actively recording |
| A.8.16 Monitoring activities | Vulnerability scans are current |
| A.8.24 Use of cryptography | Secrets encryption initialised |
| A.8.32 Change management | Configuration managed from Git |
| A.5.1 Policies for information security, A.6.3 Security awareness and training | None: owner evidence |

| SOC 2 criterion | Ankra's automated checks |
| - | - |
| CC6.1 Logical access security measures | Multi-factor authentication required, Every member enrolled in multi-factor |
| CC6.2 Credentials issued and removed | No dormant API tokens |
| CC6.6 Protection against outside threats | Known-exploited vulnerabilities remediated, Exploited-vulnerability deadlines met |
| CC6.7 Protection of data in transmission and at rest | Secrets encryption initialised |
| CC7.1 Vulnerability detection and monitoring | Vulnerability scanning covers every cluster, Vulnerability scans are current |
| CC7.2 Anomaly monitoring | Runtime anomaly monitoring |
| CC7.3 Evaluation of security events | Severe findings triaged within 30 days |
| CC7.4 Incident response | Critical vulnerabilities remediated |
| CC7.5 Incident recovery | Verified backup vault available |
| CC8.1 Authorised infrastructure changes | Configuration managed from Git, Security baseline enforced, Audit trail actively recording |
| A1.2 Recovery infrastructure | Verified backup vault available |
| A1.3 Recovery plan testing | None: owner evidence |

What each check measures is in [Compliance Management](https://docs.ankra.ai/security/compliance-management.md#framework-evidence).

**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.

| Failed check | Where to fix it |
| - | - |
| Multi-factor authentication required | **Identity & access → Sign-in and security**, switch **Require a second step for everyone**. See [Account Security & 2FA](https://docs.ankra.ai/platform/account-security.md) |
| Every member enrolled in multi-factor | The same page lists who has no second step |
| No dormant API tokens | Revoke tokens unused for 90 days under **Identity & access → API and automation**. See [Service Tokens](https://docs.ankra.ai/guides/service-tokens.md) |
| Secrets encryption initialised | Initialise [SOPS](https://docs.ankra.ai/guides/sops.md) for the organisation |
| Configuration managed from Git | Connect each cluster to a [GitOps repository](https://docs.ankra.ai/concepts/gitops.md) |
| Verified backup vault available | Add and verify a [backup vault](https://docs.ankra.ai/concepts/backup-vaults.md) |
| Security baseline enforced | **Identity & access → Sign-in and security**, section **New clusters**, switch **Security baseline on new clusters**. See [Cluster Hardening](https://docs.ankra.ai/security/hardening.md) |
| Vulnerability findings checks | Fix the findings from **Security → Overview**, or accept the risk (below). See [Cluster Security](https://docs.ankra.ai/guides/cluster-security.md) |

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](https://docs.ankra.ai/security/compliance-management.md#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.

> [tab] Portal
>
> 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.

> [tab] CLI
>
> ```bash theme={null}
> ankra security compliance frameworks report iso27001 --month 2026-10 -o json > iso27001-2026-10.json
> ankra security compliance frameworks report soc2 --month 2026-10 -o json > soc2-2026-10.json
> ```

**Check:** the file names the framework and the period you chose, and its controls match what the report showed on screen.

## 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.

```bash theme={null}
ankra security compliance export --format json \
  --start-date 2026-10-01 --end-date 2026-10-31 --output-file compliance-2026-10.json

ankra org audit-logs export --format json \
  --since 2026-10-01 --until 2026-10-31 --file audit-2026-10.json
```

In the portal, the audit log export is **Identity & access → Audit log → Export**; see [Audit Export](https://docs.ankra.ai/security/audit-export.md). The compliance report has no portal button: use the CLI or the API route in [The compliance report](https://docs.ankra.ai/security/compliance-management.md#the-compliance-report).

**Check:** both files are written. One audit export holds up to 100,000 rows, and the CLI says so on stderr when an export hit that cap; if it did, export shorter windows.

## 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](https://docs.ankra.ai/guides/service-tokens.md) that holds `security.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:

```bash theme={null}
ankra security evidence deliveries send --destination <destination-id> --framework iso27001 --month 2026-10
ankra security evidence deliveries list
```

## What an auditor asks, and where the answer is

| The auditor asks | Where the answer is |
| - | - |
| Is MFA enforced for everyone? | The attestation in the compliance report, and the check "Multi-factor authentication required" |
| Who has access, and at what scope? | **Identity & access → People** and **Roles**; [Identity & Access Controls](https://docs.ankra.ai/security/identity-and-access.md#evidence-map) |
| Who reached production clusters with `kubectl`? | `ankra security access --cluster <cluster>` for standing grants, and the access entries in the audit log |
| How do leavers lose access? | [Single sign-on](https://docs.ankra.ai/guides/single-sign-on.md) re-verification, and the `sso_member_suspended` entries in the audit log |
| Which changes reached production, and who approved them? | Git history for desired state, and the reviews on your pull requests. Each audit entry is classified as a pre-approved [standard change](https://docs.ankra.ai/security/change-management.md) or a normal change; Ankra does not check who approved a normal change |
| Are vulnerabilities found and fixed on time? | The framework report's vulnerability checks, and the findings section of the compliance report |
| Which risks did you accept, and who owns them? | **Security → Accepted risks**, and the dispositions section of the compliance report |
| Are all clusters covered? | **Security → Coverage**, and the scanner list in the attestation |
| Can you restore? | The backup check, plus your own restore tests: A.8.13 and A1.3 need evidence that you tested a restore |
| What did your vendor's staff do in your organisation? | **Identity & access → Ankra support access**, and the `support_session_*` audit entries; see [Ankra Support Access](https://docs.ankra.ai/security/support-access.md) |
| Is Ankra itself in scope? | [Shared Responsibility](https://docs.ankra.ai/security/shared-responsibility.md) |

## 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 both `security.read` and `audit.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](https://docs.ankra.ai/guides/cluster-security.md#the-security-baseline) on each cluster.

## Next steps

* [Compliance Management](https://docs.ankra.ai/security/compliance-management.md) - the controls, statuses and exports in detail.
* [Audit Export](https://docs.ankra.ai/security/audit-export.md) - every column of the audit export, and feeding it to a SIEM.
* [Security Reports](https://docs.ankra.ai/guides/security-reports.md) - scheduled posture reports for management review.
* [Shared Responsibility](https://docs.ankra.ai/security/shared-responsibility.md) - where Ankra's responsibility ends and yours begins.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.