Search: “NIST”

5 stories

Searchkeyword smart Sortlatest hot importance relevance

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

CategoryAll Vulnerability 518 Policy & legal 295 Ransomware 231 Industry 205 Data breach 199 Exploit / PoC 189 Threat actor 61 Phishing & fraud 58 Malware 55 AI safety & security 37 Advisory 32 Research 31 AI research 23 AI tools & infra 19

SeverityAll critical 1032 high 293 medium 232 low 319 info 114

Who's governing your AI? A trust framework for enterprise agents and models

DigiCert pitches AI Trust framework using PKI, DNS policy records and workload identity to govern shadow AI agents across enterprises.

The Register-sponsored piece outlines DigiCert's AI Trust framework for governing AI agents, built on PKI, DNS, and attestation, citing IBM's 2026 Cost of a Data Breach report that 68% of organizations lack AI governance or shadow AI detection. The approach treats agent identity as workload identity aligned with IETF WIMSE, NIST CSF 2.0, and SPIFFE/SPIRE, using short-lived credentials instead of static API keys. DigiCert also proposes DMARC-style DNS agent policy records and an AI Agent Passport cryptographically binding agent identity to approved operations, with a unified kill switch.

The Register · SecuritySep 15, 15:00 UTC · 1d agoAI safety & security1

NovaFabric: Tamper-Evident, Replayable Evidence for Autonomous AI Agent Runs

NovaFabric seals autonomous AI agent runs into tamper-evident, replayable Run Capsules enabling third-party audit under EU AI Act and ISO 42001.

NovaFabric records autonomous agent runs without modifying agent logic into portable Run Capsules (fifteen-entity schema) sealed with DSSE signatures, RFC 3161 timestamps, a Merkle log, and redaction attestations, supporting four-mode replay and third-party Evidence Bundle verification. Evaluation shows tampering rejected across three tested classes, 14/14 credential types redacted while preserving 9/9 decoys, and 140/140 mutations localized; blast-radius queries reach 45.5ms p99 over 10M edges. Limits include only 2/10 tool-using workloads completing replay due to missing tool-response substitution and ingest capped at 61.6 req/s. The contribution integrates OpenTelemetry, DSSE/in-toto, and W3C PROV rather than new cryptography.

arXiv cs.CRSep 11, 08:35 UTC · 6d 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

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

To keep the AI hacking genie bottled up, try one-way networks

Intuition Machines CEO proposes data diodes and one-way networks to physically prevent frontier AI models from escaping training sandboxes, citing the OpenAI Hugging Face incident.

Eli-Shaoul Khedouri, CEO of Intuition Machines, argues that sandboxes, permissions, and VMs are insufficient to contain frontier models, pointing to OpenAI's hack of Hugging Face as evidence. He proposes high assurance architectures modeled on classified SCIF environments: one-way optical data diodes for training inputs and telemetry, a sel4-verified receiver, immutable snapshots of registries like PyPI, GitHub, and npm, and mocked web services. He estimates under five percent overhead per gigawatt for such clusters, but notes frontier labs have not adopted them, largely because of competitive speed rather than cost.

The Register · SecuritySep 3, 06:33 UTC · 14d agoAI safety & security