Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The Abbott Cyber Incident Reveals Why Infrastructure Security Is No Longer Enough for Healthcare

Healthcare has spent years strengthening its infrastructure against ransomware, patching vulnerabilities, deploying endpoint detection, and implementing zero-trust architectures. Yet, attackers continue to find new ways to compromise healthcare organizations.

When AI Agents Run Healthcare Workflows, Business Logic Becomes the New Attack Surface

Healthcare has moved well past pilot projects. AI agents now triage support tickets, draft clinical documentation, manage patient engagement, and coordinate care across systems that were never designed to talk to autonomous software. Autonomous systems can now analyze data, make decisions, trigger actions, and coordinate across clinical systems with minimal human oversight.

How I'd Plug the MiniMax M3 API Into a Coding Agent Without Rebuilding the Stack

Every time a promising new model shows up, I run through the same mental math before getting excited: how much of my existing agent setup survives the swap, and how much do I have to tear out and rebuild just to try it. Most of the time the answer is "more than I'd like," which is exactly why I ignore half the models that cross my feed. MiniMax M3 is one of the rare ones where the answer turned out to be "almost none of it," and it's worth walking through why, because the reasoning applies beyond just this one model.

The Agentic Attack Surface Is Growing Faster Than Your API Inventory. Here's How to Catch Up

Ask any security leader how many APIs their organization runs, and you’ll usually get a confident number. Ask them how many of those APIs are actually being called by an AI agent, a copilot, or an automated workflow right now, and the confidence tends to disappear. That gap is the problem. APIs have always outpaced the inventories built to track them; new services ship every sprint, integrations get added without a ticket, and old endpoints get deprecated without ever being switched off.

The Agentic Attack Surface Is Growing Faster Than Your API Inventory

Ask any security leader how many APIs their organization runs, and you’ll usually get a confident number. Ask them how many AI agents are operating in their environment right now, what those agents are deciding to do, and which APIs they’re calling to do it, and the confidence tends to disappear.

SCIM & REST API Provisioning for Jira and Confluence

Wouldn't it be great if managing user accounts didn't take hours of manual effort? For many IT teams, unfortunately, that's exactly the reality. Every new employee needs access for all the apps they intend to use. When someone switches roles, permissions need updating. And when someone leaves, all their access needs to be revoked immediately. These tasks might sound simple, but they become exponentially more challenging as your company grows.

Monitor Apigee X API traffic and security with Datadog

Apigee X is Google Cloud’s API management platform. Software and platform teams use it to secure, publish, and govern the APIs that internal services, partners, and external developers depend on. Apigee X sits in the request path for that traffic, so a latency spike or a rise in policy errors reaches API consumers before most other signals do. Watching proxy traffic, latency, and security posture usually means jumping between Apigee analytics and separate infrastructure tools.

MCP Data Exfiltration: How AI Agents Leak Sensitive Data Through MCP Tool Calls

Model Context Protocol (MCP) is what turns an AI assistant into an AI agent. It’s the standardized bridge that lets models call real tools – read files, query databases, send messages, pull emails. That capability is the whole point. It’s also what makes MCP environments a target. Most deployments were scoped for what the agent needed to do. Not for what happens when that access is turned against the organization.