Policy: Turbot > Workspace > osquery > Secrets > Rotation
Check or Enforce that Turbot > Workspace > osquery > Secrets
are being per the Turbot > Workspace > osquery > Secrets > Expiration Period
policy. For example, secrets must be rotated every year.
This policy is very useful when combined with Turbot's automatic management of event handlers across cloud providers.
If your organization requires continuous rotation of secrets, then use Turbot automation combined with Enforce: Rotate osquery secret
.
A common (and practical) policy position is having the ability to rotate secrets when required - as opposed to continuous rotating them. In that case you could set this policy to Check
combined with an expiration period of Never
.
Resource Types
This policy targets the following resource types:
Primary Policy
This policy is used with the following primary policy:
Controls
Policy Specification
Schema Type |
|
---|---|
Valid Values [YAML] |
|
Default template |
|
Default template input |
|
Examples [YAML] |
|
Category
In Your Workspace
Developers
- tmod:@turbot/turbot#/control/categories/turbot
- tmod:@turbot/osquery#/policy/types/workspaceOsquerySecretsRotation
- turbot graphql policy-type --id "tmod:@turbot/osquery#/policy/types/workspaceOsquerySecretsRotation"
- turbot graphql policy-settings --filter "policyTypeId:tmod:@turbot/osquery#/policy/types/workspaceOsquerySecretsRotation"
Get Policy TypeGet Policy Settings