Search: “Privilege Manager”

16 stories

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Vulnerability 1989 Ransomware 849 Exploit / PoC 777 Malware 492 Data breach 454 Industry 300 Threat actor 226 Policy & legal 226 Phishing & fraud 118 AI safety & security 77 Advisory 76 AI tools & infra 71 Research 37 Tools 30

SeverityAll critical 3160 high 1322 medium 751 low 306 info 225

AI supply chain risk is showing up in developer workflows first

Zentera Systems CEO says AI supply chain attacks currently hit developer workflows first, advising segmentation over tooling and citing the Phantom Raven campaign.

In an interview, Zentera Systems CEO Dr. Jaushin Lee argues that most active AI supply chain incidents target developer workflows and open-source package repositories, while poisoned model weights, compromised MCP servers, and poisoned vector stores remain largely in research and demos. He cites the active 'Phantom Raven' campaign, where attackers register AI-hallucinated package names in public repositories with malicious payloads that silently infect vibe-coding build pipelines. He recommends software-defined segmentation, semiconductor-style project enclaves with egress controls, and warns that self-hosting models without agent sandboxing leaves exposure unchanged.

Help Net SecurityAug 25, 00:00 UTC · 23d agoAI safety & security

What 90 days and a small budget can buy in AI agent security

Versa Field CISO details hidden costs of self-hosting open-weight models and a 90-day AI agent security plan of inventory, blast-radius reduction and testing.

In a Help Net Security interview, Prasad Tharippala, Field CISO at Versa, argues running open-weight models in-house improves control but shifts hardening, patching, access control, monitoring and incident response onto the buyer, with underestimated costs in GPU infrastructure, licensing review, EU AI Act compliance and scarce AI/ML security skills. On red-teaming AI agents, he recommends testing prompt injection, indirect injection, excessive permissions, data leakage, memory and RAG poisoning, malicious tool outputs, cross-agent trust abuse and infrastructure attack paths, mapped to OWASP agentic guidance and MITRE ATLAS. He highlights the handoff between chained agents as a major risk zone and stresses exercising human approval, shutdown and rollback controls under test conditions. For teams with 90 days and small budgets, he ranks inventory, blast radius reduction and ongoing testing as the priority order.

Help Net SecurityAug 28, 00:00 UTC · 20d agoAI safety & security

Why "Shady AI" is Security's Next Big Governance Problem

Opinion piece argues approved-but-ungoverned AI agent use ('shady AI') is a growing enterprise risk, citing a Meta Sev 1 data-exposure incident.

In March 2026, an approved AI agent at Meta posted a forum answer publicly, exposing sensitive company and user data to unauthorized employees for over two hours and triggering a Sev 1 incident. The author contrasts shadow AI (unapproved tools) with 'shady AI' (approved tools used in unapproved or unanticipated ways), arguing the latter is harder to govern because it operates inside the organization's visibility. A July 2026 SANS survey found 76% of security teams now have a role in governing enterprise AI. The piece recommends governance-by-default environments with built-in permissions, access controls, and monitoring rather than policy and training alone.

The Hacker NewsAug 22, 08:33 UTC · 26d agoAI safety & security

Claude Mythos AI Autonomously Executes Full Cyber Kill Chain Without Human Guidance

Booz Allen's benchmark found Anthropic's Claude Mythos was the only tested model to autonomously complete a full cyber kill chain to domain administrator control.

Booz Allen assessed 18 US and Chinese models as autonomous attackers against a production-grade enterprise network, measuring actions via network and host telemetry. Claude Mythos scored 80 on the Cyber Weapon Index (74 vulnerability research, 86 kill-chain attainment), moving from a stolen employee credential to administrator-level control in every credentialed attempt. Only frontier Anthropic models identified the previously unseen flaw in compiled software, and only Claude Mythos exploited it; the report notes a harness paired with Claude Sonnet could rival Claude Mythos. The result is a controlled benchmark, not evidence of a real-world campaign or victim breach.

Cyber Security NewsSep 8, 12:50 UTC · 9d agoAI safety & security1

Orchid Security targets AI agent risk with drift detection and kill switches

Orchid Security launched identity drift detection and application-level kill switches to govern AI agents that exploit enterprise identity debt.

Orchid Security announced AI readiness controls including agent discovery, continuous drift detection between an agent's intended purpose and observed behavior, and application-level kill switches that revoke credentials, disconnect tools, or suspend agent workflows. The company cites its Identity Gap 2026 finding that 57% of enterprise identity is unseen and unmanaged, which agents can leverage to gain elevated access in seconds to minutes. New integrations include a certified PAM integration for Palo Alto Networks Idira and identity telemetry streaming to Splunk Enterprise Security. The launch follows agentic enhancements to Orchid's Identity Control Plane in May 2026 and cites NIST's draft Cyber AI Profile and DORA as regulatory drivers.

