用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-database-6-1命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 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-database-6.1 |
| description | Ensure Azure Database for PostgreSQL uses Customer Managed Keys for Encryption at Rest |
| category | cis-azure-database |
| version | 2.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","postgresql","database"] |
| cis_id | 6.1 |
| cis_benchmark | CIS Microsoft Azure Database Services Benchmark v2.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Enable sensitive data encryption at rest using Customer Managed Keys (CMK) rather than Microsoft Managed keys (MMK).
By default, data in Azure Database for PostgreSQL is encrypted using Microsoft Service Managed Keys ('SMK' or 'MMK') which constitutes an implied trust. If an organization wishes to control and manage encryption keys, however, customer-managed keys (CMK) can be supplied. The provided key is used to protect and control access to the key that encrypts the data. You can also choose to automatically update the key version used for Azure Database for MySQL encryption whenever a new version is available in the associated Key Vault.
NOTE: This is primarily recommended where control of encryption keys is specified by compliance or security framework requirements. In many circumstances, Microsoft Managed Key encryption is an acceptable method of accomplishing encryption at rest.
If the key expires by setting the 'activation date' and 'expiration date', the user must rotate the key manually.
Using Customer Managed Keys may also incur additional man-hour requirements to create, store, manage, and protect the keys as needed.
Azure Database for PostgreSQL select the server you wish to audit.> Security.Data Encryption.Customer-managed key is selected.Policy ID: 12c74c95-0efd-48da-b8d9-2a7d68470c92
Name: 'PostgreSQL flexible servers should use customer-managed keys to encrypt data at rest'
Customer-managed key should be selected for data encryption.
Azure Database for PostgreSQL select the server you wish to audit.> Security.Data Encryption.Customer-managed key.User assigned managed identity by either creating or selecting one.Enter a key identifier, enter the URL for the key in Azure Key vault. For , navigate through the menu and choose the location of your key store by subscription, and whether it is a key vault or managed HSM.Select a keySave. Verify on the next window that your changes have taken effect.Unless selected at resource creation, by default Azure Database for PostgreSQL uses Microsoft Managed Keys.