Logging and monitoring guardrails protect the audit trail, and block the teams that tune it
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
8 guardrails in the library address logging and monitoring: 4 AWS, 2 Azure, 2 Google Cloud. The first in the list, "Deny enabling and disabling AWS Config", denies stopping or deleting AWS Config recorders, delivery channels, rules and aggregators, and putting new configuration, unless the caller is the privileged role.
All risk classes ยท Download the library
Guardrails in this class protect the records that show what happened: AWS Config, CloudTrail, GuardDuty and VPC flow logs, plus diagnostic settings in Azure. The library holds 8. They break tuning. Denying changes to AWS Config means teams cannot add their own Config rules or recorders outside the privileged role. The GuardDuty entry lists guardduty:ArchiveFindings and guardduty:CreateFilter, so day-to-day findings handling also needs the privileged role. The flow log entry has no exception condition, so cleanup automation is denied too. Azure's deployIfNotExists is not a blocking effect: matching resources are marked noncompliant until a remediation task runs.
What these guardrails break
- Deny enabling and disabling AWS Config (AWS): Teams cannot add or change their own Config rules or recorders outside the privileged role; the README notes AWS Control Tower already applies a similar default control.
- Deny modifications to specific CloudTrail trails (AWS): The resource is a placeholder trail name that must be replaced; the README notes an organization trail already prevents member account users from altering it.
- Deny disabling or modifying Amazon GuardDuty (AWS): The action list includes guardduty:ArchiveFindings and guardduty:CreateFilter, so day-to-day findings handling also needs the privileged role.
- Deny deleting VPC flow logs (AWS): The policy has no exception condition, so it applies to every IAM user, role and the root user in the affected member accounts, including cleanup automation that deletes flow logs.
- Deploy diagnostic settings for Key Vault to Event Hub (Azure): DeployIfNotExists is not a blocking effect: matching resources are marked non-compliant and no action is taken on them until a remediation task runs.
- Application Insights components should block non-Entra ingestion (Azure): Existing components that accept unauthenticated ingestion are marked non-compliant but not changed.
- Require predefined policies for VPC flow logs (Google Cloud): Google documents that subnetworks in scope must have flow logs enabled with the required minimum sampling rate, where by default any settings are allowed.
- Disable Audit Logging exemption (Google Cloud): Google documents that it does not affect audit-logging exemptions that existed before the constraint was enforced.
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
Related pages
Sources
- Deny enabling and disabling AWS Config, read 10 Nov 2026
- Deny modifications to specific CloudTrail trails, read 10 Nov 2026
- Deny disabling or modifying Amazon GuardDuty, read 10 Nov 2026
- Deny deleting VPC flow logs, read 10 Nov 2026
- Deploy diagnostic settings for Key Vault to Event Hub, read 10 Nov 2026
- Application Insights components should block non-Entra ingestion, read 10 Nov 2026
- Require predefined policies for VPC flow logs, read 10 Nov 2026
- Disable Audit Logging exemption, read 10 Nov 2026
Last reviewed 16 Nov 2026.