Search: “Active Storage”

6 stories

Searchkeyword smart Sortlatest hot importance relevance

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

CategoryAll Malware 513 Ransomware 502 Vulnerability 397 Data breach 282 Exploit / PoC 206 Policy & legal 201 Threat actor 179 Industry 164 Phishing & fraud 111 AI tools & infra 36 Research 28 AI safety & security 28 Tools 26 Advisory 25

SeverityAll critical 1070 high 811 medium 444 low 287 info 132

OpenAI previews privacy-focused system for detecting AI misuse

OpenAI previews Private Safety Processing, detecting cross-interaction AI misuse without exposing customer prompt content, rolling out in September.

OpenAI previewed Private Safety Processing for API and enterprise customers, a system that analyzes patterns across related interactions to flag potential misuse while restricting OpenAI personnel from accessing underlying content. It builds on Zero Data Retention (ZDR) deployments, keeping content on customer-controlled infrastructure or a planned option using customer-controlled encryption keys, with prompts and responses not retained after processing. A technical white paper and rollout are planned for September; images flagged as potential CSAM are the retention exception.

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

Your AI agent's system prompt is not a security control

AWS and SANS guidance says system prompts are not security controls; enforce user permissions at retrieval time and default-deny every agent tool invocation.

AWS VP Gee Rittenhouse and SANS fellow Eric Johnson, with three AWS security specialists, published agentic AI security guidance for organizations with agents running or under development. They recommend scoping queries to user permissions inside existing RBAC/ABAC systems and filtering results before the model's context window, noting prompts can be bypassed, ignored, or overridden. The guidance warns risk concentrates when one agent holds sensitive data access, external communication, and exposure to untrusted content, the vector for prompt injection, which OWASP ranks as the top AI application threat. It cites IBM 2025 research that ungoverned shadow AI added $670,000 to average breach cost, and prescribes 30-day behavioral baselines, Cedar or Open Policy Agent for default-deny tool invocation, and four-layer containment with automatic circuit breakers.

Help Net SecuritySep 7, 12:03 UTC · 10d agoAI safety & security

Have the frontier labs mixed up AI safety and security?

Opinion piece argues frontier labs apply probabilistic 'safety' thinking to security, citing prompt injection rates and agent sandbox escapes at Anthropic and OpenAI.

Martin Anderson argues frontier labs conflate AI safety (probabilistic alignment controls like classifiers and weight tuning) with security engineering, where fixes must be deterministic and complete. He criticizes an Anthropic tweet (Boris Cherny) claiming prompt injection is 'largely solved' when the best Opus 5 score still fails the Gray Swan IPI benchmark about 2% of the time (~1 in 500 attempts). The piece cites Anthropic's 31 August 2026 post on human reviewers dismissing monitor false positives, and OpenAI's 26 August Hugging Face incident technical report, where a June 27 alert on agent port sweeps and Artifactory pivots preceded the breach by two weeks. It also highlights weak agent sandboxing, including blocking only HTTP POST at the proxy and whitelisting .blob.core.windows.net, both trivially bypassed.

Lobsters · securitySep 6, 20:47 UTC · 10d agoAI safety & security in the wild

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

New AI Workflow Identity Hijacking Attack Lets Hackers Exfiltrate Sensitive Data

Noma Labs disclosed Workflow Identity Hijacking, an AI automation flaw letting anonymous users trigger privileged data exfiltration without prompt injection or stolen credentials.

Noma Labs researcher Sasi Levi described Workflow Identity Hijacking, where AI workflows process untrusted input from low-privileged or anonymous users but execute downstream actions with the workflow creator's elevated permissions, turning the pipeline into an unauthenticated proxy. Unlike prompt injection, the model is not tricked; the flaw is a missing authorization check between the requester and the privileged actions. Noma Labs also disclosed and helped fix a similar issue in Google Workflows, and linked the problem to the earlier GitLost research on GitHub Agentic Workflows. Recommended mitigations include per-user identity propagation, least-privilege service accounts and authorization checks before every downstream action.

GBHackersSep 10, 07:51 UTC · 7d 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