用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-database-3-7命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-azure-database-3.7 |
| description | Ensure that Cosmos DB Logging is Enabled |
| category | cis-azure-database |
| version | 2.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","cosmos-db","nosql"] |
| cis_id | 3.7 |
| cis_benchmark | CIS Microsoft Azure Database Services Benchmark v2.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Cosmos DB logs should be captured to track events relevant to auditing and diagnostics.
Logging of changes, events, and information related to Cosmos DB provides a diagnostic tool and a forensic record of activity. An effective set of logs help provide integrity and availability to the service and contribute to the effectiveness of detective systems such as a SIEM.
There may be additional storage costs for logging a large amount of events. Potentially only keep logs for a certain timeframe before they are deleted.
NOTE: This procedure assumes a Log Analytics Workspace or other logging destination already exists. Please see attached resources on this setup.
Azure CosmosDB, select the database you wish to audit.> Monitoring.allLogs under Category groups is checked.Get-AzCosmosDBAccount -ResourceGroupName <resource group name>
Get-AzDiagnosticSetting -ResourceId <CosmosDB Account Id>
Diagnostic settings should be configured with allLogs enabled under Category groups, sending logs to an appropriate logging destination (Log Analytics Workspace, Storage Account, or Event Hub).
NOTE: This procedure assumes a Log Analytics Workspace or other logging destination already exists. Please see attached resources on this setup.
Azure CosmosDB, select the database you wish to audit.> Monitoring.+ Add Diagnostic SettingDiagnostic Setting Name.allLogs under Category groupsSend to Log Analytics workspace or other logging solution under Destination details.For each CosmosDB account out of compliance, enable the logging by running the following command:
$categories = @(
@{
Category="ControlPlaneRequests";
Enabled=$true;
RetentionPolicy=@{ Enabled=$false; Days=0 }
},
@{
Category="DataPlaneRequests";
Enabled=$true;
RetentionPolicy=@{ Enabled=$false; Days=0 }
},
@{
Category="MongoRequests";
Enabled=$true;
RetentionPolicy=@{ Enabled=$false; Days=0 }
},
@{
Category="SqlRequests";
Enabled=$true;
RetentionPolicy=@{ Enabled=$false; Days=0 }
},
@{
Category="GremlinQueries";
Enabled=$true;
RetentionPolicy=@{ Enabled=$false; Days=0 }
},
@{
Category="TableRequests";
Enabled=$true;
RetentionPolicy=@{ Enabled=$false; Days=0 }
}
)
Set-AzDiagnosticSetting -Name <name of new CosmosDB diagnostic setting> -ResourceId <CosmosDB Account Id> -WorkspaceId <log analytics workspace id> -Categories $categories -Enabled $true
By default, event logging for Azure Cosmos DB is not enabled.