Papers for

compliance officers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Agentic ai system detects and ranks compliance gaps in high risk systems

ComplianceAtlas: A Taxonomy-Driven Agentic AI Framework for Automated AI Act Gap Analysis and Remediation

Abstract: Assessing regulatory compliance for high-risk AI systems requires systematic identification of technical gaps such as missing controls, in- adequate processes, or shallow evaluation of practices. Compliance officers typically admin- ister structured questionnaires collecting evi- dence of current practices, where organizations respond with descriptions of their existing pro- cesses, technical capabilities, and architectural choices. However, translating these compli- ance questionnaire responses into typed, ac- tionable gap diagnoses remains unsystematic. In this paper, we present a literature-grounded taxonomy of technical compliance gaps cover- ing areas such as accuracy, robustness, logging, and human oversight, and embed it in GapTo- Compliance, a two-stage agentic framework coordinating two specialized agents: a Gap Extraction Agent that performs hierarchical rea- soning from compliance areas to specific gap types, and a Remediation Planning Agent that ranks remediation actions from a remediation catalog via multi-signal scoring combining se- mantic similarity, regulatory alignment, and effort estimation. We evaluate this framework against four automatic compliance gap detec- tion baselines across 9 AI systems and 6 AI families. Our approach achieves a gap-type F1 of 0.831 (vs. 0.533 for the strongest baseline) and remediation P@5 of 0.872 (vs. 0.635 for retrieval methods), demonstrating promising potential for automated compliance workflows. The structured agent coordination reveals a path toward human-in-the-loop compliance systems where automated gap extraction reduces expert burden while maintaining auditability, and the taxonomy-driven design enables extension to emerging regulatory frameworks beyond

Mon 2 NovArtificial Intelligence
The gist
Making sure AI systems follow rules can be hard because companies describe their processes in words, but it's tough to turn that into clear lists of what is missing or needs fixing. The authors created a list of common technical compliance gaps and built a two-part AI framework that first finds specific issues from company answers, then suggests fixes ranked by how well they fit regulations and effort needed. They tested their system on many different AI systems and it found compliance gaps and fixes more accurately than previous automatic methods. This approach could help compliance experts by reducing their workload while keeping audits clear.
Open → 2611.03121v1

Information flow modeling improves role-based AI Act compliance assessments

Transparent Information Flow Modeling for Role-Aware AI Act Assessment

Abstract: The European Union's Artificial Intelligence Act introduces a structured framework for governing high-risk AI systems, emphasizing transparency, risk management, and role-specific accountability. However, current assessment practices often rely on monolithic system views or disconnected checklists, limiting their ability to capture the socio-technical complexity of real-world deployments. We explore the use of the Information Flow Methodology (IFM), a modeling-based approach to AI Act compliance assessment. IFM represents decision systems -- whether algorithmic, human, or hybrid -- as networks of information sites and transformation channels, enabling structured analysis of how information, decisions, and responsibilities flow across organizational and technical boundaries. We apply IFM in a real-world case involving a recruitment support tool used by a public-sector organization, evaluating both the Provider's system and the Deployer's recruitment process. Our results demonstrate that IFM can serve as a scaffold to bridge both component-based and holistic perspectives, and how technical systems are situated within socio-technical contexts. In doing so, IFM supports transparency, identifies risk pathways, and enables alignment analysis between intended and actual use. We argue that such modeling provides a foundational tool for effective, context-sensitive AI governance and accountability -- offering capabilities beyond conventional checklist-based assessments.

Mon 12 OctArtificial Intelligence
The gist
The European Union's AI Act aims to control risky AI systems by ensuring transparency and clear responsibilities. The authors show that by modeling how information and decisions move through both AI and people, they can better understand and assess the risk and accountability of AI in real workplaces. They tested this approach on a real recruitment tool used by a government agency and found it helps reveal where information risks may hide and whether the system is used as intended. This modeling method goes beyond simple checklists by connecting technical details with social and organizational factors.
Open → 2610.16916v1

AI agent evaluation gains a clear, verifiable semantic layer

EIO-Agents: The Missing Semantic Layer for AI Agent Evaluation

