Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Dario Amodei asking the AI race to slow down is a little rich. He is not wrong. Our AI pioneers were so preoccupied with whether or not they could, they didn’t stop to think if they should. Anthropic helped push the frontier hard, and now its CEO is warning that the pace is getting dangerous. Security people have seen this pattern. Build thing, connect thing, watch it behave in ways nobody quite expected, then go looking for controls.

There is a difference between watching data go into an AI tool and knowing what is inside it. Most security tools do the first. Few do the second. Employees now keep contracts, source code, and customer records inside their AI workspaces, in chats and projects that build up for months. Cyberhaven's integration with Claude's Compliance API brings that content into view for Claude Enterprise, and ties it back to where it came from.

A SOC analyst spots suspicious activity from an internal IP. They need to understand what is happening. They open their SIEM's built-in AI assistant and type: "Tell me about 192.168.0.10." The assistant checks the entity store. Nothing. The analyst rephrases: "This is in our environment. Can you please check the logs and walk me through what's going on with this device?" A moment later, the assistant returns a summary. The host is involved in Windows file sharing and remote administration.

41% of CISOs said an audio deepfake targeted their organization within the last 12 months, according to a new survey by Gartner. Additionally, 36% of respondents said employees were targeted by deepfake video calls over the past year. Craig Porter, Director Analyst at Gartner, noted that social engineering and human deception remain at the core of these AI-assisted attacks.

Agent Risk Manager, KnowBe4’s AI agent security product in the KnowBe4 Platform, integrates with the Claude Compliance API to help organizations monitor Claude activity and detect risks in real time. Today, that integration is featured in Claude’s Compliance API milestone announcement.

Microsoft is retiring Exchange Web Services (EWS) API. The change will happen in stages, starting in October 2026, with EWS scheduled to be fully disabled in April 2027.

Every login, every API call, and every file someone opens starts with the same two questions: who is this, and what are they allowed to do? Those questions matter more than they used to. Networks no longer have a clean perimeter, applications run across cloud and on-premises environments, and users connect from anywhere. Identity is now what decides whether a request is allowed through.

Healthcare workers move between EHRs, clinical applications, imaging systems, telehealth platforms, and administrative tools throughout the day. When every system requires separate authentication, access becomes a recurring interruption and identity management becomes fragmented. SSO for healthcare brings authentication into a centralized identity layer, allowing authorized users to access multiple applications through one authentication experience.

MSPs rarely inherit a clean slate. Whether onboarding a new client or expanding services within an existing account, providers often step into environments shaped by years of identity and access decisions made long before they became involved. Former employees may still have active accounts. Temporary administrator privileges may have quietly become permanent. Shared credentials can persist because replacing them would disrupt established workflows.

Launched in June, Keeper Privileged Cloud has delivered just-in-time, zero-standing privilege access across cloud platforms, identity providers and federated applications – including AWS IAM, Microsoft Entra ID, GCP, Okta and Active Directory. Rather than relying on shared privileged credentials, it grants temporary elevated access by modifying a user’s identity-layer membership or role assignment for an approved, time-bound window.