Below are some examples of compliance mandates and obligations related to FIM:Įlectronically protected health information will require FIM / electronic mechanisms to corroborate that a particular data has not not been compromised in an unauthorized manner.Ī POS system would require FIM for PCI DSS compliance.įor the SOX/COBIT Framework, FIM is required for reporting on internal control structures (SOX 404), Internal controls (SOX 302), Supporting applications (COBIT enablers), and Evaluation and monitoring (COBIT lifecycle).įIM can help the configuration change management and vulnerability assessments required by CIP-010-2.įIM can assist with ensuring that organizations remain compliant under the NIST SP 800-53 federal guidelines.

Within compliance, file integrity monitoring represents a crucial role in meeting obligations and requirements. It can also serve as an intruder detection tactic to monitor changes to vital configuration files. It also allows for better incident response like the detection of malware outbreaks or malicious changes made by malware to critical assets. By using file integrity monitoring, better control measures can be taken due to being able to track and provide data for alerts of activities on assets that are being monitored, such as potential unauthorized changes. File integrity monitoring is largely used as a security measure for detection and for meeting obligations such as compliance.

File integrity monitoring is implemented as a detection mechanism to monitor changes to important files and folders.

Nxlog flat file