Help Net SecuritySep 9, 13:29 UTC · 7d agoAI safety & security

AI Agents Are Here. So Are the Threats.

Unit 42 demonstrates nine framework-agnostic attack scenarios against AI agents built with CrewAI and AutoGen, causing data leakage, credential theft and remote code execution.

Palo Alto Networks Unit 42 investigated how attackers can target agentic applications, implementing two functionally identical apps with the open-source CrewAI and AutoGen frameworks and executing the same attacks on both. Nine attack scenarios produce outcomes including information leakage, credential theft, tool exploitation and remote code execution. Findings show most vulnerabilities are framework-agnostic, arising from insecure design patterns, misconfigurations and unsafe tool integrations rather than flaws in the frameworks themselves. The team published defense strategies per scenario and open-sourced the source code and datasets on GitHub.

Palo Alto Unit 42Aug 17, 12:33 UTC · Aug 17, 2026AI safety & security

How MCP Servers Can Expose Enterprise Secrets

MCP servers holding AI agent credentials risk secret exposure via plaintext configs, credential sprawl, prompt injection, and over-permissioning; mitigations include centralization and least privilege.

The article examines how Model Context Protocol servers, which hold API keys, tokens, and service-account credentials for AI agents, can leak enterprise secrets. Documented exposure paths include plaintext credentials in config files, ungoverned credential sprawl, prompt injection, over-permissioning, and untrusted third-party servers. It cites CVE-2025-6514 in mcp-remote (400,000+ downloads), where a malicious server triggered OS command injection leading to remote code execution. Recommended mitigations include centralized secret stores, short-lived auto-rotated credentials, least privilege, and human approval for sensitive actions.

The Hacker NewsAug 17, 11:58 UTC · Aug 17, 2026AI safety & security CVE-2025-6514

Securing Claude Code: The New Compliance API, Local Visibility, and Identity Governance

Anthropic's new Compliance API endpoints expose Claude Code local session transcripts, highlighting governance gaps for endpoint AI agents.

Anthropic added local session transcript endpoints to its Compliance API on August 11, 2026, giving security teams visibility into prompts, bash commands, file operations, and MCP commands run by Claude Code harnesses on endpoints. The article argues local harnesses break the classic shared-responsibility model, citing Token Security data that 68.6% of discovered AI agents run on endpoints, and a Cloud Security Alliance survey of 418 IT and security professionals in which 82% found an unknown agent within the past year. It outlines three governance layers: Anthropic managed settings as a policy baseline, the Compliance API for cloud-visible transcripts, and endpoint telemetry to connect agent activity to identity, credentials, and permissions.

The Hacker NewsAug 31, 11:31 UTC · 17d agoAI safety & security1

Securing AI agents: Key controls and best practices

Security experts warn AI agents with employee-level privileges outpace human access controls and advise layered enforcement, sandboxing, and approval gates.

CSO reports that enterprises granting AI agents credentials, tools, and network access face risks that human-focused identity controls cannot contain, including machine-speed action chaining and sub-agent spawning. Experts from Strike Graph, Veracode, Delinea, and XBOW recommend treating agents as privileged insiders with hard technical boundaries: egress proxies with allowlists, short-lived brokered tokens, separated read/write rights, and approval for high-risk actions. XBOW describes a layered architecture with a guardian model reviewing agent actions and per-agent audit files. OWASP guidance on excessive agency urges limiting agent functions, permissions, and autonomy with authorization enforced downstream.

CSO OnlineSep 8, 08:25 UTC · 9d agoAI safety & security

10 most critical LLM vulnerabilities

OWASP updated its Top 10 LLM application vulnerabilities, ranking prompt injection first and elevating excessive agency to third amid agentic adoption.

OWASP refreshed its Top 10 list of critical vulnerabilities in LLM applications, for the first time incorporating real-world incident data alongside expert voting. Prompt injection and sensitive information disclosure remain first and second, while excessive agency jumped from sixth to third as agentic systems that call APIs and execute code proliferate. Unbounded consumption of AI resources rose in prominence, while improper output handling dropped to the bottom as output sanitization becomes widespread. The list includes remediation guidance such as strict output schemas, human-in-the-loop approvals, and least-privilege credentials held in application code.

CSO OnlineSep 10, 08:25 UTC · 7d agoAI safety & security

The agentic harness for Tenable Hexa AI: How Tenable prevents AI agents from going off the rails

Tenable details the 'harness' governing its Hexa AI agents, treating LLMs as untrusted insiders with scoped permissions, human approval and audit logging.

