Benchmark: Cryptographic Key Establishment and Management (SC-12)
Description
The organization establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with organization-defined requirements for key generation, distribution, storage, access, and destruction.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-azure-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select Cryptographic Key Establishment and Management (SC-12).
Run this benchmark in your terminal:
powerpipe benchmark run azure_compliance.benchmark.nist_sp_800_53_rev_5_sc_12Snapshot and share results via Turbot Pipes:
powerpipe benchmark run azure_compliance.benchmark.nist_sp_800_53_rev_5_sc_12 --shareControls
- Azure Automation accounts should use customer-managed keys to encrypt data at rest
- Azure Batch account should use customer-managed keys to encrypt data
- Bot Service should be encrypted with a customer-managed key
- Cognitive Services accounts should enable data encryption with a customer-managed key
- OS and data disks should be encrypted with a customer-managed key
- Managed disks should be double encrypted with both platform-managed and customer-managed keys
- Container Instance container group should use customer-managed key for encryption
- Container registries should be encrypted with a customer-managed key
- Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest
- Azure data factories should be encrypted with a customer-managed key
- Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password
- Event Hub namespaces should use a customer-managed key for encryption
- Azure HDInsight clusters should use customer-managed keys to encrypt data at rest
- Azure HDInsight clusters should use encryption at host to encrypt data at rest
- Azure API for FHIR should use a customer-managed key to encrypt data at rest
- HPC Cache accounts should use customer-managed key for encryption
- IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK)
- Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys
- Azure Data Explorer encryption at rest should use a customer-managed key
- Logic Apps Integration Service Environment should be encrypted with customer-managed keys
- Azure Machine Learning workspaces should be encrypted with a customer-managed key
- Saved-queries in Azure Monitor should be saved in customer storage account for logs encryption
- Azure Monitor Logs clusters should be encrypted with customer-managed key
- SQL managed instances should use customer-managed keys to encrypt data at rest
- MySQL servers should use customer-managed keys to encrypt data at rest
- PostgreSQL servers should use customer-managed keys to encrypt data at rest
- Azure Recovery Services vaults should use customer-managed keys for encrypting backup data
- Service Bus Premium namespaces should use a customer-managed key for encryption
- SQL servers should use customer-managed keys to encrypt data at rest
- Storage accounts should use customer-managed key for encryption
- Storage account encryption scopes should use customer-managed keys to encrypt data at rest
- Azure Stream Analytics jobs should use customer-managed keys to encrypt data
- Azure Synapse workspaces should use customer-managed keys to encrypt data at rest