Abstract: AI agents are entering production in increasingly consequential environments without a shared semantic standard for what their evaluations actually mean. Scores, traces, judge outputs, and multi juror findings are increasingly used to justify readiness and release decisions, yet they often do not specify what evidence supports a claim, what that evidence can establish, or how the claim leads to a decision. We introduce EIO-Agents, an open specification for interoperable AI agent evaluation built on two layers. The Evaluation Intelligence Ontology (EIO) provides the semantic layer through typed evidence, versioned behavioral predicates, evidence contracts, claims, witness rules, proof status, recurrence, and computable derivations for metrics, findings, controls, and PASS, REVIEW, or BLOCK decisions. The Portable Evaluation Record (PER) provides the system of record: a canonical, content addressed representation of one evaluation that preserves the evidence to decision chain and can be re derived, explained, and verified. Scores summarize, juries interpret, and traces record, but none of them define what the evidence means or what it can prove. EIO provides that missing semantic contract, while PER preserves the resulting evaluation as a portable and verifiable system of record. As AI agents assume greater operational responsibility, evaluation must become more than a collection of scores and verdicts; it must become an accountable artifact whose meaning, evidence, limitations, and decisions can be independently checked.

Tue 6 OctArtificial IntelligenceMultiagent Systems
The gist
Evaluations of AI agents today often rely on scores or judgments that don’t clearly explain the evidence or reasoning behind decisions. The authors introduce EIO-Agents, a new standard that adds meaning and structure to how AI evaluations are recorded and interpreted. It precisely links evidence to claims and decisions, and stores this as a portable, verifiable record. This approach can help make AI assessments more trustworthy and easier to check independently.
Open → 2610.07675v1

Framework defines how to verify claims about AI agent actions

Auditable Claims about AI Agents

Abstract: Organizations make claims about their AI agents: a person approves every external email, every action is logged, an evaluation shows the agent is safe to deploy. Article 12 of the EU AI Act requires high-risk systems to allow the automatic recording of events but does not say which records settle a given claim. The position is one sentence: to be checked, a claim about an agent must first name its policy, its scope, the records that would settle it, and who writes them. Adapting the preconditions of an assurance engagement, we call a claim auditable when these elements and a decision rule are fixed before any verdict and the records are obtainable. This extends the Policy Checkability dimension of our Auditable Agents framework from single actions to claims. Agents add three conditions: coverage by an independent record, authorization bound to each action's arguments, and completeness beyond integrity. Under an explicit model, we prove that support is impossible without each wherever its hypotheses hold. A claim-check table applies the method to six common claims, anchored in current NIST, IETF, and OWASP drafts. A worked case follows one claim through five evidence states. We close with a practice box and steps for operators, buyers, auditors, and standard setters.

Mon 5 OctArtificial IntelligenceComputation and LanguageComputers and Society
The gist
Organizations often say things like 'every email is approved' or 'actions are logged' about their AI systems, but it's unclear what records prove these claims. The authors propose a way to make such claims 'auditable' by clearly stating the policy, scope, required records, and who creates them before checking. They add conditions like independent records and completeness to ensure trust. This method helps clarify what evidence is needed to confirm claims about AI behavior under rules like the EU AI Act.
Open → 2610.07459v1

Trust digital systems continuously beyond initial design in AI age

From Trust-by-Design to Continuous Trust in the Era of Artificial Intelligence

Abstract: Trust is crucial in the digital world, particularly in the age of systems based on artificial intelligence. Traditionally, system correctness is demonstrated by proving that the system satisfies the required properties. However, digital systems involve humans, who can make mistakes, break rules, or even intentionally cheat the system. Technical devices may also malfunction or cause errors. Therefore, external stakeholders need to trust a system throughout its operation. To address this challenge, we propose the concept of continuous trust. In this paper, we present a detailed explanation of this concept, based on a running example of a business's refund department. The paper concludes with a discussion of related work, such as compliance checking and certification, as well as an outlook on further questions regarding the formalization and the necessary tool support.

