Pinned Tweet
Big news for Akeyless: we’ve been recognized in the 2026 Gartner® Magic Quadrant™ for Privileged Access Management. It’s our first inclusion, and an important step as we extend our machine identity and AI-agent security foundation into human privileged access.
Read the release: hubs.li/Q04CjWmB0
Attackers went from a stolen developer token to admin control in roughly 3 hours, Anthropic reports.
Short-lived credentials help, but secrets in an AI agent’s memory or logs can still leak before they expire.
Why agents shouldn’t hold credentials: hubs.li/Q04BHp2g0
Need a quick escape from back-to-back meetings? 🧠☕
Everyone is talking about AI, so we decided to turn it into a fun weekly challenge.
🎮 Play this week's game:hubs.li/Q04ByrnK0
⏱️ Share your time in the comments.
Through our partnership with @SecondFront, federal agencies and organizations with FedRAMP requirements can now access the Akeyless platform for their most sensitive environments.
Read the announcement: hubs.li/Q04B0m0K0
Once AI agents can approve transactions or change infrastructure, EU AI Act oversight becomes an identity question. How does the agent get access, and can someone stop it mid-task? Our readiness checklist: hubs.li/Q04znyX00
#EUAIAct #AIAgents #IdentitySecurity
Even if your vault works perfectly, your AI agent credential can still leak.
Unit 42 showed how an AWS AgentCore credential could be exposed from runtime memory, exfiltrated, and replayed outside AWS.
In the latest from Refael Angel: why runtime is the weak point, and how removing downstream credentials from the agent process breaks that attack path.
Read the blog: hubs.li/Q04yHlhM0
#AIAgents #IdentitySecurity #Cybersecurity #SecretsManagement
In its new Innovation Insight: Strengthen Cybersecurity with Machine IAM, @Gartner_inc calls for a shift away from credential-centric controls toward managed workload identities, short-lived access, stronger lifecycle governance, and tighter controls for AI agents, naming Akeyless as a Representative Provider .
Our take: once the machine is an autonomous agent, identity and access are only part of the problem. Security also has to govern how that authority is used at runtime. Read more: hubs.li/Q04y5flv0
#MachineIAM #IdentitySecurity #AIAgents
There's much to consume in Anthropic’s latest threat report but one thing really grabbed us: a stolen developer token became full cloud admin access in just three hours.
Akeyless CTO Refael Angel on what defenders need to change as AI compresses the path from exposed credential to real compromise → hubs.li/Q04xGk6H0
Cursor stores your API keys in a local database any extension can read. Still unresolved.
The Akeyless extension finds hardcoded secrets as you type and swaps static keys for dynamic, JIT secrets, right inside Cursor.
See how: hubs.li/Q04x9_yd0
Agentic Runtime Authority is now GA.
An agent told to summarize sales data can't delete a database, even if its permissions allow it. Intent enforced at the moment of action.
hubs.li/Q04x30G90
#AIAgents #IdentitySecurity #AgenticAI #NHI
Roughly 700 AI agents broke out of an internal test in July and compromised Hugging Face's production infrastructure.
You can't stop an agent from going rogue. You can stop a rogue agent from finding a credential worth using:
hubs.li/Q04w5nsn0
Gartner: workforce password managers and PAM aren't interchangeable. Forcing one to do the other's job = audit gaps, not less risk.
Refael Angel breaks down why the "just buy two tools" fix misses the point — and how Akeyless does both on one platform.
hubs.li/Q04t_22T0
#PAM #PasswordManagement #IdentitySecurity #CyberSecurity
Attackers don't break encryption. They steal credentials.
Standing privilege is still the biggest hole in most infrastructure, and rotating credentials only closes half of it.
The real question: who holds the complete key?
With Akeyless, no one does. Not the customer, not us.
Full breakdown: hubs.li/Q04tvLqs0
#SecretsManagement #IdentitySecurity #WorkloadIdentity
AI agents can pass every access check, authenticate, get authorized, and still do something no one saw coming. One agent wiped a production database in 9 seconds.
Akeyless CEO Oded Hareven on why identity's old walls are falling: hubs.li/Q04rYs9t0
#AIAgentSecurity
One npm token used to be enough to take over an account completely.
That changed July 31.
Refael Angel breaks down what GitHub's new 2FA rules mean for every credential in your pipeline: hubs.li/Q04rLNvt0
#NPM #SupplyChain #DevSecOps
5 categories of tools claim to "secure AI agents." Discovery, gateways, workforce governance, orchestration, runtime authority.
Only one decides whether a specific action is actually allowed to happen.
We mapped who does what 👇
hubs.li/Q04rBHr40
Today, we're announcing the Akeyless integration with Claude's Compliance API.
AI agents increasingly need access to production systems, but they shouldn't rely on long-lived credentials or unrestricted access.
Agentic Runtime Authority helps organizations secure AI agent access with just-in-time credentials, runtime policy enforcement, and a complete audit trail.
Learn more: hubs.li/Q04qCbRN0
An AI agent breached Hugging Face and logged 17,000+ actions in one weekend. OpenAI confirmed it ran on their own models, guardrails off.
The headline is the AI. The cause was one harvestable credential.
What that means for agent identity 👇
hubs.li/Q04qrdW60
#AIAgentSecurity #NonHumanIdentity #SecretsManagement
AI agents shouldn’t have access to credentials. That’s progress. But what happens after login?
Who decides what an authenticated agent can do, what data it can see, and which actions should be blocked?
Refael Angel explores the next layer of AI agent security:
hubs.li/Q04pZz-G0
As AI coding agents move from writing code to executing it, secrets become a much bigger security challenge. The new Akeyless MCP integration for OpenAI Codex lets teams give Codex the access it needs, without exposing credentials in prompts, .env files, repositories, or model context.
Read the blog:
hubs.li/Q04p6KV20
#aisecurity #openai #codex #identitysecurity


















