用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-compute-20-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-compute-20.10 |
| description | Ensure Trusted Launch is enabled on Virtual Machines |
| category | cis-azure-compute |
| version | 2.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","virtual-machines","vm","disks","encryption"] |
| cis_id | 20.10 |
| cis_benchmark | CIS Microsoft Azure Compute Services Benchmark v2.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
When Secure Boot and vTPM are enabled together, they provide a strong foundation for protecting your VM from boot attacks. For example, if an attacker attempts to replace the bootloader with a malicious version, Secure Boot will prevent the VM from booting. If the attacker is able to bypass Secure Boot and install a malicious bootloader, vTPM can be used to detect the intrusion and alert you.
Secure Boot and vTPM work together to protect your VM from a variety of boot attacks, including bootkits, rootkits, and firmware rootkits. Not enabling Trusted Launch in Azure VM can lead to increased vulnerability to rootkits and boot-level malware, reduced ability to detect and prevent unauthorized changes to the boot process, and a potential compromise of system integrity and data security.
Secure Boot and vTPM are not currently supported for Azure Generation 1 VMs.
IMPORTANT: Before enabling Secure Boot and vTPM on a Generation 2 VM which does not already have both enabled, it is highly recommended to create a restore point of the VM prior to remediation.
Run the following command to list VM names and security profile settings:
az vm list --query [*].[name,securityProfile]
For each VM, ensure that securityType is set to TrustedLaunch, uefiSettings.secureBootEnabled is set to true, and uefiSettings.vTpmEnabled is set to true.
Run the following command to list VMs:
Get-AzVm
Run the following command to get the VM in a resource group with a given name:
$vm = Get-AzVm -ResourceGroupName <resource-group> -Name <vm>
Run the following command to get the security profile settings for the VM:
$vm.SecurityProfile
Ensure that SecurityType is set to TrustedLaunch.
Run the following command to get the UEFI settings for the VM:
$vm.SecurityProfile.UefiSettings
Ensure that SecureBootEnabled and VTpmEnabled are set to True.
Repeat for each VM.
All VMs should have securityType set to TrustedLaunch with both secureBootEnabled and vTpmEnabled set to true.
Note: Trusted launch on existing virtual machines (VMs) is currently not supported for Azure Generation 1 VMs.
Ensure that it is safe to change the state of the VM.
Run the following command to deallocate the VM:
az vm deallocate --resource-group <resource-group> --name <vm>
Run the following command to update the VM, setting security type to TrustedLaunch and enabling secure boot and vTPM:
az vm update --resource-group <resource-group> --name <vm> --enable-secure-boot true --enable-vtpm true --security-type TrustedLaunch
Run the following command to restart the VM:
az vm start --resource-group <resource-group> --name <vm>
Repeat for each VM requiring remediation.
Ensure it is safe to change the state of the VM.
Run the following command to stop the VM:
Stop-AzVm -ResourceGroupName <resource-group> -Name <vm> -Force
Run the following command to get the VM in a resource group with a given name:
$vm = Get-AzVM -ResourceGroupName <resource-group> -Name <vm>
Run the following command to update the VM, setting security type to TrustedLaunch and enabling secure boot and vTPM:
Update-AzVm -ResourceGroupName <resource-group> -VM $vm -EnableSecureBoot 1 -EnableVtpm 1 -SecurityType TrustedLaunch
Run the following command to start the VM:
Start-AzVm -ResourceGroupName <resource-group> -Name <vm>
Repeat for each VM requiring remediation.
On Azure Generation 2 VMs, vTPM is enabled by default. Secure Boot is not enabled by default.
Level 1 | Automated