[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-EXGsi7HQmUGU9tF9NL3ZMIA2-Ap75ekWMqJu7jC04Y":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":47,"controls":48},"3016453b-a7f8-421b-bacd-ed02de6806ba","dormant-ai-agents-retain-excessive-access-posing-silent-data-risk","16393e7a-9622-4a4c-9f5f-7e25a16620df","Dormant AI Agents Retain Excessive Access, Posing Silent Data Risk","Organizations are deploying AI agents with broad permissions and long-lived API keys, then forgetting about them — leaving 76% idle for over 60 days while still holding valid credentials to sensitive systems. This 'ghost agent' problem mirrors the classic challenge of orphaned service accounts, but with the added risk of unsecured triggers that allow external actors to reactivate dormant agents and initiate actions like data exfiltration. The lack of data loss prevention coverage over these agent connections compounds the exposure. This matters because attackers increasingly target non-human identities, which are often overlooked in access reviews and lack the same scrutiny as human user accounts.","**Immediate actions:**\n- Audit all deployed AI agents and revoke credentials or API keys for any agent inactive for more than 30 days.\n- Disable or sandbox unsecured triggers on dormant agents until a formal review confirms they are still required.\n\n**Long-term improvements:**\n- Enforce least-privilege principles for all AI agent identities, scoping permissions to only the resources and actions each agent strictly requires.\n- Implement mandatory expiry and automated rotation for all API keys and credentials issued to AI agents.\n- Maintain a living inventory of all non-human identities (AI agents, service accounts, bots) with documented owners, purposes, and last-active timestamps.\n\n**Detection measures:**\n- Apply data loss prevention (DLP) policies to all data paths accessible by AI agents, alerting on anomalous data movement.\n- Configure logging and alerting for any reactivation of agents that have been dormant beyond a defined threshold, treating it as a potential security event.",[12,13,14,15,16,17,18],"CIS Control 5: Account Management","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","NIST SP 800-53 SI-2: Flaw Remediation","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","CIS Control 12: Network Infrastructure Management","GDPR Article 32","CIS Control 18: Penetration Testing",{"GDPR Article 32":20,"CIS Control 5: Account Management":21,"CIS Control 18: Penetration Testing":22,"NIST SP 800-53 SI-2: Flaw Remediation":23,"CIS Control 12: Network Infrastructure Management":24,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":25,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":26},"If dormant agents with unsecured access exfiltrate personal data, organizations face breach liability; Article 32 requires appropriate technical measures — including access controls and monitoring — to ensure ongoing confidentiality of personal data.","Dormant AI agents with persistent credentials are unmanaged accounts; CIS Control 5 requires organizations to inventoried, disable, and remove unused accounts and credentials, which would have eliminated the standing access of inactive agents.","Regular adversarial testing that includes non-human identity attack paths would surface the risk of reactivating dormant agents with valid credentials, enabling organizations to remediate before real attackers exploit the vector.","Excessive permissions and orphaned credentials represent a systemic configuration flaw; a formal remediation process would identify and correct these over-privileged agent identities before they can be exploited.","Many agents connected to sensitive services without adequate network-layer DLP controls; this control requires that data flows be managed and restricted, limiting an agent's ability to silently exfiltrate data.","Never-expiring API keys and misconfigured agent triggers are technical vulnerabilities that require identification and remediation under this control, which mandates timely action on identified exposure.","The agents retained never-expiring API keys and excessive permissions; this function explicitly calls for managing credentials and enforcing least privilege for all identities, including non-human ones.","published","2026-10-26T06:20:24.097269+00:00","2026-10-26T06:20:24.081+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fwww.helpnetsecurity.com\u002F2026\u002F10\u002F26\u002Farrakis-dormant-ai-agent-risks-report\u002F","forgotten-ai-agents-may-still-access-sensitive-company-data-b22df1","Forgotten AI agents may still access sensitive company data",[35,41],{"id":36,"name":37,"slug":38,"description":39,"color":40},"1ec88fde-2d0f-4ed8-932a-33f5ccc0fdc7","Access Control","access-control","Excessive privileges, missing MFA, weak auth","#f97316",{"id":42,"name":43,"slug":44,"description":45,"color":46},"859cf0ad-a7e9-42bb-a75d-bac6511fa5d5","Configuration Management","configuration-management","Misconfigs, default credentials, exposed services","#eab308",[],[49,53,57],{"slug":50,"name":51,"problem":52},"identity-governance","Identity governance and single sign-on","People who leave or change roles lose access everywhere at once, and forgotten accounts stop piling up.",{"slug":54,"name":55,"problem":56},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":58,"name":59,"problem":60},"data-loss-prevention","Data loss prevention (DLP)","Sensitive data cannot quietly leave by email, upload, USB stick or AI tool."]