Federated Agent Audit
Trace and audit any multi-agent system for privacy & compliance risks — with the central auditor never seeing raw content.
pip install federated-agent-audit
Think LangSmith/Langfuse for multi-agent systems, but federated — your prompts and outputs never leave the agents' own environments. Two pillars, framework- and scenario-agnostic:
- Behavior tracing — capture the real agent-to-agent interaction graph (who sent what to whom, tool calls, hand-offs) from CrewAI · LangGraph · AutoGen · OpenAI Agents · LlamaIndex, or any custom orchestration.
- Federated desensitized audit — each agent audits locally; the central auditor only ever sees hashed, pseudonymized, DP-noised metadata, yet detects the compositional privacy/compliance risks that emerge across agents.
The hard part, proven. Detection has to survive desensitization. Run every benchmark scenario through the full 6-layer desensitizer and differential privacy and the audit still holds F1 ≈ 0.91 (ε 0.5–3.0) with zero raw-content leakage — where a naive design collapses to ~0.17 specificity.
Who's this for? Anyone running a multi-agent system who needs to observe and govern its behavior — with extra pull for teams who can't ship raw prompts to a third-party vendor (regulated data, on-prem, data residency). A single-LLM-app on-ramp is built in (the firewall below).
30-Second Quick Start
New here? Start with the firewall — it works on a single LLM call, no multi-agent setup. The multi-agent audit is the depth you grow into.
from federated_agent_audit import scan
result = scan("Zhang Wei's SSN is 123-45-6789, salary $185,000")
print(result["clean"]) # False
print(result["detected"]) # ['SSN', 'salary']
print(result["text"]) # "Zhang Wei's [REDACTED] is [SSN], [REDACTED] [DOLLAR_AMOUNT]"
echo "credit card 4532-1234-5678-9012" | federated-audit scan
# REDACTED Detected: credit card
Protect Your LLM Calls
Intercept every OpenAI/Anthropic response automatically — the single-app on-ramp. Production-hardened: fail-open (the firewall can't crash your app), streaming blocked the moment a violation accumulates, and sensitive content inspected inside tool-call arguments.
from federated_agent_audit import firewall
fw = firewall(["salary", "SSN", "diagnosis"])
fw.patch_openai() # done — every response (incl. streaming + tool calls) is now checked
response = client.chat.completions.create(model="gpt-4o", messages=[...])
# Sensitive content in the response is already redacted
The Problem
Multi-agent systems create compound privacy risks that single-agent tools can't detect:
- Agent A shares salary data with Agent B (allowed by A's policy)
- Agent B forwards a "summary" to an external partner (allowed by B's policy)
- Result: salary leaked outside the company — neither agent broke its own rules
Existing observability tools (LangSmith, Langfuse) require uploading raw prompts to their servers. This framework audits agent interactions without the central auditor ever seeing raw content.
📖 Worked case study — a leak that emerges only from
combining two policy-compliant agents, caught with the raw PHI/PII never
leaving the agents (python examples/case_study_healthcare_leak.py).
+---------------+
| Central | Phase 2: Network audit
| Auditor | (desensitized metadata only)
+-------+-------+
|
+---------------+---------------+
| | |
+------+------+ +----+----+ +--------+------+
| Local Audit | | Local | | Local Audit | Phase 1
| (Agent A) | | (Agt B) | | (Agent C) |
+-------------+ +---------+ +---------------+
raw content raw content raw content
stays here stays here stays here
See ARCHITECTURE.md for the two-party model (edge vs. center), deployment topologies, and the tamper-evidence guarantees.
Multi-Agent Trace & Audit
The integrations capture the real agent-to-agent interaction graph — exactly
what the compositional / cascade / cross-domain detectors analyze. Everything is
built on MultiAgentTracer, which works with any framework (or none):
from federated_agent_audit import MultiAgentTracer, PrivacyPolicy
tracer = MultiAgentTracer()
tracer.register_agent("hr_bot", PrivacyPolicy(agent_id="hr_bot", must_not_share=["salary"]))
# Each call is a real directed edge; taint (domains, sensitivity, origin,
# hop count) propagates across hops automatically.
tracer.record_handoff("hr_bot", "summary_bot", "Zhang Wei earns $185k", origin="zhang_wei")
tracer.record_handoff("summary_bot", "external_bot", "candidate compensation summary")
result = tracer.network_audit() # Phase-2 central audit
incidents = tracer.aggregated() # denoised, actionable alerts
Tracing, not just auditing. See what your agents did — chronologically and desensitized — whether or not anything went wrong. No raw content, ever:
tracer.timeline() # [{seq, agent, to, action, domains, sensitivity, local_action, timestamp}, ...]
tracer.summary() # per-agent sent/received/internal counts + domains touched
tracer.export() # full interaction graph as a JSON-able dict (hashes + metadata, no raw text)
It catches the compound leak no single agent's policy can see — and the central
auditor still never touched the raw data (python examples/multiagent_trace_demo.py):
Incidents: 5 alert_summary={'critical': 3, 'high': 2}
[CRITICAL] cross_domain_leak — Sensitive health data reaches social domain via 2-agent chain
[CRITICAL] cross_domain_leak — Sensitive finance data reaches social domain via 2-agent chain
[CRITICAL] taint_spreading — Data from origin 'zhang_wei' spread to 4 agents across the network
[HIGH] inference_accumulation — external_bot accumulated high inference risk (77%)
[HIGH] compound_scope_escalation — 3 agent pairs exceed authorized scope
Privacy verification (central reports): hr_bot → clean health_bot → clean summary_bot → clean
Framework Integrations
# CrewAI — captures agent delegation (Delegate/Ask coworker) as A→B edges
from federated_agent_audit.sdk import crew_audit
crew = crew_audit(crew, default_policy=policy)
crew.kickoff(); result = crew._federated_tracer.network_audit()
# LangChain / LangGraph — per-node identity + node-to-node hand-offs
from federated_agent_audit.sdk import langchain_callback
handler = langchain_callback(default_policy=policy) # asynchronous=True for async graphs
graph.invoke(input, config={"callbacks": [handler]}); result = handler.tracer.network_audit()
# AutoGen / AG2 — hooks every agent-to-agent message
from federated_agent_audit.sdk import autogen_audit
tracer = autogen_audit([assistant, user_proxy, critic], default_policy=policy)
user_proxy.initiate_chat(assistant, message="..."); result = tracer.network_audit()
# OpenAI Agents SDK — captures first-class handoffs
from federated_agent_audit.sdk import openai_agents_hooks
hooks = openai_agents_hooks(default_policy=policy)
await Runner.run(triage_agent, input="...", hooks=hooks); result = hooks.tracer.network_audit()
# LlamaIndex AgentWorkflow — captures hand-offs from the event stream
from federated_agent_audit.sdk import llamaindex_handler
h = llamaindex_handler(default_policy=policy)
async for event in workflow.run(user_msg="...").stream_events(): h.handle_event(event)
result = h.tracer.network_audit()
# Generic Python — single-agent decorator
from federated_agent_audit import audited
@audited(policy, to_agent="downstream")
def my_agent(text: str) -> str: ...
What It Detects
| Risk | What happens | How we catch it |
|---|---|---|
| Cross-domain leak | Health data reaches a social/external agent | Domain boundary analysis on metadata |
| Cross-owner leak | My agent leaks my private data to another user's agent | Owner-boundary analysis (taint origin vs recipient owner) |
| Compositional inference | Agent collects health + identity = reidentification | Quasi-identifier assembly detection |
| Aggregation attack | 3 agents each share a fragment → hub rebuilds the profile | Multi-source convergence analysis |
| Cascading injection | Prompt injection propagates agent-to-agent like a worm | Infection tree + patient-zero attribution |
| Collusion | Two agents swap complementary data to reconstruct a profile | Bidirectional complementary-flow detection |
| Behavioral drift | Agent suddenly changes behavior (possible compromise) | Cross-session z-score monitoring |
| Negative inference | "I can't share that" confirms the data exists | Refusal pattern detection |
| Regulatory gap | EU AI Act / GDPR / CA SB 243 / COPPA unmet | Per-article compliance scoring |
Detection Effectiveness
A labeled benchmark (real compositional leaks vs. benign traffic) measures detection quality, not just speed:
python benchmarks/detection_eval.py # precision / recall / F1 (clean desensitized data)
python benchmarks/dp_eval.py # accuracy under full desensitizer + DP
On clean desensitized data (33 scenarios: 19 leak + 14 benign, incl.
adversarial cases — noise-buried leaks, diamond multi-path, same-domain
laundering, an injection worm, sensitivity-under-reporting evasion, multi-origin
aggregation, slow-drip identity assembly, cross-owner group leaks, collusion):
precision 1.0 / recall 1.0 / F1 1.0, zero raw-content leakage, stable across
thresholds 0.3–0.8. Locked by tests/test_detection_benchmark.py.
Under full desensitization + differential privacy (averaged over trials):
| DP epsilon | recall | specificity | F1 | raw leaks |
|---|---|---|---|---|
| 3.0 | 0.89 | 0.93 | 0.91 | 0 |
| 1.0 | 0.89 | 0.93 | 0.91 | 0 |
| 0.5 | 0.89 | 0.94 | 0.92 | 0 |
Domains are protected structurally (k-anonymity generalization), not by
per-domain randomized response — which fabricates spurious sensitive edges and
collapses precision to ~0.17 — and taint is preserved through DP. Locked by
tests/test_dp_robustness.py. Validated live against LangGraph (in-suite)
and CrewAI + OpenAI streaming (opt-in examples).
Forced-Embed, Attestation & Integrity
For deployments where the auditor ships inside each downloaded agent (a mandatory compliance SDK), the central auditor can verify the edges aren't cheating — tamper-evident, without ever seeing raw content:
- Attestation — build-fingerprint pinning + HMAC + per-agent sequence/hash
chain catches a modified-build / altered / omitted report. A pluggable backend
leaves a TEE upgrade path (
CallableBackend+evidence_validator) to go tamper-proof. - Cross-corroboration — recipients log desensitized receipts, so a sender that drops an edge is caught; a single bad actor can't hide.
- Challenge / reveal — the center can demand one committed entry with a Merkle proof, without browsing the rest.
Full loop: python examples/marketplace_forced_embed.py.
Compliance Engine
Built-in regulatory mapping for EU AI Act, GDPR, CA SB 243, and COPPA:
from federated_agent_audit import ComplianceEngine
engine = ComplianceEngine(eu_users=True, california_users=True, involves_children=False)
report = engine.evaluate(audit_result)
print(report.overall_score, report.status) # 0.0–1.0 · compliant / partial / non_compliant
for gap in report.gaps():
print(f"{gap.regulation} {gap.article}: {gap.remediation}")
CLI & YAML Policies
federated-audit scan "Patient SSN is 123-45-6789" # scan text (or pipe via stdin)
federated-audit validate policies/*.yaml # validate policy files
federated-audit demo # quick multi-agent demo
federated-audit server --port 8000 # start the central audit server
# policies/hr_bot.yaml
agent_id: hr_bot
must_not_share: [salary, SSN, performance review]
acceptable_abstractions: {salary: compensation level, SSN: employee identifier}
sensitivity_threshold: 3
Installation
pip install federated-agent-audit # core
pip install "federated-agent-audit[crewai]" # + a framework adapter (or langchain/
# langgraph/autogen/openai-agents/llamaindex)
pip install "federated-agent-audit[transport]" # + the central audit server
pip install "federated-agent-audit[all]" # everything
How It Works
49 modules · 723 tests · 0 external API calls required
Local (Phase 1, at the edge): Network (Phase 2, at the center):
PrivacyGate (regex + PII) Cross-domain / cross-owner detection
SemanticDetector (4-tier) Compositional leak (quasi-id assembly)
TaintTracker (info flow) Cascade infection (patient-zero)
Desensitizer (6-layer) Aggregation / collusion / multihop
MemoryAuditor (write audit) Topology + blame attribution
Attestor (tamper-evidence) Compliance engine + risk aggregation
Privacy guarantee: the central auditor architecturally cannot reconstruct raw content. Data is hashed, pseudonymized, and DP-noised before leaving local agents; Merkle-tree commitments make audit trails tamper-evident without revealing entries.
Development
git clone https://github.com/Justin0504/federated-agent-audit
cd federated-agent-audit
pip install -e ".[dev,langchain,langgraph,transport,yaml]"
pytest # 723 tests
ruff check src/ tests/ benchmarks/ # lint
python examples/multiagent_trace_demo.py
Contributions welcome — see CONTRIBUTING.md, the roadmap, and issues tagged good first issue.
License
Apache 2.0
Metadata
Release files for federated-agent-audit 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| federated_agent_audit-0.6.0.tar.gz | 229.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| federated_agent_audit-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 409.9 kB
Release files / federated_agent_audit-0.6.0.tar.gz
| Download URL | federated_agent_audit-0.6.0.tar.gz |
|---|---|
| Size | 229.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
436a82087164d3220543ba7ada2d74a689783c2174ef10a84d95f3a0e6c664b7
|
|
BLAKE2b-256 checksum How to use checksums |
2e2542f1ea917dfeb4cd2e82a613533f222db687ef3b42fd98cceda68126c801
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.
Transparency logRelease files / federated_agent_audit-0.6.0-py3-none-any.whl
| Download URL | federated_agent_audit-0.6.0-py3-none-any.whl |
|---|---|
| Size | 181.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3192eeb02b51782d5e9cb40d6ab3b9c89650649ad8d780d68b3a23fa117eb986
|
|
BLAKE2b-256 checksum How to use checksums |
9f066aa412473d720d13149d61341cf9ec3ddb5d89529d4e691b32cf80133b29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.
Transparency log