Notifications
Clear all
Topic starter
04/07/2026 10:17 pm
TL;DR: Twine says its participation in Anthropic’s Cyber Verification Program adds an independent check for defensive AI security work, where real-time cyber safeguards block risky model use by default and verified organisations can pursue bounded dual-use tasks, according to Twine Security. That matters because trust in agentic AI now depends on inspectable mechanisms, not vendor assurances.
NHIMG editorial — based on content published by Twine Security: Twine Is Anthropic Cyber Verified Raising the Bar for Trusted AI Identity Operations
Questions worth separating out
Q: How should security teams govern AI systems that perform identity work?
A: Security teams should separate model trust from execution trust.
Q: Why do AI identity workflows need both verification and approvals?
A: Verification answers whether the model is allowed to support defensive cyber work.
Q: What do organisations get wrong about trusted AI in security operations?
A: They often collapse trust into a single vendor claim or a single approval step.
Practitioner guidance
- Define separate control planes for model and action trust Document which decisions belong to the frontier model provider, which belong to the workflow owner, and which remain with human approvers.
- Gate dual-use identity tasks behind explicit defensive justification Require a documented defensive purpose before allowing AI to perform threat modelling, attack-path analysis, or abuse simulation.
- Keep per-action autonomy bounded and reversible Set task-level autonomy settings so the AI can only execute within predefined scopes, and make approvals mandatory for high-impact identity changes.
What's in the full article
Twine Security's full post covers the operational detail this post intentionally leaves for the source:
- How Twine’s control membrane sets per-action autonomy and approval boundaries for Alex.
- How Anthropic’s Cyber Verification Program scopes verified defensive use at the model layer.
- How the organization-based verification process works, including application, review, and appeals.
- How Twine frames auditability and traceable reasoning for AI digital employee actions.
👉 Read Twine Security’s analysis of Anthropic Cyber Verification for trusted AI identity operations →
Anthropic cyber verification for AI identity operations: what changes?
Explore further
04/07/2026 10:21 pm
Layered AI trust is now a control design problem, not a branding claim. The article shows that model-layer verification and action-layer governance answer different questions. Anthropic controls what the model may do, while the vendor controls what the AI employee may execute. Practitioners should treat those as separate evidence requirements, not substitute assurances.
A few things that frame the scale:
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities, according to The State of Non-Human Identity Security.
- Lack of credential rotation is cited as the top cause of NHI-related attacks by 45% of organisations, followed by inadequate monitoring and logging at 37% and over-privileged accounts at 37%.
A question worth separating out:
Q: How can teams evaluate whether an AI vendor is safe for identity operations?
A: Ask which layer is controlled externally, which layer is controlled by your team, and how each layer is audited. If the vendor cannot separate model safeguards from workflow authority, the organisation may be treating a capability label as a governance model.
👉 Read our full editorial: Anthropic cyber verification changes trusted AI identity operations
