Control types for @turbot/aws-guardduty

• AWS > GuardDuty > Detector > Active
• AWS > GuardDuty > Detector > Approved
• AWS > GuardDuty > Detector > CMDB
• AWS > GuardDuty > Detector > Configured
• AWS > GuardDuty > Detector > Discovery
• AWS > GuardDuty > Detector > Tags
• AWS > GuardDuty > Detector > Usage
• AWS > GuardDuty > Finding > CMDB
• AWS > GuardDuty > Finding > Discovery
• AWS > GuardDuty > IPSet > Active
• AWS > GuardDuty > IPSet > Approved
• AWS > GuardDuty > IPSet > CMDB
• AWS > GuardDuty > IPSet > Discovery
• AWS > GuardDuty > IPSet > Tags
• AWS > GuardDuty > IPSet > Usage
• AWS > GuardDuty > ThreatIntelSet > Active
• AWS > GuardDuty > ThreatIntelSet > Approved
• AWS > GuardDuty > ThreatIntelSet > CMDB
• AWS > GuardDuty > ThreatIntelSet > Discovery
• AWS > GuardDuty > ThreatIntelSet > Tags
• AWS > GuardDuty > ThreatIntelSet > Usage

AWS > GuardDuty > Detector > Active

Take an action when an AWS GuardDuty detector is not active based on the
AWS > GuardDuty > Detector > Active > * policies.

The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.

The Active control checks the status of all defined Active policies for the
resource (AWS > GuardDuty > Detector > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.

Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

AWS > GuardDuty > Detector > Approved

Take an action when an AWS GuardDuty detector is not approved based on AWS > GuardDuty > Detector > Approved > * policies.

The 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.

For 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.

See Approved for more information.

AWS > GuardDuty > Detector > CMDB

Record and synchronize details for the AWS GuardDuty detector into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > GuardDuty > Detector > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > GuardDuty > Detector > Configured

Maintain AWS > GuardDuty > Detector configuration.

Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored
and inherit from the stack that owns it.

AWS > GuardDuty > Detector > Discovery

Discover all AWS GuardDuty detector resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > GuardDuty > Detector > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > GuardDuty > Detector > Tags

Take an action when an AWS GuardDuty detector tags is not updated based on the AWS > GuardDuty > Detector > Tags > * policies.

If the resource is not updated with the tags defined in AWS > GuardDuty > Detector > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > GuardDuty > Detector > Usage

The Usage control determines whether the number of AWS GuardDuty detector resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > GuardDuty > Detector > Usage policy, and set the limit with the AWS > GuardDuty > Detector > Usage > Limit policy.

AWS > GuardDuty > Finding > CMDB

Record and synchronize details for the AWS GuardDuty finding into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > GuardDuty > Finding > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

This control will automatically re-run every 24 hours because AWS does not currently support real-time events for this resource type.

AWS > GuardDuty > Finding > Discovery

Discover all AWS GuardDuty finding resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > GuardDuty > Finding > Regions policy, the CMDB control will delete the resource from the CMDB.

This control will automatically re-run every 24 hours because AWS does not currently support real-time events for this resource type.

AWS > GuardDuty > IPSet > Active

Take an action when an AWS GuardDuty ipset is not active based on the
AWS > GuardDuty > IPSet > Active > * policies.

The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.

The Active control checks the status of all defined Active policies for the
resource (AWS > GuardDuty > IPSet > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.

Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

AWS > GuardDuty > IPSet > Approved

Take an action when an AWS GuardDuty ipset is not approved based on AWS > GuardDuty > IPSet > Approved > * policies.

The 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.

For 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.

See Approved for more information.

AWS > GuardDuty > IPSet > CMDB

Record and synchronize details for the AWS GuardDuty ipset into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > GuardDuty > IPSet > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > GuardDuty > IPSet > Discovery

Discover all AWS GuardDuty ipset resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > GuardDuty > IPSet > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > GuardDuty > IPSet > Tags

Take an action when an AWS GuardDuty ipset tags is not updated based on the AWS > GuardDuty > IPSet > Tags > * policies.

If the resource is not updated with the tags defined in AWS > GuardDuty > IPSet > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > GuardDuty > IPSet > Usage

The Usage control determines whether the number of AWS GuardDuty ipset resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > GuardDuty > IPSet > Usage policy, and set the limit with the AWS > GuardDuty > IPSet > Usage > Limit policy.

AWS > GuardDuty > ThreatIntelSet > Active

Take an action when an AWS GuardDuty threatintelset is not active based on the
AWS > GuardDuty > ThreatIntelSet > Active > * policies.

The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.

The Active control checks the status of all defined Active policies for the
resource (AWS > GuardDuty > ThreatIntelSet > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.

Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

AWS > GuardDuty > ThreatIntelSet > Approved

Take an action when an AWS GuardDuty threatintelset is not approved based on AWS > GuardDuty > ThreatIntelSet > Approved > * policies.

The 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.

For 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.

See Approved for more information.

AWS > GuardDuty > ThreatIntelSet > CMDB

Record and synchronize details for the AWS GuardDuty threatintelset into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > GuardDuty > ThreatIntelSet > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > GuardDuty > ThreatIntelSet > Discovery

Discover all AWS GuardDuty threatintelset resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > GuardDuty > ThreatIntelSet > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > GuardDuty > ThreatIntelSet > Tags

Take an action when an AWS GuardDuty threatintelset tags is not updated based on the AWS > GuardDuty > ThreatIntelSet > Tags > * policies.

If the resource is not updated with the tags defined in AWS > GuardDuty > ThreatIntelSet > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > GuardDuty > ThreatIntelSet > Usage

The Usage control determines whether the number of AWS GuardDuty threatintelset resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > GuardDuty > ThreatIntelSet > Usage policy, and set the limit with the AWS > GuardDuty > ThreatIntelSet > Usage > Limit policy.