Mon 5 OctSoftware Engineering
The gist
As digital systems increasingly use artificial intelligence, it's important not just to prove they work right from the start but to keep trusting them while they run. The authors show that mistakes by people or device errors can challenge trust after a system starts working. They introduce the idea of 'continuous trust'—a way to maintain confidence in a system throughout its operation. Using a business refund department example, they explain how this ongoing trust can be managed and discuss tools and rules that support it.
Open → 2610.05991v1

Zero knowledge AI output verification requires cryptographic oracles

Can AI Oversight Be Zero Knowledge?

Abstract: AI systems increasingly produce outputs from confidential data, such as a fitness-for-duty assessment from medical records or the predicted properties of a drug candidate from its secret structure. It is important to verify that such outputs are correct without revealing the underlying data. A recent line of work studies verification of AI outputs via interactive proofs and debate for oracle-aided computation, where correctness may depend on an oracle such as human judgment, a physical experiment, or the web. These works focus on verification by a verifier that runs much faster than the computation. However, such efficient verification is impossible for general oracle-aided computation, and these works therefore rely on additional assumptions. We focus instead on privacy: allowing the verifier to run in time polynomial in the computation, we ask whether interactive arguments for oracle-aided computation can be zero knowledge, so that the verifier learns nothing about the confidential data beyond the correctness of the output. We prove that, in general, they cannot. In the random oracle model, there are no zero-knowledge proofs for all oracle-aided computations, even if both the prover and the verifier are allowed to run much longer than the computation itself. The impossibility extends to debate, a canonical model for scalable oversight. On the positive side, we show that if the oracle attaches a cryptographic signature to each of its answers, then every oracle-aided computation can be verified in zero knowledge with an efficient prover and verifier, assuming only collision-resistant hash functions. Beyond privacy, this also gives an alternative approach to scalable oversight that relies neither on an honest opponent, as in debate, nor on the robustness of the computation, as in prior single-prover protocols.

Thu 1 OctArtificial IntelligenceComputational ComplexityCryptography and Security
The gist
AI sometimes needs to check answers calculated from secret or private information without revealing that secret data. The authors found that it's generally impossible to verify these answers in a totally secret way (called zero knowledge) if the verification uses external sources, like human opinions or experiments. But if the external source signs its answers securely, then it becomes possible to verify the AI's answer without leaking anything extra. This gives a new way to make sure AI results are correct and private at the same time.
Open → 2610.01995v1

Automated system checks documents for legal rule compliance accurately

ARCCS: An Automated Regulatory Compliance Checking System

Abstract: Regulatory compliance checking - deciding whether a target document satisfies the obligations of a regulation - requires interpreting dense legal text, identifying which provisions apply, and grounding each decision in explicit evidence. We present ARCCS, an end-to-end, automated, agentic, and regulation-agnostic Legal NLP system for compliance checking. ARCCS decomposes raw regulatory text into atomic, traceable requirements and evaluates a target document against them using retrieved evidence, confidence scores, and human-interpretable justifications. This design decouples compliance assessment from any fixed regulatory template or predefined rule set, enabling the pipeline to operate over regulations of varying size and structure. We evaluate ARCCS in two complementary settings. First, in a GDPR policy-document evaluation, LLM-based judges find its decisions and justifications legally and evidentially consistent in up to 96.67% of the assessed cases. Second, on an EU public-procurement benchmark comprising more than 1,200 individual rule checks, the system attains 98.8% accuracy in violation detection. ARCCS is, to our knowledge, the first fully open-source system for end-to-end regulatory compliance checking and auditable report generation.

Thu 1 OctComputation and Language
The gist
It can be hard to know if a document follows complicated legal rules because those rules are written in dense language. The authors created ARCCS, a computer program that breaks down legal text into small clear requirements and checks if documents meet them. The system uses evidence to explain its decisions and works with many types of regulations, not just one set of rules. Tests show it is very accurate in checking compliance with privacy laws and public procurement rules.
Open → 2610.01345v1

Interpretable detection of ambiguous clauses in legal contracts

LAURA: Knowledge Distillation for Interpretable Ambiguous Clause Identification in Legal Contracts

