Add Azure diagnostic pipeline evidence gates#1642
Open
Desalzes wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1624.
This strengthens
azure-reviewso diagnostic settings cannot pass CIS Section 5 from existence alone. It requires evidence for subscription and resource diagnostic coverage, required categories/category groups, destination retention, destination hardening, authorization scope, and sample log delivery.Changes
AZ-DIAG-01throughAZ-DIAG-05finding IDs for missing resource coverage, category gaps, retention gaps, destination hardening gaps, and missing sample delivery.AuditEvent,category_group = "allLogs", destination retention/hardening, CMK, and Not Evaluable sample delivery.Validation
git diff --check