用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-foundations-8-3-2命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-azure-foundations-8.3.2 |
| description | Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults |
| category | cis-azure-foundations |
| version | 5.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","security","key-vault","keys","expiration"] |
| cis_id | 8.3.2 |
| cis_benchmark | CIS Microsoft Azure Foundations Benchmark v5.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Ensure that all cryptographic keys stored in Azure Key Vaults using Vault Access Policy authorization (non-RBAC) have an expiration date configured.
Cryptographic keys without expiration dates remain valid indefinitely, creating a security risk as the likelihood of key compromise increases over time. Non-RBAC Key Vaults use Vault Access Policies for authorization, but the key management best practices remain the same. Setting an expiration date ensures keys are periodically reviewed and rotated, limiting the impact of potential key compromise. This aligns with cryptographic best practices and compliance requirements.
When keys expire, applications and services using those keys will fail until the keys are renewed or replaced. Organizations need to implement key rotation procedures and monitoring to ensure keys are renewed before expiration. Automation through Azure Key Vault key rotation policies can help manage this lifecycle.
From Azure Portal:
Key vaults.Objects, click Keys.Expiration date column shows a date (not blank or 'Not set').From Azure CLI:
az keyvault list --query "[?properties.enableRbacAuthorization!=\`true\`].name" -o tsv
For each non-RBAC Key Vault:
az keyvault key list --vault-name {vaultName} --query "[].{Name:name, Expires:attributes.expires}" -o table
Ensure Expires is set for all keys.
From PowerShell:
$vaults = Get-AzKeyVault | Where-Object { $_.EnableRbacAuthorization -ne $true }
foreach ($vault in $vaults) {
Get-AzKeyVaultKey -VaultName $vault.VaultName | Select-Object Name, Expires
}
Ensure Expires is populated for all keys.
All keys in non-RBAC Key Vaults should have an expiration date set.
From Azure Portal:
Key vaults.Objects, click Keys.Expiration date.Save.From Azure CLI:
az keyvault key set-attributes --vault-name {vaultName} --name {keyName} --expires "2025-12-31T23:59:59Z"
From PowerShell:
$expires = (Get-Date).AddYears(1).ToUniversalTime()
Update-AzKeyVaultKey -VaultName {vaultName} -Name {keyName} -Expires $expires
By default, keys are created without an expiration date.