Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The Shai‑Hulud worm and the Nx / S1ngularity attacks show how token‑stealing malware, vulnerable workflows, and always‑on elevated permissions allow cascading compromise. Enforcing JIT access on repository, organization owner/admin roles, and team‑based inherited permissions sharply reduces exposure, limits damage, and strengthens audit/compliance posture.

APIs are the foundation of modern applications, and attackers know it well. A single misconfigured endpoint or exposed token can give adversaries a direct path into sensitive systems and data across your environment. Your already overburdened security teams can’t afford to miss what may be their fastest-growing attack surface. How fast-growing is the threat?

We’re excited to announce the launch of our MCP server for end users, designed to boost engineering productivity while keeping security strong. Engineers often know exactly what they need to do—deploy to a new environment, spin up a workload, investigate logs—but not which permissions translate into those tasks. That leads to two common problems: The result is wasted time, frustrated teams, and an inflated attack surface from unnecessary standing privileges.

Modern enterprises run on automation. But behind every line of code deploying infrastructure, moving data, or triggering workflows is something often overlooked: a non-human identity (NHI). These NHIs—service accounts, machine credentials, API tokens, CI/CD integrations—outnumber human users by orders of magnitude. And they’re everywhere. Yet in too many organizations, they’re still unmanaged, invisible, and dangerously overprivileged.

The Drift OAuth breach didn’t just expose one SaaS vendor — it exposed a systemic blind spot: the sprawling, ungoverned world of Non-Human Identities. In case you missed it, in August 2025, attackers from UNC6395 exploited compromised OAuth tokens from Salesloft’s Drift integration—an AI chat tool—to access and exfiltrate data from Salesforce, including credentials like AWS keys and Snowflake tokens.

Everyone’s trying to make AI agents do useful things. That’s why the Model Context Protocol (MCP) is gaining momentum with teams operationalizing LLMs across their infrastructure and tooling. Backed by teams like OpenAI and Google, MCP gives a consistent, standardized way to connect LLMs with the rest of your stack. In other words, the MCP Protocol makes connecting AI tools with real business data and workflows easier using structured access instead of janky UI hacks and glued-on custom code.

Today we’re excited to announce the launch of Apono’s new AI-powered Access Assistant, now live across the Apono Cloud Access Management Platform. As AI continues to transform engineering and security workflows, this assistant brings natural language interaction to access management. Helping teams move faster while staying secure. By eliminating the guesswork from access requests, Apono’s Access Assistant gives engineers a powerful new way to get exactly the access they need.

By 2025, non-human identities (like service accounts, API keys, and bots) will outnumber human identities by 45:1 in cloud environments. Yet many organizations still rely on static IAM roles and manual provisioning, leaving them exposed to credential sprawl, insider risk, and compliance violations. That’s where modern Enterprise Identity Management (EIM) comes in. Enterprise software development is increasingly cloud native.

If you’re a security vendor and you get breached, you’re not just another victim; you’re a failed promise. A broken fire alarm in a burning building. When Okta disclosed a breach in October 2023, its stock dropped nearly 11%, wiping out close to $2 billion in market cap in a single day – a stark reminder of how quickly trust evaporates.

You can’t secure what you don’t manage. Mismanaged access is an open invitation for breaches. Overprivileged users and a surge in non-human identities (like service accounts and API keys) are quietly expanding your organization’s attack surface. Yet many still rely on outdated, manual IAM practices that can’t keep up with modern infrastructure. It’s not just a theory—38% of breaches trace back to stolen credentials.