Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Protecting sensitive data does require investment, and that mindset hasn’t been universal. Now, it isn’t an option. It’s time to move from debate to execution.

When application traffic fails to reach its destination, teams must determine whether the problem lies in routing, firewall rules, NAT behavior, or a combination of all three. In many environments, these components overlap in ways that make traditional troubleshooting slow and error-prone. Engineers often have to run repeated tests, stage changes, or temporarily disable rules to understand why a flow is being blocked.

In the race to deploy autonomous AI agents, organizations are inadvertently building on a foundation of shifting sand. While security teams have spent the last year focused on "Prompt Injection" and "Model Poisoning," a much older, more dangerous adversary has quietly become the primary attack vector for the agentic era: Broken Object Level Authorization (BOLA).

What are HIPAA disaster recovery requirements? Healthcare data breaches exposed over 276 million patient records in 2024, representing more than 80% of the US population according to the HHS Office for Civil Rights. For healthcare organizations, the question is no longer whether a disruption will occur, but when. The HIPAA Security Rule addresses this reality directly through its contingency planning requirements, yet many organizations still operate with significant compliance gaps.

The Model Context Protocol (MCP) is emerging as a foundational interoperability layer for agentic AI, embraced by major platform providers. MCP simplifies how AI models connect to external tools and data. Think of it as a universal remote for security platforms: Instead of building fragile, one-off integrations, MCP allows AI to discover and use capabilities dynamically. For SIEM and detection providers, this shift is significant.

The widespread adoption of AI agents creates a new, unmanaged attack surface. The Exabeam January New-Scale launch directly addresses this risk, providing a layered approach to secure your AI workforce from onboarding to automated threat response.

Security teams require continuous innovation to defend against sophisticated attackers and support modern infrastructure. The January 2026 LogRhythm SIEM release delivers critical updates to your security operations, improving everything from detection and investigation to core platform stability.

With my youthful good looks, it’s hard to believe that I’ve been in cybersecurity for almost two decades. : ) I’ve seen the industry go through some massive transformations. Each change brought its own set of challenges, failures (I’m looking at you XDR) and, more importantly, opportunities. As I am now entrenched in application security, I’m learning that we’re in the middle of another one of those moments, and it’s just as exciting.

In my house, we consume a lot of AI research. We also watch a lot—probably too much—TV. Late in 2025, those worlds collided when the AI giant Anthropic was featured on “60 Minutes.” My husband tried to scroll past it, but I snatched the controller away, unable to resist a headline calling out the first widely acknowledged case of an “agentic AI cyberattack.” The framing itself was irresistible, a milestone moment in the rapid acceleration of AI.

Security Operations Centers (SOCs) are overwhelmed by alerts, often reacting to threats as they appear rather than anticipating them. Bitsight Threat Intelligence (TI) transforms SOC operations by providing external visibility, context, and correlation with real adversary behavior. By mapping incidents to MITRE ATT&CK techniques and monitoring the deep and dark web for emerging risks, Bitsight TI enables SOC and CTI teams to detect, understand, and prevent threats before they cause impact.