Do infrastructure changes go through code review and pipelines, with console changes in production flagged?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 30 of the assessment asks: Do infrastructure changes go through code review and pipelines, with console changes in production flagged? A change that bypasses review is a change nobody checked against your own rules. It comes from Microsoft cloud security benchmark PV-1 and carries weight 2 in the guardrails and drift domain.
Start the assessment ยท All 40 questions
Why it matters
A change that bypasses review is a change nobody checked against your own rules.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, console writes are flagged | 1 |
| Mostly code, console not monitored | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- Query CloudTrail for write events where userAgent or sessionContext indicates console or user sessions in production accounts.
- Azure
- Query the Activity Log for write operations by users rather than the pipeline service principal in production subscriptions.
- Google Cloud
- Query Cloud Audit Logs admin activity for write calls by user principals rather than the pipeline service account.
The fix
Alert on write actions from the console in production and make the pipeline the only role that can change infrastructure. Effort: high.
Where it comes from
- Microsoft cloud security benchmark PV-1: Define and establish secure configurations
- NIST SP 800-53 Rev. 5 CM-2: source
Related pages
Sources
- Microsoft cloud security benchmark PV-1, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 CM-2, read 16 Nov 2026
Last reviewed 16 Nov 2026.