Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

AI adoption inside security teams is now near-universal. Tines' Voice of Security 2026 report found that 99% of SOCs use AI in some capacity. What hasn't kept up is the policy that's supposed to govern it. ISACA's 2026 AI Pulse Poll found 56% of digital trust professionals don't know how quickly they could shut AI down after a security incident. The policy was supposed to handle this.

As businesses adopt more cloud applications, managing user access securely has become increasingly complex. Employees today use dozens of applications for communication, collaboration, development, HR, finance, and customer management. This creates a major challenge for IT teams: balancing security with a seamless user experience. To solve this problem, organizations typically evaluate two technologies: Single Sign-On (SSO) and password managers. In this guide, we’ll cover.

Imagine onboarding a new employee, contractor, or partner without creating accounts manually for every application. That’s exactly what Just-in-Time (JIT) provisioning enables. Instead of relying on slow, manual onboarding workflows, JIT provisioning automatically creates user accounts the moment users log in through SAML SSO. As organizations adopt more cloud applications and remote work models, automated user provisioning has become essential for scalable Identity and Access Management (IAM).

The Cyber Resilience Act (CRA) is an EU regulation that sets binding cybersecurity requirements for any "product with digital elements" placed on the European Union market. It is the first horizontal EU law that holds manufacturers accountable for the security of hardware and software throughout the entire product lifecycle—from design to end-of-support.

As organizations scale Anthropic’s Claude model across their workforce, they need the same level of auditability around AI platform activity that they expect from every other enterprise application. A new integration with the Claude Compliance API brings Claude activity into the CrowdStrike Falcon platform to deliver real-time visibility, detection, and automated response for AI use.

Today, we are extending Cloudflare’s cloud access security broker (CASB) to support the Claude Compliance API. Security and compliance teams can now monitor Claude usage directly in the Cloudflare dashboard. No endpoint agents required. Enterprise security teams have long struggled to see how users interact with sanctioned and unsanctioned applications. The rapid adoption of AI applications has made this harder.

In July 2025, Replit's autonomous AI coding agent deleted a live production database despite being explicitly instructed to freeze all changes. The agent then attempted to reassure the user with incorrect information after the fact. The team had safeguards in place. The instructions were explicit. Neither stopped it. The conclusion that follows is one the security community should take seriously: you cannot enforce AI agent behavior through the agent itself.

See how Torq harnesses AI in your SOC to detect, prioritize, and respond to threats faster. Request a Demo Noam Cohen is a serial entrepreneur building seriously cool data and AI companies since 2018. Noam’s insights are informed by a unique combination of data, product, and AI expertise — with a background that includes winning the Israel Defense Prize for his work in leveraging data to predict terror attacks.

Artificial intelligence is rapidly reshaping how security operations centers (SOCs) function. Many organizations are now evaluating AI-native architectures to reduce workload and accelerate investigations. A new architectural narrative is emerging. A growing set of AI-native security vendors are proposing centralizing telemetry in a warehouse and deploying AI agents to replace the operational role of the SIEM. They want to centralize telemetry, apply AI, and automate the SOC.

Our previous post, How to Secure Microservices with SPIFFE and Istio, showed how to secure Kubernetes microservices using Istio policy and SPIFFE identities, with Teleport issuing the identities that the mesh trusts. The question teams face next is: How do you extend that identity-driven security model to workloads outside Kubernetes — such as VMs, edge gateways, and legacy services — without creating a massive certificate-management project?