用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-compute-2-2-10命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
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 职业分类
| name | cis-azure-compute-2.2.10 |
| description | Ensure 'Remote debugging' is set to 'Off' |
| category | cis-azure-compute |
| version | 2.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","app-service","deployment-slots","remote-debugging","attack-surface","security-hardening"] |
| cis_id | 2.2.10 |
| cis_benchmark | CIS Microsoft Azure Compute Services Benchmark v2.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Remote debugging allows an App Service deployment slot to be debugged in real-time directly in the Azure environment. When remote debugging is enabled, it opens a communication channel that could potentially be exploited by unauthorized users if not properly secured.
Disabling remote debugging on an App Service deployment slot is primarily about enhancing security.
Remote debugging opens a communication channel that can be exploited by attackers. By disabling it, you reduce the number of potential entry points for unauthorized access.
If remote debugging is enabled without proper access controls, it can allow unauthorized users to connect to your deployment slot, potentially leading to data breaches or malicious code execution.
During a remote debugging session, sensitive information might be exposed. Disabling remote debugging helps ensure that such data remains secure. This minimizes the use of remote access tools to reduce risk.
You will not be able to connect to your deployment slot from a remote location to diagnose and fix issues in real-time. You will not be able to step through code, set breakpoints, or inspect variables and the call stack while the deployment slot is running on the server. Remote debugging is particularly useful for diagnosing issues that only occur in the production environment. Without it, you will need to rely on logs and other diagnostic tools.
App Services.Deployment, click Deployment slots.Settings, click Configuration.General settings pane, under Debugging, ensure that Remote debugging is set to Off.Run the following command to list apps:
az webapp list
For each app, run the following command to list deployment slots:
az webapp deployment slot list --resource-group <resource-group-name> --name <app-name>
For each deployment slot, run the following command to get the remote debugging setting:
az resource show --name web --resource-group <resource-group-name> --namespace Microsoft.Web --resource-type config --parent sites/<app-name>/slots/<deployment-slot-name> --query properties.remoteDebuggingEnabled
Ensure that false is returned.
The remoteDebuggingEnabled property should return false.
App Services.Deployment, click Deployment slots.Settings, click Configuration.General settings pane, under Debugging, set Remote debugging to Off.Save.Continue.For each deployment slot requiring remediation, run the following command to disable remote debugging:
az resource update --name web --resource-group <resource-group-name> --namespace Microsoft.Web --resource-type config --parent sites/<app-name>/slots/<deployment-slot-name> --set properties.remoteDebuggingEnabled=false
By default, remote debugging is set to off.
Level 1 | Automated