30
Fortunate Recall: Ontology-Driven Memory Lifecycle Management for Persistent Coherence in LLMs
Fortunate Recall introduces ontology-based lifecycle policies for LLM memory, cutting confabulation roughly in half (e.g., 45.1% to 22.4%) versus Mem0.
Fortunate Recall (FR) is a composable policy layer that classifies personal facts into a 10+1 behavioral ontology and applies category-specific lifecycle rules including differential temporal decay, slot-key supersession, event-time validity, and retrieval routing. FR-Bank scores 76.9% on the new 516-question LifecycleBench, ahead of Mem0, A-MEM, Memory-R1, and MemoryOS (61%-70.5%), and 75.2% on LongMemEval-S. End-to-end, confabulation drops from Mem0's 45.1% to 22.4% over answered queries, with the ranking replicating on open-weight Kimi K2.5 and transferring to the independent BEAM benchmark (46.8% vs 32.9%).
30
How to Secure Enterprise AI: From Adoption to Incident Readiness
Sygnia-backed guidance urges a lifecycle approach to enterprise AI security, citing survey data that AI adoption is outpacing governance and incident readiness.
The Hacker News published Sygnia-sponsored guidance on securing enterprise AI across its lifecycle, from use-case definition and vendor selection to deployment and incident readiness. It cites Sygnia's 2026 CISO survey of 600 senior leaders: 63% expect AI fully embedded by 2027, 73% say their organization would not be fully ready for a significant cyberattack, and 67% of executives believe unapproved AI tools already caused a breach. The piece highlights shadow AI, ad hoc integrations, and over-permissioned AI agents as key attack surface risks, noting only 38% of organizations report a comprehensive AI policy.
25
50
30
30
30
30
30
30
30
50
30
50
Toward Secure AI-Powered Penetration Testing Agents: Security Threats, Guardrails, and Architectural Perspectives
Paper proposes a threat taxonomy and guardrail analysis for LLM-powered autonomous penetration testing agents, covering lifecycle, architecture, and behavioral attacks.
The paper analyzes security threats to autonomous LLM-based penetration testing agents that independently perform reconnaissance, vulnerability identification, exploitation planning, and post-exploitation with minimal human supervision. It characterizes trust boundaries and attack surfaces of representative agent architectures and proposes a threat taxonomy spanning LLM lifecycle attacks, agent-architecture attacks, and cross-cutting behavioral attacks. The authors argue existing conversational-AI guardrails are insufficient for agentic, long-horizon offensive workflows and outline research directions for context-aware, architecture-aware guardrails.
45
30
30
30
30
BenchShield: Formal Model-Backed Instrumentation for Reward Integrity in LLM-Agent Evaluation Infrastructure
BenchShield uses lifecycle-model-backed instrumentation to detect reward hacking in LLM-agent benchmarks, lifting full-chain recall to 77-100% at up to 65% lower cost.
The framework grounds reward-hacking detection in a finite lifecycle model of an evaluation's reward-relevant events, combining a static phase-aware taint analysis with runtime infrastructure-side evidence attribution. Evaluation used a human-labeled corpus of 456 adjudicated trajectories drawn from more than 31,000 public agent runs across three benchmarks. BenchShield improves full-chain recall from 23-94% to 77-100% and same-vector coverage from 16-56% to 43-78%, cuts per-task cost by up to 65%, and achieves 96% accuracy detecting reward hacking at runtime.
42
30
30
30
30
30
30
30
30
CyberArk Identity Security Platform enhancements secure risky access and broaden identity protection
30
30
30
30
30
From Intent to Execution Grant: An Execution-Boundary Conformance Profile for High-Risk AI Actions
Researchers specify EBL-Core, an execution-boundary conformance profile binding AI agent intents, policies, and evidence into verifiable execution grants, validated with bounded tests.
The paper defines EBL-Core, a conformance profile deciding whether one fully materialized AI-generated candidate action may receive action-scoped execution authority. It binds a structured intent object, Root and Operational Policies, typed evidence, and a verifiable Decision Derivation through an Execution Release Contract, with lifecycle rules for Redemption and Revocation. Evaluation included 34 static vectors, 15 lifecycle checks, and 100 trials of 32 concurrent Redemption attempts yielding exactly one winner per trial. The authors state these bounded results demonstrate executability of the specified subset, not production readiness or complete mediation.
25
The OCUDU dApp Platform: An Open Runtime and E3 Interface for Real-Time AI-RAN
OCUDU open runtime lets third-party signed AI-RAN dApps run inside production 5G distributed units under three timing contracts, released as BSD-3 preview.
The OCUDU dApp platform provides an open runtime and E3 interface for executing signed AI-RAN applications inside a production 3GPP NR distributed unit, where prior dApp frameworks could only observe export streams. Modules run under three typed timing contracts: GPU receive-chain residency (Class A), the scheduler's 100 microsecond deadline (Class B), or non-blocking observer (Class C). On a GB10 gNB, dApps including an out-of-tree neural equalizer ran on a live cell without fallback. Platform, SDK, and a zero-hardware quickstart are public under BSD-3-Clause-Clear as a preview of the OCUDU AI-RAN Working Group 2.
22
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.
30
GitLab 19.3 helps enterprises scale agentic development securely
GitLab 19.3 runs its Duo Agent Platform AI Gateway inside Dedicated single-tenant environments and adds Secrets Manager plus agentic SAST remediation.
GitLab 19.3 lets GitLab Dedicated customers run the Duo Agent Platform AI Gateway within the same single-tenant environment and region, with support for bring-your-own inference models. The release adds Secrets Manager in limited availability scoping secrets to environment and branch across Kubernetes, Terraform, and OpenTofu, plus bulk SAST false positive detection and agentic vulnerability resolution generating ready-to-merge fixes. Flow Creator Agent creates automation flows from plain-language descriptions, and GitLab Credits usage caps are now generally available.
32
Deloitte strengthens AI governance to support trusted enterprise adoption
Deloitte expanded AI Controls and Assurance services to close governance gaps, noting only 21% of firms have mature agentic AI governance.
Deloitte announced expanded AI Controls and Assurance services spanning AI governance frameworks, risk assessments, model validations, AI-enabled internal audit, ecosystem integration with hyperscalers, and regulatory readiness including SOC reporting. The launch cites Deloitte's State of AI in the Enterprise finding that 74% of companies plan to deploy agentic AI within two years while only 21% report mature governance for autonomous agents. The offerings align with Deloitte's Trustworthy AI framework and target the AI lifecycle from exploration to enterprise-scale deployment.
18
30
30