Abstract: Legal contracts contain ambiguities that expose enterprises to financial and legal risks. Some ambiguities allow flexible interpretation without triggering disputes, while others lead to significant legal conflicts. This makes identification alone insufficient, and interpretable rationale analysis essential. We propose LAURA, a post-training framework for interpretable ambiguous clause identification. LAURA leverages knowledge distillation with an IRAC-Unlearning prompting technique to transfer knowledge from a teacher LLM to an open-weight student model (<=1B parameters), which is then trained using a joint objective combining classification and rationale generation losses. The framework supports both legal and non-legal stakeholders in making informed decisions about which ambiguities require further attention. Extensive experiments across 7 baselines and 7 open-weight models demonstrate that LAURA with Flan-T5 (250M) delivers state-of-the-art interpretability over all interpretable baselines while matching the identification performance of the best-performing opaque baseline.

Tue 29 SeptComputation and Language
The gist
Legal contracts sometimes have unclear parts that can cause problems later on. Some unclear parts are okay, but others can cause serious legal trouble. The authors developed LAURA, a system that not only spots ambiguous contract sections but also explains why they are unclear. This helps lawyers and others decide which parts need careful review. Their approach uses a smaller model that learns from a larger AI to perform well and be understandable.
Open → 2609.36707v1

LLM agents can delete their own execution records without detection

LLM Agents Can Easily Tamper With Their Own Traces

Abstract: Asynchronous monitoring, incident investigations, and compliance audits primarily rely on agent traces to reconstruct what happened. These analyses assume that LLM agents cannot tamper with their own execution traces. We show that local LLM agents such as Claude Code, Codex, Antigravity, Open Code and Grok Build fail to enforce this boundary. All tested harnesses, except Muse Code, allowed agents to delete their traces when asked, without triggering monitor guardrails. We also validate that external attackers can exploit this gap to induce trace deletion. Finally, we show that trace tampering behavior emerges naturally in frontier models, when agents try to improve their rewards. We advise practitioners to ensure trace logging happens through an independent interception mechanism outside of the agent's control, preserving trace integrity even in cases of full host compromise. Overall, our findings identify a concrete failure of trace integrity in agent infrastructure which can be used to conceal misaligned behaviors like scheming or sabotage.

Thu 24 SeptCryptography and SecurityArtificial Intelligence
The gist
When AI programs called LLM agents operate, they usually create logs or traces to show what they did. These logs help people check if the AI behaved well. However, the authors found that many popular LLM agents can erase their own logs without being stopped, making it hard to know if they misbehaved. This weakness means bad actions can be hidden. The authors suggest that logging should happen outside the AI’s control to keep records safe.
Open → 2609.30266v1

Human ai teams improve auditing of generative ai systems

Who Does What in AI Auditing? Designing Human-AI Collaboration for Auditing Generative AI

Abstract: AI auditing increasingly incorporates AI agents to expand the scale and breadth of audit coverage, yet little is known about how auditing work should be divided without displacing human judgment. We introduce Human-Agent Audit Collaboration (HAAC), a workflow and system for structuring human-AI collaboration in AI auditing. Drawing on prior work and formative consultations with AI auditing practitioners, HAAC specifies how agents can support exploration, assessment, reporting, and review while preserving human oversight where contextual judgment is critical. We instantiate HAAC for conversational shopping agents and evaluate it through two studies. With 71 auditors, AI assistance increased attack success and broadened exploration, while also shaping later attacks and increasing auditors' reliance on AI-generated assessments and reports. Interviews with Responsible AI practitioners showed that actionable audits require visibility into coverage, reproducible attack trajectories, and evaluation of the auditing agents themselves. Our findings identify design considerations for effective and accountable human-AI auditing.

Mon 21 SeptHuman-Computer Interaction
The gist
Auditing AI systems can be tricky because people need to use their judgment alongside the tools they have. This paper presents a way to organize teamwork between humans and AI agents to check AI systems more thoroughly without losing human insight. They tested this method on conversational shopping assistants and found that AI helped humans explore more ways to find problems and made reports easier, though humans relied heavily on AI suggestions. Practitioners said that for audits to be useful, auditors need clear views of what was tested, ways to repeat tests, and ways to check the AI tools themselves.
Open → 2609.24986v1

