Search: “regression”

5 stories

Searchkeyword smart Sortlatest hot importance relevance

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

CategoryAll Vulnerability 62 Exploit / PoC 29 Industry 20 AI research 20 AI tools & infra 12 Policy & legal 10 Model release 9 Data breach 8 Research 7 Threat actor 6 Tools 6 Ransomware 6 Malware 5 Advisory 5

SeverityAll critical 80 high 30 medium 24 low 28 info 55

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 · 6d agoAI safety & security1

When the prompt becomes the payload: A practical pen-testing guide for GenAI, LLM and RAG applications

CSO Online publishes a practical penetration-testing guide for GenAI, LLM, and RAG applications, covering prompt injection, retrieval poisoning, and tenant isolation testing.

The guide frames LLM applications as attack graphs spanning prompts, retrieval layers, vector stores, tools, identities, and downstream APIs, arguing that conventional web testing misses instruction-vs-data channel risks. It builds on OWASP prompt injection guidance (direct vs. indirect injection) and NIST's 2025 adversarial machine-learning taxonomy, noting that RAG and fine-tuning do not remove injection risk. Recommended practices include documenting trust transitions across components, using canaries and synthetic records to avoid test side effects, running multi-turn and obfuscated injection campaigns, and verifying chains from poisoned documents to observable state changes. It also details testing RAG pipelines via controlled document poisoning across metadata, OCR layers, and code comments, plus cross-tenant isolation checks on retrieved document IDs.

CSO OnlineSep 9, 10:00 UTC · 8d agoAI safety & security1

Search: “regression”

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

When the prompt becomes the payload: A practical pen-testing guide for GenAI, LLM and RAG applications

Praxen: Open-source AI agent behavior verification

Microsoft Open-Sources RAMPART and Clarity to Secure AI Agents During Development

Picking an AI red teaming vendor is getting harder