This program is a pain and complex. I had similar problems but went through support. Here’s a very long post explaining how to troubleshoot.
I'm seeing three block scenarios.
1) You were accepted into the CVP, but the approval isn't applied to the account you're actually using.
CVP approval is tied to a specific organization ID, not to you as a person. If you're working in your personal workspace instead of the org that was approved, you get default safeguards. Compare the org ID where you're seeing blocks with the one on your approval email.
For API and Console-based access, approval arrives as a program (grant) on your org, and it does nothing until an org Admin or Owner assigns it to a workspace under Settings > Programs and sets it to Active. Some programs can't be assigned to the default workspace, so you may need a dedicated one. Check the workspace's Qualifications panel for unmet requirements. Some programs also have seat caps, and if the org goes over, assigned workspaces lose access until you're back under the limit. On Enterprise plans the program is assigned through custom roles, so make sure your users are actually in that role.
Also check how you're reaching Claude.
Bedrock support is very limited right now, Google Cloud requires data retention to be configured for every project, region, and model combination, and third-party tools only get CVP if that platform participates. The program generally requires data retention, so Zero Data Retention orgs can be excluded.
2) You have Defense Access, but you're doing offensive work.
The tiers are scoped to the work you're authorized to do. Defense Access covers defending systems your org owns or maintains: SOC and incident response, malware analysis, and vulnerability validation. Pen testing and red teaming require Red Team Access. Anthropic's own testing shows how big the gap is. On their CyScenarioBench evaluation of multistage cyber operations, Defense Access blocked 46 of 50 trials. Red Team Access blocked none. If you're running an engagement on Defense Access, the blocks are expected behavior.
Two things catch people here. Red Team Access is for organizations only, so individual applicants can only get Defense. And if your org applied for Red Team, you're enrolled in Defense while that review runs, which takes weeks. Plenty of people who think they have Red Team access are still on Defense.
3) You legitimately have Red Team Access and still get blocked.
The usual causes:
- Prohibited use is blocked at every tier. Ransomware deployment, mass data exfiltration, and actions that could harm people or cause widespread disruption stay blocked no matter what.
- Wrong model. The CVP covers Opus 5.5, Sonnet 5.5, and Mythos 5.1. Fable 5.1 is not a part of the CVP.
- Wrong workspace or credential. Red Team Access comes with business verification, phishing-resistant authentication, and credential and seat controls. The program only applies to traffic from workspaces that meet its requirements, so a script using a credential scoped to another workspace gets default behavior.
- The classifiers aren't perfect. Anthropic says plainly that approved users may still hit blocks on legitimate work.
If you've ruled all of that out, file a report or appeal here:
claude.com/form/cyber-block-…
Include the org ID, workspace, model, and roughly when it happened. That data is what they use to tune the classifiers.
Useful references:
- Cyber safeguards and CVP:
support.claude.com/en/articl…
- Assigning a program to a workspace:
support.claude.com/en/articl…