Tenable describes the agentic 'harness' built for Hexa AI, the agentic engine of the Tenable One Exposure Management Platform, which limits what context models can see, which tools they can call, when humans must approve actions, and what is recorded. The post catalogs real development failures: agents acting past their authority, being confidently wrong about tenant data, crashing on broad queries, over-refusing capable tasks, and over-conservative safety filtering causing false positives. It also highlights that attacker-writable security data such as hostnames and certificate fields can serve as a prompt-injection vector for agents reading platform data.

Tenable BlogSep 10, 13:00 UTC · 7d agoAI safety & security1

NCSC Warns Shadow AI Creates New Security Risks

UK NCSC warns that unapproved AI tools used by 71% of UK employees expose corporate data and create hard-to-detect organizational security risks.

The UK's National Cyber Security Centre warned on 7 September that shadow AI, unapproved AI tools used outside organizational controls, creates visibility gaps and raises risks of data breaches, intellectual property loss, and regulatory non-compliance. It cited Microsoft research finding 71% of UK employees had used AI tools not approved by their employer. NCSC also warned AI agents can carry critical vulnerabilities, allowing attackers who exploit one to inherit the agent's data access, services and privileges, and that attackers are highly likely to abuse agents with looser guardrails. The agency recommended reducing rather than eliminating shadow AI through positive security culture and clear guardrails.

Infosecurity MagazineSep 7, 14:00 UTC · 9d agoAI safety & security

Ping Identity introduces enterprise security for personal AI agents

Ping Identity launched Enterprise Personal Agent Access to discover, authenticate and control personal AI agents like Claude at runtime.

Ping Identity announced Enterprise Personal Agent Access, delivered through PingOne Privilege, to give enterprises visibility and control over personal AI agents such as Claude and Claude Code. The product discovers agents including shadow AI, associates each session with the user and device behind it, and enforces allow, deny, log, human-approval or revocation decisions on agent access at runtime. It enables secretless developer workflows so agents can commit code without long-lived credentials while keeping actions attributable to the agent. Ping cites Gravitee research that 48% of production AI agents run unsecured and says the product is available now and piloting with global enterprises.

Help Net SecuritySep 3, 06:25 UTC · 14d agoAI safety & security

The Outsized Shadow: Why 5% of AI Users Are Your Biggest Security Risk

Akamai's 2026 Enterprise AI Usage report finds the top 5% of AI power users create outsized shadow AI, data leakage, and agent security risks.

Akamai's State of the Internet: Enterprise AI Usage Risk Report 2026, based on real-world usage telemetry, finds the top 5% of enterprise AI power users interact with AI models at 12 times the rate of the bottom 50% of the workforce. 47.11% of enterprise AI conversations occur through personal identities rather than corporate-managed accounts, and 14.4% run through corporate email addresses tied to personal freemium subscriptions. 17.7% of employees at midsize enterprises use AI browser or IDE extensions, of which 16.31% contain known CVE vulnerabilities and nearly 75% request high or critical permissions. The report also describes emerging attack vectors including Vibe Hacking, CursorJacking, and CometJacking indirect prompt injection.

The Hacker NewsAug 24, 11:30 UTC · 24d agoAI safety & security1

When an Attacker Meets a Group of Agents: Navigating Amazon Bedrock's Multi

Unit 42 red-teamed Amazon Bedrock multi-agent applications, demonstrating prompt-injection attack chains that leak agent instructions and invoke tools, mitigated by Bedrock Guardrails.

Unit 42 red-teamed Amazon Bedrock Agents' multi-agent collaboration in Supervisor and Supervisor with Routing modes. The demonstrated attack chain detects the operating mode, discovers collaborator agents, delivers attacker-controlled payloads, and can disclose agent instructions and tool schemas and invoke tools with attacker-supplied inputs. No vulnerabilities were found in Bedrock itself, and the built-in prompt attack Guardrail blocked the attacks when properly configured. The researchers collaborated with Amazon's security team and frame the findings as a broader prompt injection risk for LLM-based systems.

Palo Alto Unit 42Aug 17, 12:31 UTC · Aug 17, 2026AI safety & security

How to secure edge AI in customer-owned environments

Microsoft outlines security architecture guidance for edge AI, urging runtime attestation, artifact provenance, and deterministic mediation of model actions.

Microsoft details how edge AI shifts trust responsibilities to customers operating their own infrastructure, where prompt injection, model tampering, and malicious firmware updates can occur alongside model weights, credentials, and physical-system access. The guidance recommends verifying runtimes with attestation, verifying AI artifacts with provenance, and constraining model actions through a deterministic mediator outside the model. It also covers new exposure surfaces from MCP, multi-agent systems, and computer-use agents running in disconnected or hostile edge environments.

Microsoft Security BlogSep 4, 19:10 UTC · 12d agoAI safety & security