Cis Azure Foundations 8.3.3
DevOps & Securitycis-azure-foundations-8.3.3Cis Azure Foundations 8.3.3 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Foundations_Benchmark_v5.0.0/cis-azure-foundations-8.3.3/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-foundations-8-3-3, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
8.3.3 Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults (Automated)
Description
Ensure that all secrets stored in Azure Key Vaults using RBAC (Role-Based Access Control) authorization have an expiration date configured.
Rationale
Secrets (such as passwords, connection strings, API keys, and certificates) without expiration dates remain valid indefinitely. This increases the risk that a compromised secret can be used by an attacker for an extended period without detection. Setting expiration dates on secrets enforces periodic rotation, reduces the window of exposure, and ensures compliance with security policies that mandate credential lifecycle management.
Impact
When secrets expire, any application or service using those secrets will fail until the secret is renewed or replaced. Organizations must implement secret rotation processes and monitoring to ensure continuity. Azure Key Vault supports integration with Azure Event Grid to notify when secrets are near expiration.
Audit Procedure
From Azure Portal:
- Go to
Key vaults. - For each Key Vault with RBAC authorization enabled, click the vault name.
- Under
Objects, clickSecrets. - For each secret, verify that the
Expiration datecolumn shows a date (not blank or 'Not set').
From Azure CLI:
az keyvault list --query "[?properties.enableRbacAuthorization==\`true\`].name" -o tsv
For each RBAC-enabled Key Vault:
az keyvault secret list --vault-name {vaultName} --query "[].{Name:name, Expires:attributes.expires}" -o table
Ensure Expires is set for all secrets.
From PowerShell:
$vaults = Get-AzKeyVault | Where-Object { $_.EnableRbacAuthorization -eq $true }
foreach ($vault in $vaults) {
Get-AzKeyVaultSecret -VaultName $vault.VaultName | Select-Object Name, Expires
}
Ensure Expires is populated for all secrets.
Expected Result
All secrets in RBAC-enabled Key Vaults should have an expiration date set.
Remediation
From Azure Portal:
- Go to
Key vaults. - Click the name of a Key Vault.
- Under
Objects, clickSecrets. - Click the secret that needs an expiration date.
- Click the current version of the secret.
- Set the
Expiration date. - Click
Save.
From Azure CLI:
az keyvault secret set-attributes --vault-name {vaultName} --name {secretName} --expires "2025-12-31T23:59:59Z"
From PowerShell:
$expires = (Get-Date).AddYears(1).ToUniversalTime()
Update-AzKeyVaultSecret -VaultName {vaultName} -Name {secretName} -Expires $expires
Default Value
By default, secrets are created without an expiration date.
References
- https://learn.microsoft.com/en-us/azure/key-vault/secrets/about-secrets
- https://learn.microsoft.com/en-us/azure/key-vault/general/best-practices
- https://learn.microsoft.com/en-us/azure/key-vault/general/event-grid-overview
- https://learn.microsoft.com/en-us/cli/azure/keyvault/secret
- https://learn.microsoft.com/en-us/powershell/module/az.keyvault/update-azkeyvaultsecret
Profile
- Level 1