last sync: 2024-Jun-14 18:20:16 UTC

Resource logs in Azure Databricks Workspaces should be enabled

Azure BuiltIn Policy definition

Source Azure Portal
Display name Resource logs in Azure Databricks Workspaces should be enabled
Id 138ff14d-b687-4faa-a81c-898c91a87fa2
Version 1.0.1
Details on versioning
Category Azure Databricks
Microsoft Learn
Description Resource logs enable recreating activity trails to use for investigation purposes when a security incident occurs or when your network is compromised.
Mode Indexed
Type BuiltIn
Preview False
Deprecated False
Effect Default
AuditIfNotExists, Disabled
RBAC role(s) none
Rule aliases THEN-ExistenceCondition (5)
Alias Namespace ResourceType DefaultPath Modifiable
Microsoft.Insights/diagnosticSettings/logs.enabled microsoft.insights diagnosticSettings properties.logs[*].enabled false
Microsoft.Insights/diagnosticSettings/logs[*] microsoft.insights diagnosticSettings properties.logs[*] false
Microsoft.Insights/diagnosticSettings/logs[*].retentionPolicy.days microsoft.insights diagnosticSettings properties.logs[*].retentionPolicy.days false
Microsoft.Insights/diagnosticSettings/logs[*].retentionPolicy.enabled microsoft.insights diagnosticSettings properties.logs[*].retentionPolicy.enabled false
Microsoft.Insights/diagnosticSettings/storageAccountId microsoft.insights diagnosticSettings properties.storageAccountId false
Rule resource types IF (1)
The following 2 compliance controls are associated with this Policy definition 'Resource logs in Azure Databricks Workspaces should be enabled' (138ff14d-b687-4faa-a81c-898c91a87fa2)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
Azure_Security_Benchmark_v3.0 LT-3 Azure_Security_Benchmark_v3.0_LT-3 Microsoft cloud security benchmark LT-3 Logging and Threat Detection Enable logging for security investigation Shared **Security Principle:** Enable logging for your cloud resources to meet the requirements for security incident investigations and security response and compliance purposes. **Azure Guidance:** Enable logging capability for resources at the different tiers, such as logs for Azure resources, operating systems and applications inside in your VMs and other log types. Be mindful about different type of logs for security, audit, and other operation logs at the management/control plane and data plane tiers. There are three types of the logs available at the Azure platform: - Azure resource log: Logging of operations that are performed within an Azure resource (the data plane). For example, getting a secret from a key vault or making a request to a database. The content of resource logs varies by the Azure service and resource type. - Azure activity log: Logging of operations on each Azure resource at the subscription layer, from the outside (the management plane). You can use the Activity Log to determine the what, who, and when for any write operations (PUT, POST, DELETE) taken on the resources in your subscription. There is a single Activity log for each Azure subscription. - Microsoft Entra logs: Logs of the history of sign-in activity and audit trail of changes made in the Microsoft Entra ID for a particular tenant. You can also use Microsoft Defender for Cloud and Azure Policy to enable resource logs and log data collecting on Azure resources. **Implementation and additional context:** Understand logging and different log types in Azure: Understand Microsoft Defender for Cloud data collection: Enable and configure antimalware monitoring: Operating systems and application logs inside in your compute resources: n/a link 15
U.15.1 - Events logged U.15.1 - Events logged 404 not found n/a n/a 43
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
Microsoft cloud security benchmark 1f3afdf9-d0c9-4c3d-847f-89da613e70a8 Security Center GA BuiltIn
NL BIO Cloud Theme 6ce73208-883e-490f-a2ac-44aac3b3687f Regulatory Compliance GA BuiltIn
Date/Time (UTC ymd) (i) Change type Change detail
2023-05-22 17:43:18 change Patch (1.0.0 > 1.0.1)
2022-12-21 17:43:51 add 138ff14d-b687-4faa-a81c-898c91a87fa2
JSON compare
compare mode: version left: version right: