用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-foundations-8-3-10命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 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.10 |
| description | Ensure 'Public network access' for Key Vault is set to 'Disabled' |
| category | cis-azure-foundations |
| version | 5.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","security","key-vault","networking","public-access"] |
| cis_id | 8.3.10 |
| cis_benchmark | CIS Microsoft Azure Foundations Benchmark v5.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Ensure that public network access to Azure Key Vault is disabled, restricting access to only private endpoints and trusted Azure services.
By default, Azure Key Vault is accessible from the public internet. Even with proper authentication and authorization, exposing Key Vault publicly increases the attack surface and the risk of brute-force attacks, credential stuffing, or exploitation of potential authentication vulnerabilities. Disabling public network access ensures that Key Vault can only be accessed through private endpoints within the virtual network or by trusted Azure services, significantly reducing the attack surface and the risk of unauthorized access to sensitive secrets, keys, and certificates.
Disabling public network access requires that all clients accessing Key Vault do so through private endpoints or trusted Azure services. This means applications outside the virtual network, including developer workstations, CI/CD pipelines, and external services, will not be able to access Key Vault unless they are connected via VPN, ExpressRoute, or other private network connectivity. Organizations must ensure private endpoints are properly configured before disabling public access to avoid service disruptions.
From Azure Portal:
Key vaults.Settings, click Networking.Firewalls and virtual networks tab, verify that Public network access is set to Disabled.From Azure CLI:
az keyvault list --query "[].{Name:name, PublicAccess:properties.publicNetworkAccess}" -o table
Ensure PublicAccess is Disabled for all Key Vaults.
For a specific vault:
az keyvault show --name {vaultName} --query "properties.publicNetworkAccess"
From PowerShell:
Get-AzKeyVault | ForEach-Object {
Get-AzKeyVault -VaultName $_.VaultName | Select-Object VaultName, PublicNetworkAccess
}
Ensure PublicNetworkAccess is Disabled for all Key Vaults.
All Key Vaults should have publicNetworkAccess set to Disabled.
From Azure Portal:
Key vaults.Settings, click Networking.Firewalls and virtual networks tab, set Public network access to Disabled.Apply.From Azure CLI:
az keyvault update --name {vaultName} --public-network-access Disabled
From PowerShell:
Update-AzKeyVault -VaultName {vaultName} -PublicNetworkAccess "Disabled"
Important: Before disabling public network access, ensure that:
By default, public network access is enabled for Azure Key Vault.