AzPolicyAdvertizer

last sync: 2024-Nov-25 18:54:24 UTC

Set file integrity rules in your organization | Regulatory Compliance - Operational

Azure BuiltIn Policy definition

Source Azure Portal
Display name Set file integrity rules in your organization
Id 9e1a2a94-cf7e-47de-b28e-d445ecc63902
Version 1.0.0
Details on versioning
Versioning Versions supported for Versioning: 1
1.0.0
Built-in Versioning [Preview]
Category Regulatory Compliance
Microsoft Learn
Description CMA_M1000 - Set file integrity rules in your organization
Additional metadata Name/Id: CMA_M1000 / CMA_0545
Category: Operational
Title: Set file integrity rules in your organization
Ownership: Customer
Description: Defender for Cloud can monitor machines using a file integrity monitoring solution powered by Defender for Endpoint (MDE) Integration. To monitor changes to critical files, registry keys, and more on your servers, enable file integrity monitoring.When the file integrity monitoring solution is enabled, monitoring rules are assigned to your machines, and defines the files to be monitored. To edit rules, or see the files changed on machines with existing rules go to the [new UI for FIM over MDE]
Requirements: The customer is responsible for implementing this recommendation.
Mode All
Type BuiltIn
Preview False
Deprecated False
Effect Default
Manual
Allowed
Manual, Disabled
RBAC role(s) none
Rule aliases none
Rule resource types IF (1)
Microsoft.Resources/subscriptions
Compliance
The following 2 compliance controls are associated with this Policy definition 'Set file integrity rules in your organization' (9e1a2a94-cf7e-47de-b28e-d445ecc63902)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
PCI_DSS_v4.0 11.5.1 PCI_DSS_v4.0_11.5.1 PCI DSS v4.0 11.5.1 Requirement 11: Test Security of Systems and Networks Regularly Network intrusions and unexpected file changes are detected and responded to Shared n/a Intrusion-detection and/or intrusionprevention techniques are used to detect and/or prevent intrusions into the network as follows: • All traffic is monitored at the perimeter of the CDE. • All traffic is monitored at critical points in the CDE. • Personnel are alerted to suspected compromises. • All intrusion-detection and prevention engines, baselines, and signatures are kept up to date. link 5
PCI_DSS_v4.0 11.5.2 PCI_DSS_v4.0_11.5.2 PCI DSS v4.0 11.5.2 Requirement 11: Test Security of Systems and Networks Regularly Network intrusions and unexpected file changes are detected and responded to Shared n/a A change-detection mechanism (for example, file integrity monitoring tools) is deployed as follows: • To alert personnel to unauthorized modification (including changes, additions, and deletions) of critical files • To perform critical file comparisons at least once weekly. link 4
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
PCI DSS v4 c676748e-3af9-4e22-bc28-50feed564afb Regulatory Compliance GA BuiltIn
History
Date/Time (UTC ymd) (i) Change type Change detail
2024-08-20 18:21:51 add 9e1a2a94-cf7e-47de-b28e-d445ecc63902
JSON compare n/a
JSON
api-version=2021-06-01
EPAC