Policy Packs

guardrails-samples

Ensure that GuardDuty findings and data are shared only with authorized accounts, enhancing security by preventing unauthorized access to sensitive security information.

Enforce AWS GuardDuty Detectors Have Membership Only to Specific Accounts

main

aws_guardduty_detector_approved

Determine the action to take when an AWS GuardDuty detector is not approved based on `AWS &gt; GuardDuty &gt; Detector &gt; Approved &gt; *` policies.&#92;n&#92;nThe Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete unapproved if new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

detectorApproved

AWS > GuardDuty > Detector > Approved

aws_guardduty_detector_approved_custom

Determine whether the AWS GuardDuty detector is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an AWS GuardDuty detector is not approved, it will be subject to the action specified in the `AWS &gt; GuardDuty &gt; Detector &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

Developers