Your security team can now see how Claude is set up.

01 · What changed

What Anthropic shipped.

What changed: reviewing Claude's security settings used to mean going setting by setting across chat, Cowork and Claude Code. Claude Enterprise now has one page for that review, hooks that send prompts and tool calls to the data security tools a company already runs, one admin console at admin.claude.com for company-wide identity settings, and an Admin API call that signs a member out everywhere. In practice, Anthropic says your team keeps the policies it has already written and applies them to Claude. A prompt from a supported Claude product that pastes in a borrower's credit agreement can then go to your data security tool for a check under those same policies.

1. 1

   Security center

   A new page in Organization settings compares your chat, Cowork and Claude Code settings with Anthropic's recommended configuration. Each control shows the current value, the recommended value where there is one, and a link to change it.

2. 2

   Attestations and reports

   Admins can record the state of each control, accept risks and flag issues in one shared workspace. The page downloads as a report that marks which controls were checked automatically and which an Owner confirmed.

3. 3

   Inference hooks

   Prompt hooks send prompts to your security tool for a check, and pre-tool-call hooks check tool calls before they run. Both are generally available and work with security vendors.

4. 4

   Centralized management

   A parent organization gets its own console at admin.claude.com for single sign-on, SCIM, domain verification, groups and Compliance API keys. Companies can connect more than one identity provider, each with its own SSO and SCIM.

5. 5

   Member sign-out

   One Admin API call ends a member's sign-in sessions on every browser and device without removing them from the organization. It is in beta and does not end API keys, running cloud sessions or scheduled routines.

6. 6

   Self-managed IP allowlist

   Enterprise admins can set up and manage their IP allowlist without going through Anthropic. In the Claude Console, the allowlist is in beta and takes up to 1,000 IPv4 or IPv6 addresses or CIDR ranges per organization.

7. 7

   Claude Desktop controls

   Admins can set the most-used Claude Desktop settings with no device management push, and block personal and other outside Claude accounts on managed computers. Owners can limit which workspace folders people use with Claude.

8. 8

   EDR in Cowork

   Admins can run their organization's EDR sensor inside the Cowork virtual machine on the user's computer. The sensor reports to the console your security team already monitors.

02 · What it means

What it means for your seat.

For most firms the first gain is evidence: a single page, and a downloadable report, that shows how Claude is configured against Anthropic's recommendations. The second is reach, because existing DLP policies and EDR sensors can now see what happens inside Claude. Anthropic is clear that the security center is guidance based on its recommendations, not a certification or a guarantee of compliance with any law or standard.

03 · This week

0 of 3 done

1. 01 · Open the security center: Have an Owner open the new page in Organization settings and list each control where your value differs from the recommended one. Download the report and file it with your current security review.
2. 02 · Ask your DLP vendor about hooks: Check whether your data security vendor supports Claude's prompt and pre-tool-call hooks. If it does, plan which existing policies to apply first.
3. 03 · Decide on personal accounts: Agree whether to block personal and other outside Claude accounts in Claude Desktop on managed computers. Write down who can call the sign-out API and when, for example after a lost laptop.

The short answers.