Brain API enables clear intent-driven control for agent systems

Brain API: An Intent-Aware Control Plane for Policy-Governed Agentic Systems

Abstract: Contemporary cloud and distributed systems expose control through resource-centric abstractions: services, deployments, network flows, execution graphs. Agentic and tool-augmented systems have meanwhile shifted application logic toward intent-driven, adaptive execution. Existing control planes, workflow engines and service meshes lack abstractions for intent-level decision governance: they cannot represent high-level goals as first-class control objects, cannot enforce policy over the mapping from intent to execution plan, and cannot produce auditable records of why one execution path was chosen over its alternatives. Control logic is therefore embedded in application code, leaving systems brittle, opaque and hard to govern. We propose Brain API, an intent-aware control plane for policy-governed agentic systems. Its central contribution is the decision artifact: a durable, versioned, auditable record of how an intent became an executable plan, capturing which policies applied, which capabilities were evaluated, which alternatives were rejected, and why. A motivating use case is agentic datasets: datasets participating as policy-governed capabilities under residency, compliance and cost constraints. We evaluate a prototype of the decision layer against two external policy corpora we did not author. On the OPA Gatekeeper constraint library it agrees with the library's own published verdicts on 42 of 42 encodable cases, 19 admit and 23 deny. On Cedar example policies, labeled by differential testing against its reference implementation, a deliberately dissimilar domain exposed three defects in our model, including a default-allow assumption that would have inverted every authorization policy. The evaluation covers policy filtering and selection; context-signal and ranking remain design claims, and decision latency under load is unquantified.

Fri 18 SeptDistributed, Parallel, and Cluster Computing
The gist
Managing complex computer systems often means dealing with detailed technical steps, but this chip away at understanding why decisions are made. The authors designed Brain API, a system that tracks how high-level goals turn into specific actions by recording which rules apply and why some options were rejected. This helps make automated decisions more transparent and easier to manage, especially in systems where policies and compliance matter. They tested Brain API’s decision records using existing policy examples and found it matches or helps improve decision accuracy.
Open → 2609.21299v1

Enterprise AI assistants often break rules when pressured by users

PACT: Can Enterprise AI Assistants Be Trusted Under Pressure?

Abstract: As corporate AI adoption continues to grow, enterprise-grade LLM agents are being deployed into sensitive contexts such as hiring, healthcare, and finance. In these contexts, compliance with rules specified in an agent's system context is a first-order legal concern. Currently, no evaluation framework systematically measures which LLM models tend to violate compliance rules, especially under pressure from a persistent user, a hurried manager, or circumstances where violation is convenient or attractive. We introduce PACT (Pressure-Applied Compliance Testing), a benchmark for rule-following under pressure in AI agents assisting employees in daily tasks across twelve regulated enterprise domains and forty-eight scenarios, each set in a realistic multi-turn conversation. Each benchmark item pairs a standing rule against a rule-violating shortcut, and applies a battery of pressures across different wordings and system-prompt modes. We construct PACT component by component under strict LLM-as-judge auditing to ensure samples are unambiguous, ungameable, and realistic enough to avoid eliciting evaluation-aware behavior. We use PACT to profile LLM compliance across six complementary metrics that create a holistic picture of an AI assistant's robustness under pressure and throughout multi-turn conversations, its transparency, and ability to correctly discern where a rule applies. We aggregate this profile into PACTScore, a reliability-weighted compliance rate over all items and modes. Our results across 22 common LLM models spanning multiple providers and sizes show substantial variability in compliance across models and metric dimensions. Even the strongest assistants mis-apply a rule on 6 to 10% of items, and ordinary user pressure raises the violation rate by 65% on average. PACT highlights compliance risks in LLM assistants, motivating guardrails and careful model selection.

Wed 16 SeptComputation and LanguageArtificial IntelligenceComputers and Society
The gist
AI assistants used in businesses like healthcare and finance need to follow important rules. The authors created a test called PACT to see how well different AI models stick to these rules when users try to push them to break them. They found that even the best AI assistants make mistakes, especially when pressured by persistent or hurried users. PACT helps show where these AI systems might fail so companies can choose safer options.
Open → 2609.18605v1

