Control types for @turbot/aws-secretsmanager

• AWS > Secrets Manager > Secret > Active
• AWS > Secrets Manager > Secret > Approved
• AWS > Secrets Manager > Secret > CMDB
• AWS > Secrets Manager > Secret > Discovery
• AWS > Secrets Manager > Secret > Encryption at Rest
• AWS > Secrets Manager > Secret > Policy
• AWS > Secrets Manager > Secret > Policy > Trusted Access
• AWS > Secrets Manager > Secret > Tags
• AWS > Secrets Manager > Secret > Usage

AWS > Secrets Manager > Secret > Active

Take an action when an AWS Secrets Manager secret is not active based on the
AWS > Secrets Manager > Secret > 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 > Secrets Manager > Secret > 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 > Secrets Manager > Secret > Approved

Take an action when an AWS Secrets Manager secret is not approved based on AWS > Secrets Manager > Secret > 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 > Secrets Manager > Secret > CMDB

Record and synchronize details for the AWS Secrets Manager secret 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 > Secrets Manager > Secret > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Secrets Manager > Secret > Discovery

Discover all AWS Secrets Manager secret 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 > Secrets Manager > Secret > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Secrets Manager > Secret > Encryption at Rest

Define the Encryption at Rest settings required for AWS > Secrets Manager > Secret.

Encryption at Rest refers specifically to the encryption of data when written
to an underlying storage system. This control determines whether the resource
is encrypted at rest, and sets encryption to your desired level.

The Encryption at Rest
control compares the encryption settings against the encryption policies for the resource
(AWS > Secrets Manager > Secret > Encryption at Rest > *),
raises an alarm, and takes the defined enforcement action.

AWS > Secrets Manager > Secret > Policy

AWS > Secrets Manager > Secret > Policy > Trusted Access

Take an action when AWS Secrets Manager secret policy is not trusted based on the
AWS > Secrets Manager > Secret > Policy > Trusted Access > * policies.

The Trusted Access control evaluates the secret policy against the list of allowed
members in each of the Trusted Access sub-policies (Trusted Access > Accounts,
Trusted Access > Services etc.), this control raises an alarm and takes the
defined enforcement action.

The account that owns the secret will always be trusted, even if its account ID is
not included in the Trusted Accounts policy.

If set to Enforce: Revoke untrusted access, access to non-trusted
members will be removed.

AWS > Secrets Manager > Secret > Tags

Take an action when an AWS Secrets Manager secret tags is not updated based on the AWS > Secrets Manager > Secret > Tags > * policies.

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

See Tags for more information.

AWS > Secrets Manager > Secret > Usage

The Usage control determines whether the number of AWS Secrets Manager secret resources exceeds the configured usage limit for this account.

You can configure the behavior of this control with the AWS > Secrets Manager > Secret > Usage policy, and set the limit with the AWS > Secrets Manager > Secret > Usage > Limit policy.