Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Microsoft 365 is great for sharing, creating and collaborating on data. Protecting data, however, is something else altogether. It’s not so easy. Many organizations assume Microsoft fully protects their information, only to discover gaps when something goes wrong. That’s why data retention, backup and archiving are so important. The three concepts have some similarities, but they serve very different purposes. More importantly, you can’t substitute one for another.

The productivity revolution promised by AI coding assistants has arrived. Developers are shipping features faster than ever, with tools like GitHub Copilot, Amazon CodeWhisperer, and Claude Code becoming as essential to modern development as Git itself. But beneath this velocity lies a troubling reality that every security leader needs to confront: we’re scaling security debt at unprecedented speed.

Most security teams did not architect their hybrid cloud environment. It grew. A legacy ERP that finance refused to migrate off-premises, a Kubernetes cluster a product team spun up in GCP without telling IT, three SaaS applications that became mission-critical before anyone ran a security assessment on them, and a VPN that was supposed to be temporary in 2020 and is still running.

It’s Tuesday morning at a mid-size fintech. A customer-support workflow runs on CrewAI in production: a Triage agent reads tickets, a Records agent pulls customer history, a Remediation agent drafts and sends the reply. A user submits a ticket with a pasted error log containing an indirect prompt injection. Triage summarizes and delegates. Records, interpreting instructions embedded in the summary, pulls 2,400 customer records instead of one.

The surgeon is thirty-two minutes into a procedure. The ambient scribe pod listening to the operating room is mid-encounter — transcribing, retrieving prior chart context, drafting the operative note for post-op sign-off. At the same moment, your SOC gets an alert: anomalous tool invocation from that pod, elevated egress volume, behavioral deviation from the agent’s baseline.

Your platform team spent a week configuring the Agent Sandbox CRD on a gVisor-enabled node pool — the architecture Google positions as the recommended pattern for AI agent workloads on GKE. Workload Identity Federation with KSA principals is bound to every agent pod. Container Threat Detection is licensed and active in Security Command Center Premium. And the runtime behavioral sensor you budgeted for won’t install.

Accelerating security solutions for small businesses‍ Tagore offers strategic services to small businesses. A partnership that can scale‍ Tagore prioritized finding a managed compliance partner with an established product, dedicated support team, and rapid release rate. Standing out from competitors‍ Tagore's partnership with Vanta enhances its strategic focus and deepens client value, creating differentiation in a competitive market.

Part 1 covered CanisterWorm, the self-spreading npm worm. Part 2 covered the malicious LiteLLM package. Part 3 covered the telnyx WAV steganography attack. Part 4 covered the xinference AI inference attack. This post covers: a compromised @bitwarden/cli package that combines a self-propagating npm worm, a GitHub Actions secrets dumper, and a novel AI assistant poisoning technique.

Revisiting a conversation between LimaCharlie co-founder Christopher Luft and Chris Cochran, Field CISO & Vice President of AI Security at SANS Institute, on The Cybersecurity Defenders Podcast. For most of cybersecurity’s history, defenders could operate under a safe assumption: somewhere on the other end of an attack, a human was making decisions. Scripts might automate parts of the kill chain, tools might accelerate execution, but a person was in the loop.