---
title: "The security review pack"
description: "The evidence a security review asks for, how to generate it from a team's own data, and which enterprise terms are contract content rather than product."
---

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

# The security review pack

The pack is generated from the team's own records, so it describes what is true now rather than what a document promised once. It contains identifiers and counts only: no token, no key, no memory text and no request body.

## What it contains

| Evidence | Where it comes from |
| --- | --- |
| The audit log, verified | [`audit export`](/cli/enterprise-audit-export/) and [`audit verify`](/cli/enterprise-audit-verify/): every row with its hash, a manifest, and an offline check. |
| What agents did and what was refused | The evidence pack counts the audited actions taken by agent tokens, by action, and how many were denied. |
| Controls and their state | Single sign-on, directory sync, the tamper-evident log, the SIEM stream, data region, customer-held keys, retention and the MCP allowlist, each shown as enabled or not configured with the fact behind it. |
| Where data is held | The [store-location check](/enterprise/data-region/): every store, the region it holds. |
| Restores work | The [restore drill](/enterprise/retention-and-deletion/) report: expected and restored counts per table. |
| Purges ran | The purge reports of [retention](/enterprise/retention-and-deletion/). |
| Keys are not exposed | The [bring-your-own-key](/enterprise/byok/) scan result: aliases and states only. |

The controls are named after the trust criteria they support (for example CC6.1 for single sign-on and CC7.2 for the audit log); they are an index into the evidence, not an attestation.

Fetch the pack with `GET /v1/tenants/{tenantId}/enterprise/evidence-pack`. An agent token for the team can fetch it, and it is included from the Business plan up.

## The MCP allowlist

With the allowlist on, a team's agents may connect only to the MCP servers you list, by host or by a subdomain of a listed host. Anything else is refused by the gateway before a connection is made. The list is edited in the same settings or with `PUT /v1/tenants/{tenantId}/enterprise/mcp-allowlist`, and each change is in the audit log.

```json
{ "mode": "allowlist", "entries": [{ "server": "mcp.example.com" }] }
```

## Contract content

An SLA, a dedicated region, a security review call and an on-call contact are terms in the Enterprise contract. They are not product features, so no command or setting changes them. Accepting legal terms is always a person's own act.

Source: https://docs.overlane.app/enterprise/security-review-pack/index.mdx