Data-Poisoning Audits for Causal Effect Estimation
Summary
A new data-poisoning audit framework addresses the vulnerability of observational causal analyses, particularly those pooling records across diverse sources, to append-only attacks. These attacks strategically add plausible records to alter a reported treatment effect. The framework, designed for augmented inverse-probability-weighted (AIPW) estimation, requires an analyst to specify a finite catalog of feasible records, an append budget, and nested source capacities. It proposes a greedy scan to compute the exact finite-sample worst-case movement when preprocessing and nuisance fits are held fixed. For scenarios involving nuisance refitting, a total-influence score is derived, combining direct record contribution with its effect through propensity and outcome models. Additionally, a conservative finite-budget bound is provided for fully refitted estimates. Extensive simulations validate the exact results, demonstrating material sensitivity at small append budgets in multisite and public-data analyses. This framework translates adversarial data-composition risk into quantifiable movement curves and critical budgets, supporting more reliable causal reporting and the design of source-level safeguards.
Key takeaway
For AI Scientists and Data Scientists evaluating the reliability of causal effect estimates from pooled observational studies, traditional robustness checks are insufficient against strategic data additions. You should implement data-poisoning audits to proactively assess the vulnerability of your causal pipelines. Use the audit's movement curves and critical budgets to understand potential estimate shifts, design source-level safeguards, and inform more transparent causal reporting, especially in high-stakes applications.
Key insights
Data-poisoning audits quantify causal estimate vulnerability to strategic record additions under capacity constraints.
Principles
- Causal estimates from pooled observational data are vulnerable to append-only attacks.
- Robustness guarantees against model error do not protect against strategic data composition changes.
- Inverse-propensity-weighted outcome residuals can become large, creating attack surfaces.
Method
Specify a feasible record catalog, nested source capacities, and an append budget. Use a greedy scan for fixed-pipeline movement or total-influence for refit-aware ranking.
In practice
- Quantify vulnerability by translating adversarial risk into movement curves.
- Use decision-instability budgets to find minimum records needed to cross thresholds.
- Evaluate inverse-weight capping for clean-data precision versus poisoning exposure.
Topics
- Causal Inference
- Data Poisoning
- Adversarial Robustness
- Average Treatment Effect
- AIPW Estimation
- Influence Functions
Best for: Research Scientist, CTO, VP of Engineering/Data, AI Scientist, Data Scientist, AI Security Engineer
Related on AIssential
See Counsel's argued verdicts on the open AI decisions leaders are weighing →
Editorial summary, takeaway, and curation by AIssential. Original article published by stat.ML updates on arXiv.org.