NIS2 compliance
Network and Information Systems directive — DriftGuard maps your Terraform changes to NIS2 controls.
Which checks map to NIS2
NIS2 Article 21 requires “appropriate and proportionate technical measures” to manage risk. DriftGuard enforces a subset of those measures directly on the pull request that changes your infrastructure:
- 21(2)(a) risk analysis — Checkov + policy engine flag misconfigurations before merge.
- 21(2)(e) secure change control — a required GitHub Check gates merges; drift detection blocks stale plans.
- 21(2)(f) effectiveness review — the audit log records every decision for later assessment.
Policy rules
The measures above run automatically — nothing to enable. To block a specific NIS2-relevant pattern (an open ingress rule, a public bucket) rather than just warn on it, create a policy rule from the dashboard's Policies page; rules match on severity, resource pattern, or rule ID and can be set to block, warn, or alert.
Evidence per PR
Each pull request produces an evidence record referencing the NIS2 measures exercised, the check results, and the merge decision. Records flow into the append-only audit log. DriftGuard is early access and provides evidence to support a NIS2 program — it is not a substitute for a formal audit.