Deny disabling or modifying Amazon GuardDuty
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Deny disabling or modifying Amazon GuardDuty is an AWS guardrail written in service control policies. Denies GuardDuty actions that disable detectors or change filters, IP sets, members and publishing destinations unless the caller is the privileged role. What it breaks: the action list includes guardduty:ArchiveFindings and guardduty:CreateFilter, so day-to-day findings handling also needs the privileged role.
More logging and monitoring guardrails ยท About Service control policies
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Deny",
"Action": [
"guardduty:AcceptInvitation",
"guardduty:ArchiveFindings",
"guardduty:CreateDetector",
"guardduty:CreateFilter",
"guardduty:CreateIPSet",
"guardduty:CreateMembers",
"guardduty:CreatePublishingDestination",
"guardduty:CreateSampleFindings",
"guardduty:CreateThreatIntelSet",
"guardduty:DeclineInvitations",
"guardduty:DeleteDetector",
"guardduty:DeleteFilter",
"guardduty:DeleteInvitations",
"guardduty:DeleteIPSet",
"guardduty:DeleteMembers",
"guardduty:DeletePublishingDestination",
"guardduty:DeleteThreatIntelSet",
"guardduty:DisassociateFromMasterAccount",
"guardduty:DisassociateMembers",
"guardduty:InviteMembers",
"guardduty:StartMonitoringMembers",
"guardduty:StopMonitoringMembers",
"guardduty:TagResource",
"guardduty:UnarchiveFindings",
"guardduty:UntagResource",
"guardduty:UpdateDetector",
"guardduty:UpdateFilter",
"guardduty:UpdateFindingsFeedback",
"guardduty:UpdateIPSet",
"guardduty:UpdatePublishingDestination",
"guardduty:UpdateThreatIntelSet"
],
"Resource": "*",
"Condition": {
"ArnNotLike": {
"aws:PrincipalARN": "arn:aws:iam::${Account}:role/[PRIVILEGED_ROLE]"
}
}
}
]
}
- Blocks
- Denies GuardDuty actions that disable detectors or change filters, IP sets, members and publishing destinations unless the caller is the privileged role.
- Breaks
- The action list includes guardduty:ArchiveFindings and guardduty:CreateFilter, so day-to-day findings handling also needs the privileged role. (source)
- Test before applying
- As for every Service control policies guardrail: how to test before enforcing
- Mechanism
- Service control policies (SCPs): IAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles.
- Taken from
- open source set, MIT-0 (README states MIT-0; LICENSE file fetched, MIT-0 text, Copyright Amazon.com, Inc.): https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/LICENSE
What the policy text names
It names 31 actions or patterns: guardduty:AcceptInvitation, guardduty:ArchiveFindings, guardduty:CreateDetector, guardduty:CreateFilter, guardduty:CreateIPSet, guardduty:CreateMembers, guardduty:CreatePublishingDestination, guardduty:CreateSampleFindings, and more. Its conditions test aws:PrincipalARN.
What the source says
guardduty:DeleteDetector (read 10 Nov 2026).
On what it breaks: guardduty:ArchiveFindings
Related guardrails
- Deploy diagnostic settings for Key Vault to Event HubAzure, Azure Policy (built-in definitions), logging and monitoring
- Application Insights components should block non-Entra ingestionAzure, Azure Policy (built-in definitions), logging and monitoring
- Require predefined policies for VPC flow logsGoogle Cloud, Organization Policy Service (managed and legacy constraints), logging and monitoring
- Deny enabling and disabling AWS ConfigAWS, Service control policies (SCPs), logging and monitoring
- Deny modifications to specific CloudTrail trailsAWS, Service control policies (SCPs), logging and monitoring
- Deny deleting VPC flow logsAWS, Service control policies (SCPs), logging and monitoring
Related pages
Sources
- Deny disabling or modifying Amazon GuardDuty, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.