Data protection
DP-1: Discover, classify, and label sensitive data
Feature: Sensitive Data Discovery and Classification
Description: Tools (such as Azure Purview or Azure Information Protection) can be used for data discovery and classification in the service.
Configuration Guidance: This feature isn't supported to secure this service.
DP-2: Monitor anomalies and threats targeting sensitive data
Feature: Data Leakage/Loss Prevention
Description: Service supports DLP solution to monitor sensitive data movement (in customer's content).
Configuration Guidance: This feature isn't supported to secure this service.
DP-3: Encrypt sensitive data in transit
Feature: Data in Transit Encryption
Description: Service supports data in-transit encryption for data plane.
Configuration Guidance: No additional configurations are required as this is enabled on a default deployment.
Other guidance for DP-3: Management plane calls are made through Azure Resource Manager over TLS. A valid JSON web token (JWT) is required. Data plane calls can be secured with TLS and one of supported authentication mechanisms (for example, client certificate or JWT).
DP-6: Use a secure key management process
Feature: Key Management in Azure Key Vault
Description: The service supports Azure Key Vault integration for any customer keys, secrets, or certificates.
Configuration Guidance: Set up integration of API Management with Azure Key Vault. Ensure that keys used by API Management are stored an Azure Key Vault so they can be securely accessed and updated.
DP-7: Use a secure certificate management process
Feature: Certificate Management in Azure Key Vault
Description: The service supports Azure Key Vault integration for any customer certificates.
Configuration Guidance: Set up integration of API Management with Azure Key Vault. Ensure that secrets for API Management (Named values) are stored an Azure Key Vault so they can be securely accessed and updated.
Use Azure Key Vault to create and control the certificate lifecycle, including creation, importing, rotation, revocation, storage, and purging of the certificate. Ensure the certificate generation follows defined standards without using any insecure properties, such as: insufficient key size, overly long validity period, insecure cryptography. Setup automatic rotation of the certificate in Azure Key Vault and the Azure service (if supported) based on a defined schedule or when there's a certificate expiration. If automatic rotation isn't supported in the application, ensure they're still rotated using manual methods in Azure Key Vault and the application.
Comments
Post a Comment