mlsanityData to 7 Oct 2026

Practical Whole-System Provenance Capture

arXiv 1711.05296 ↗First posted 14 Nov 2017cs.CRcited by 19

Not on the map. Why?

Abstract (arXiv)

Data provenance describes how data came to be in its present form. It includes data sources and the transformations that have been applied to them. Data provenance has many uses, from forensics and security to aiding the reproducibility of scientific experiments. We present CamFlow, a whole-system provenance capture mechanism that integrates easily into a PaaS offering. While there have been several prior whole-system provenance systems that captured a comprehensive, systemic and ubiquitous record of a system's behavior, none have been widely adopted. They either A) impose too much overhead, B) are designed for long-outdated kernel releases and are hard to port to current systems, C) generate too much data, or D) are designed for a single system. CamFlow addresses these shortcoming by: 1) leveraging the latest kernel design advances to achieve efficiency; 2) using a self-contained, easily maintainable implementation relying on a Linux Security Module, NetFilter, and other existing kernel facilities; 3) providing a mechanism to tailor the captured provenance data to the needs of the application; and 4) making it easy to integrate provenance across distributed systems. The provenance we capture is streamed and consumed by tenant-built auditor applications. We illustrate the usability of our implementation by describing three such applications: demonstrating compliance with data regulations; performing fault/intrusion detection; and implementing data loss prevention. We also show how CamFlow can be leveraged to capture meaningful provenance without modifying existing applications.

Key facts. Cited by 19 papers in the map (data through 7 Oct 2026). First posted on arXiv 14 Nov 2017.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2021: 2; 2022: 1; 2023: 3; 2024: 0; 2025: 2; 2026: 11.

19 papers.

Sort:

By area:

  1. 2026Formal Policy Enforcement for Real-World Agentic Systemscited by 31
  2. 2023Kairos: Practical Intrusion Detection and Investigation using Whole-system Provenancecited by 30
  3. 2021threaTrace: Detecting and Tracing Host-based Threats in Node Level Through Provenance Graph Learningcited by 22
  4. 2023MAGIC: Detecting Advanced Persistent Threats via Masked Graph Representation Learningcited by 20
  5. 2026Agent libOS: A Runtime Substrate for Capability-Controlled Self-Evolving LLM Agentscited by 8
  6. 2021ANUBIS: A Provenance Graph-Based Framework for Advanced Persistent Threat Detectioncited by 3
  7. 2025OMNISEC: LLM-Driven Provenance-based Intrusion Detection via Retrieval-Augmented Behavior Promptingcited by 3
  8. 2026DeepStage: Learning Autonomous Defense Policies Against Multi-Stage APT Campaignscited by 3
  9. 2025Deep Learning-based Intrusion Detection Systems: A Surveycited by 2
  10. 2023TBDetector:Transformer-Based Detector for Advanced Persistent Threats with Provenance Graphcited by 1
  11. 2026PIDSMaker: Building and Evaluating Provenance-based Intrusion Detection Systemscited by 1
  12. 2026Observability for Delegated Execution in Agentic AI Systemscited by 1
7 more
  1. 2022Flurry: a Fast Framework for Reproducible Multi-layered Provenance Graph Representation Learningcited by 0
  2. 2026Agentic Data Environmentscited by 0
  3. 2026How Benchmarks and Evaluation Protocols Shape Conclusions in Provenance-Based Intrusion Detectioncited by 0
  4. 2026AUDITA: certified auditing and causal attribution of adverse outcomes in autonomous multi-agent systemscited by 0
  5. 2026Structurally Close, Temporally Distant: Measuring Security Exposure in Long-Horizon LLM Agentscited by 0
  6. 2026Runtime Authorization Consistency Checking for MCP-based Agentic Workflowscited by 0
  7. 2026Hearsay: Can an Auditor Trust the Record a Deployed Agent Harness Writes?cited by 0