Discuss how organizations are approaching the use of AI, security against AI, and managing non-human identities
Recently active
Here’s a quick summary of the key points from our second live virtual security briefing. Sign up for upcoming sessions in the series here, and find the full recordings from all sessions here. Briefing RecapThe problemMachine identities already outnumber people 82 to 1 in the typical enterprise, and 78% of organizations have no documented policy for creating or removing AI identities.Three kinds of accounts carry real privilege and answer to nobody:A local admin account: five people know the password, and the log names the account, not the person. A service account: created for a project years ago, never rotated, its creator long gone. An AI agent: running all night on a developer's token or an unreviewed OAuth grant, with nobody who decided when it should stop. Ownership is two different questions: Attribution asks who acted, and on whose behalf, answered per action. Sponsorship asks who decided this identity should exist and hold this much access, answered once for its whole life: who
Read the quick briefing from our third live virtual AI series session here, or watch the recording of the full conversation below (at the bottom of the write up). We are continuing to deliver this series, so sign up for upcoming sessions here. Briefing recapThe problem Machine identities already outnumber people 82 to 1 in the typical enterprise, and only 22% of teams treat AI agents as independent identities. Token theft is replacing password theft because tokens leave fewer traces. Every MFA factor assumes a person supplies it, and an agent can't: no phone, no biometric, no one to approve a push. What's left is a static secret, and whoever holds it is the machine. Why the gap is wider than it looks NIST's own guidelines separate verifying an identity from authenticating with a credential. For a person, someone checks a government ID first. For a machine, that step usually never happens: a service account gets created and nothing verifies what will run under it. It's the same gap tha
Here’s a quick summary of the key points from our second live virtual security briefing. Sign up for upcoming sessions in the series here, and find the full recording from this session at the bottom of the post. Briefing recapThe scenario An AI harness connects into a workspace using a persistent grant nobody remembers approving. Once it's compromised, the attacker rides that grant laterally through every connected account and finds credentials sitting in plain text, ready to use. None of it takes a sophisticated exploit: the grant was always live, and the credentials were always there. How it happenedNobody sets out to build standing access. It accumulates one reasonable decision at a time: a broad onboarding role, a temporary exception that outlived its project, a shared service account with credentials in a config file. Then an AI agent inherits the whole thing. Today, 59% of organizations say they don't have a workable alternative to that inheritance. What this means for youThree
We recently launched our AI Education Series; a weekly 30-minute QA with one of Delinea’s AI Security experts about a real world AI challenge or question and actions we recommend. Below is a recap from our first session. Find the recording of the full session after the write up. Briefing recapReal world scenarioIn July 2026, an autonomous AI agent running an unsupervised evaluation found a software flaw and let itself into Hugging Face's production infrastructure with no human steering it, taking 17,600 actions over two and a half days and reaching admin control of two clusters within thirteen hours. 😳🫣😮 What slowed this attack A role that refused every change the agent tried, a database it could never get to from where it landed, and a credential store that caught and denied all 84 things the agent attempted. None of these security measures are exotic, but they worked.A credential that was never sitting there to steal in the first place may have worked even better. What does this
Sometimes, it’s the things we use the most that we take for granted. We use them frequently, we think we are getting maximum value from them, and then we realize there’s more. Take your car. It can warn you when you drift out of your lane, watch your blind spots, and brake before you've registered a hazard. Most of us pay for that protection, drive off the lot, and then: never set it up. The car does its main job so well that we don’t remember the other valuable things it can do.Identity security works the same way. When it comes to vaulting, many Delinea customers have vaulted their credentials, become comfortable, and moved on to additional priorities. Meanwhile, AI adoption is creating identities faster than most teams can track them. Every new agent, automation, and integration shows up with credentials, service accounts, and privileged pathways attached. Vaulting is the example I used here – but it could have just as well been endpoints, servers, or something else.The instinct mig
Artificial Intelligence (AI) is rapidly transforming the cybersecurity landscape. From automating threat detection to streamlining workflows, AI-powered tools are becoming more common in our industry. But with these advancements come new questions, challenges, and opportunities.We’d love to hear your thoughts and experiences!How do you feel about the growing role of AI in cybersecurity? What advantages or benefits have you seen (or do you anticipate) from using AI-driven solutions? Are there any disadvantages or concerns you think the industry should be aware of? Have you found any AI use cases that have helped you or your team work more efficiently or securely? What would you like to see from AI in the future of cybersecurity?Jump in below—let’s discuss how AI is impacting our work, our systems, and the future of cybersecurity!
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.