ServiceNow CMDB CI relationship sync: faster, more complete →
Mods
GCP

Policy: GCP > Compute Engine > Disk > Active > Attached

Determine whether the Disk is active, based on whether it is attached to any other resource types. 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 > Compute Engine > Disk > 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.

Resource Types

This policy targets the following resource types:

Primary Policy

This policy is used with the following primary policy:

Controls

Policy Packs

This policy setting is used by the following policy packs:

Policy Specification

Schema Type
string
Default
Skip
Valid Values [YAML]
  • Skip
    
  • Active if attached
    
  • Force active if attached
    
  • Force inactive if unattached
    
  • Force inactive if unattached > 1 day
    
  • Force inactive if unattached > 3 days
    
  • Force inactive if unattached > 7 days
    
  • Force inactive if unattached > 14 days
    
  • Force inactive if unattached > 30 days
    
  • Force inactive if unattached > 60 days
    
  • Force inactive if unattached > 90 days
    
  • Force inactive if unattached > 180 days
    
  • Force inactive if unattached > 365 days
    
Examples [YAML]
  • Skip
    

Category

In Your Workspace

Developers