audit-workflow

Bi-directional configuration auditing compares what your repository actually contains against expected standards from templates, identifying missing items, extra configurations, and matches in one pass. This catches both gaps and unexpected settings that one-way validation would miss.

Yes. The audit workflow handles diverse configuration formats by detecting repository type and loading applicable standards, then performing two-way comparisons across all discovered configs to generate a unified report with violations and warnings.

For each discrepancy, you receive three remediation options: conform your config to the template, update the template to match your needs, or ignore the violation. This gives you control over whether to standardize or evolve your standards.

Scope detection dynamically determines audit boundaries based on your intent, supporting entire repository scans, specific application configs, or recently modified files. This lets you focus validation on relevant changes without unnecessary overhead.

One-way validation misses extra or unexpected configurations that can cause runtime issues or security gaps. Bi-directional auditing identifies both missing and extra elements, giving complete visibility into compliance violations and configuration drift.