Control types for @turbot/gcp-iam
- GCP > IAM > API Enabled
- GCP > IAM > CMDB
- GCP > IAM > Discovery
- GCP > IAM > Member > Configured
- GCP > IAM > Project Role > CMDB
- GCP > IAM > Project Role > Configured
- GCP > IAM > Project Role > Discovery
- GCP > IAM > Project User > Active
- GCP > IAM > Project User > CMDB
- GCP > IAM > Project User > Discovery
- GCP > IAM > Service Account > Active
- GCP > IAM > Service Account > Approved
- GCP > IAM > Service Account > CMDB
- GCP > IAM > Service Account > Discovery
- GCP > IAM > Service Account > Policy
- GCP > IAM > Service Account > Policy > Trusted Access
- GCP > IAM > Service Account > Usage
- GCP > IAM > Service Account Key > Active
- GCP > IAM > Service Account Key > Approved
- GCP > IAM > Service Account Key > CMDB
- GCP > IAM > Service Account Key > Discovery
- GCP > IAM > Service Account Key > Usage
- GCP > Project > Policy > CMDB
- GCP > Project > Policy > Discovery
- GCP > Project > Policy > Trusted Access
- GCP > Turbot > IAM
GCP > IAM > API Enabled
Check whether GCP IAM API is enabled.
API Enabled refers specifically to the API state of a service in a cloud project.
This control determines whether the API state is set as per desired level.
The GCP > IAM > API Enabled
control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/gcp-iam#/control/types/iamApiEnabled
GCP > IAM > CMDB
Record and synchronize details for the GCP IAM into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
GCP > IAM > Discovery
Discover GCP IAM resources and add them to the CMDB.
The Discovery
control is tasked with identifying instances for a particular resource.
The Discovery control will periodically search for new target resources and
save them to the Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.
tmod:@turbot/gcp-iam#/control/types/iamDiscovery
GCP > IAM > Member > Configured
Maintain iam member configuration
tmod:@turbot/gcp-iam#/control/types/memberConfigured
GCP > IAM > Project Role > CMDB
Record and synchronize details for the GCP IAM project role into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/gcp-iam#/control/types/projectRoleCmdb
GCP > IAM > Project Role > Configured
Maintain iam projectRole configuration
tmod:@turbot/gcp-iam#/control/types/projectRoleConfigured
GCP > IAM > Project Role > Discovery
Discover GCP IAM project role resources and add them to the CMDB.
The Discovery
control is tasked with identifying instances for a particular resource.
The Discovery control will periodically search for new target resources and
save them to the Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.
tmod:@turbot/gcp-iam#/control/types/projectRoleDiscovery
GCP > IAM > Project User > Active
Take an action when an GCP IAM project user is not active based on theGCP > IAM > Project User > 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 (GCP > IAM > Project User > 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.
tmod:@turbot/gcp-iam#/control/types/projectUserActive
GCP > IAM > Project User > CMDB
Record and synchronize details for the GCP IAM project user into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/gcp-iam#/control/types/projectUserCmdb
GCP > IAM > Project User > Discovery
Discover GCP IAM project user resources and add them to the CMDB.
The Discovery
control is tasked with identifying instances for a particular resource.
The Discovery control will periodically search for new target resources and
save them to the Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.
tmod:@turbot/gcp-iam#/control/types/projectUserDiscovery
GCP > IAM > Service Account > Active
Take an action when an GCP IAM service account is not active based on theGCP > IAM > Service Account > 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 (GCP > IAM > Service Account > 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.
tmod:@turbot/gcp-iam#/control/types/serviceAccountActive
GCP > IAM > Service Account > Approved
Take an action when a GCP IAM service account is not approved based on GCP > IAM > Service Account > 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.
tmod:@turbot/gcp-iam#/control/types/serviceAccountApproved
GCP > IAM > Service Account > CMDB
Record and synchronize details for the GCP IAM service account into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/gcp-iam#/control/types/serviceAccountCmdb
GCP > IAM > Service Account > Discovery
Discover GCP IAM service account resources and add them to the CMDB.
The Discovery
control is tasked with identifying instances for a particular resource.
The Discovery control will periodically search for new target resources and
save them to the Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.
tmod:@turbot/gcp-iam#/control/types/serviceAccountDiscovery
GCP > IAM > Service Account > Policy
tmod:@turbot/gcp-iam#/control/types/serviceAccountPolicy
GCP > IAM > Service Account > Policy > Trusted Access
Take an action when GCP IAM Service Account policy is not trusted based on theGCP > IAM > Service Account > Trusted Access > *
policies.
The Trusted Access control evaluates the IAM policy against the list of allowed
members in each of the Trusted Access sub-policies (Trusted Access > Domains,
Trusted Access > Groups, etc)., this control raises an alarm and takes the
defined enforcement action.
If set to "Enforce: Trusted Access > *", access to non-trusted
members will be removed.
tmod:@turbot/gcp-iam#/control/types/serviceAccountPolicyTrustedAccess
GCP > IAM > Service Account > Usage
The Usage control determines whether the number of GCP IAM service account resources exceeds the configured usage limit for this project.
You can configure the behavior of this control with the GCP > IAM > Service Account > Usage
policy, and set the limit with the GCP > IAM > Service Account > Usage > Limit
policy.
tmod:@turbot/gcp-iam#/control/types/serviceAccountUsage
GCP > IAM > Service Account Key > Active
Take an action when an GCP IAM service account key is not active based on theGCP > IAM > Service Account Key > 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 (GCP > IAM > Service Account Key > 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.
tmod:@turbot/gcp-iam#/control/types/serviceAccountKeyActive
GCP > IAM > Service Account Key > Approved
Take an action when a GCP IAM service account key is not approved based on GCP > IAM > Service Account Key > 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.
tmod:@turbot/gcp-iam#/control/types/serviceAccountKeyApproved
GCP > IAM > Service Account Key > CMDB
Record and synchronize details for the GCP IAM service account key into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/gcp-iam#/control/types/serviceAccountKeyCmdb
GCP > IAM > Service Account Key > Discovery
Discover GCP IAM service account key resources and add them to the CMDB.
The Discovery
control is tasked with identifying instances for a particular resource.
The Discovery control will periodically search for new target resources and
save them to the Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.
tmod:@turbot/gcp-iam#/control/types/serviceAccountKeyDiscovery
GCP > IAM > Service Account Key > Usage
The Usage control determines whether the number of GCP IAM service account key resources exceeds the configured usage limit for this serviceAccount.
You can configure the behavior of this control with the GCP > IAM > Service Account Key > Usage
policy, and set the limit with the GCP > IAM > Service Account Key > Usage > Limit
policy.
tmod:@turbot/gcp-iam#/control/types/serviceAccountKeyUsage
GCP > Project > Policy > CMDB
Record and synchronize details for the GCP IAM policy into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/gcp-iam#/control/types/projectIamPolicyCmdb
GCP > Project > Policy > Discovery
Discover GCP IAM policy resources and add them to the CMDB.
The Discovery
control is tasked with identifying instances for a particular resource.
The Discovery control will periodically search for new target resources and
save them to the Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.
tmod:@turbot/gcp-iam#/control/types/projectIamPolicyDiscovery
GCP > Project > Policy > Trusted Access
Take an action when GCP Project IAM policy is not trusted based on theGCP > Project > Policy > Trusted Access > *
policies.
The Trusted Access control evaluates the IAM policy against the list of allowed
members in each of the Trusted Access sub-policies (Trusted Access > Domains,
Trusted Access > Groups, etc)., this control raises an alarm and takes the
defined enforcement action.
If set to "Enforce: Trusted Access > *", access to non-trusted
members will be removed.
tmod:@turbot/gcp-iam#/control/types/projectIamPolicyTrustedAccess
GCP > Turbot > IAM
Maintain configuration of iam resources
tmod:@turbot/gcp-iam#/control/types/iamTurbot