audit-trends

To track audit findings trends over time, you aggregate timestamped JSON snapshots from your audit directory to compute new, fixed, reopened, and lingering findings. This process maintains per-finding histories using first_seen and last_seen timestamps to produce a structured trend report.

Calculating MTTR per severity helps with audit health analysis by deriving the median time-to-resolution across different severity levels. This metric, combined with a per-window health score, enables teams to prioritize remediation efforts and identify patterns in risk and resolution speed.

Yes, you can use audit snapshot data to detect security regressions. By applying historical trend analysis across timestamped snapshots, the system identifies phase regressions and provides a time-series view to guide and adjust your remediation planning accordingly.

Yes, you need a specific schema to validate your audit findings JSON files. The trend aggregation requires loading findings JSON files from the audit directory and validating them against the audit-finding.schema.json file before processing the historical data.

The best way to generate an audit health score from historical snapshots is to aggregate timestamped findings data and compute new, fixed, and lingering items per window. This yields a per-snapshot health score that surfaces deterioration or improvements over time.