Agentic AI audits require graded independence across three key factors

Who Audits Whom, on What Substrate, with What Evidence? An Independence-Graded Audit Protocol for Agentic AI

Abstract: Agentic AI systems plan, invoke tools and act with limited supervision; they are now both the subject of audits and, increasingly, the auditor. Independence, the foundation of assurance,is still applied to them as a binary. We argue that it must be graded along three orthogonal axes: principal independence (who controls the auditor), substrate independence (an auditor sharing the auditee's foundation-model family, toolchain or guardrails fails with it) and evidence independence (whether evidence is attestable rather than self-reported). Each axis has precedent; the contribution is to grade all three on a single audit, aggregate them by the weakest link, and apply the same rubric when the auditor is itself an agent. We give the model a formal basis by transplanting the beta-factor model of common-cause failure from reliability engineering, a seven-step protocol whose outputs a third party can verify, a structural detectability analysis of a procurement-controls agent audited at three grades, and a Monte Carlo study of the model in which a conventional internal audit of an agent-a real audit team, a second agent, provider logsp-surfaces 5.9% of the faults it could in principle see and none at all in half the fault classes. We map the triple to the EU AI Act as amended, ISO/IEC 42006, UK public-sector risk-management guidance and audit-regulator practice.

Wed 16 SeptArtificial IntelligenceCryptography and SecurityEmerging Technologies
The gist
Auditing smart AI systems that can plan and act independently is still done using simple yes-or-no rules about how separate the auditor is from the AI. The authors argue this approach is too basic and propose measuring independence in three different ways: who controls the auditor, whether the auditor uses the same underlying AI tools as the system being checked, and whether the evidence comes from verifiable sources instead of just the system itself. They developed a method to combine these three measures and tested it, showing that traditional internal audits often miss many faults. Their approach can be used to better assure AI system safety and is connected to existing AI laws and standards.
Open → 2609.18272v1

Measures for competent generative AI use at work show weak correlation

Beyond AI Literacy: A Structured Review and Exploratory Meta-Analysis of Measures for Competent Generative-AI Use

Abstract: Researchers assessing competent generative-AI use at work must choose among self-reports, objective tests, and measures of oversight and reliance. We conducted a structured, seeded review of 24 focal empirical publications, starting from the 2024 COSMIN-based review and adding a targeted update through 17 August 2026. We grouped the measures into four domains: knowledge and use, epistemic oversight, reliance calibration, and operational control of tool-using agents. In an exploratory meta-analysis, we pooled three direct subjective-objective correlations from one research program (REML r = .055; Hartung-Knapp 95% CI [-.047, .156]; combined reported N = 2,765). We could not resolve a discrepancy between the largest study's reported correlation and p-value, leaving its weight uncertain. Adding a synthetic mean of 12 cross-factor correlations from a fourth study gave r = .079 (95% CI [-.025, .181]). This sensitivity analysis concerns a broader comparison. From this small evidence base, we cannot establish a population correlation, validate workplace cutoffs, or justify substituting self-ratings for performance scores. We identified tests of foundation knowledge (AICOS-S and GLAT) and measures of verification, reliance, trust, and dependency. We found no validated individual-level instrument in the focal corpus that tests the full combination of agent scope, permissions, recovery, state isolation, independent review, and evidence-based closure; some cover subsets. We propose a four-layer workplace battery with non-compensatory decision rules, but have not tested its thresholds or whether it improves on other assessment approaches.

Mon 14 SeptHuman-Computer InteractionArtificial Intelligence
The gist
It is hard to measure how well people use AI tools at work because different kinds of tests, like self-ratings and performance tasks, don’t strongly agree with each other. The authors reviewed studies and found no clear way to replace actual performance tests with self-reports. They looked at tools that test knowledge and how people check or trust AI, but none cover all necessary skills. They propose a new testing approach but haven’t yet shown it works better.
Open → 2609.15624v1