Skip to content

[new-research] arXiv:2610.03434 — Persona Guardrail: A Production-Grade Defense Framework for Agentic Systems #194

Open

Description

@github-actions

New arXiv Research Paper

arXiv ID: 2610.03434
Title: Persona Guardrail: A Production-Grade Defense Framework for Agentic Systems
Authors: Bijeeta Pal, Sridhar Reddy Maddireddy, Muhaimin Bin Munir, Zoltan Puha, Max Zhurovich, Adi Raghavendra, Sean Tout
Published: 2026-10-02T15:13:38Z
URL: https://arxiv.org/abs/2610.03434

Abstract (first 300 chars)

Large language model-based agents are increasingly deployed to perform domain-specific tasks by interacting with enterprise knowledge, tools, and external services. Existing runtime guardrails primarily target prompt injection and other attack-specific behaviors under a black-box threat model, but p…

Suggested OWASP Mapping

LLM01, ASI01, ASI02

Suggested Action

Review this paper against the OWASP GenAI Crosswalk entries and update relevant mapping files if new attack patterns or mitigations are identified.

Activity

  1. emmanuelgjr commented on Oct 9, 2026

    @emmanuelgjr
    Contributor

    Routed to the benchmark catalogue — rule 3.

    Persona Guardrail: A Production-Grade Defense Framework for Agentic Systems presents a runtime guardrail that enforces functional boundaries for customer-facing agents. It also introduces PAGE (Persona-Aware Guardrail Evaluation), which the full abstract describes as "a benchmark for evaluating function-specific guardrails across benign, adversarial, and out-of-domain interactions on both user and agent turns".

    Routed per docs/TRIAGE_RULES.md:

    • Not an incident. "Currently deployed in production" describes the defense, not a failure of a deployed system.
    • A catalogue row for PAGE. Rule 3 covers a benchmark or evaluation dataset meant for testing systems, so PAGE gets a row in evals/EXTERNAL_BENCHMARKS.md. The guardrail itself is literature and is noted.
    • Release: the arXiv record links no benchmark release, so the row will record it as not released.
    • Provenance: the benchmark evaluates the authors' own product. The row will say so, as the APort Vault row does.

    The row's OWASP entry column lands as DRAFT — SME review required. This issue closes when #222 merges. A row for a benchmark introduced by a defense paper follows the maintainer ruling of 2026-10-09, recorded in rule 3 by that PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions