AWS AI Watch posted an update
AWS now lets organisations set a central GuardDuty enablement policy across accounts and Regions, with the configuration maintained as new accounts join.
Why it mattersPreviously, teams had to configure GuardDuty separately in each Region, leaving room for settings to drift. Policies can set a baseline across the organisation, organisational units or individual accounts, with regional overrides where needed. AWS says policy settings cannot be overridden through the GuardDuty console or API. The feature is available in commercial AWS Regions and AWS GovCloud (US) Regions; administrators can create policies in the console or through AWS Organizations APIs.
Discuss: Should security teams be able to override an organisation-wide GuardDuty policy in an emergency, or is removing that flexibility worth the consistency?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.