#File monitor software software#
^ "Critical Control 3: Secure Configurations for Hardware and Software on Mobile Devices, Laptops, Workstations, and Servers".: Cite journal requires |journal= ( help) National Institute of Standards and Technology. "An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule" (PDF). National Institute of Standards and Technology (NIST). ^ "Applying NIST SP 800-53 to Industrial Control Systems" (PDF).North American Electric Reliability Corporation (NERC). ^ "Standard CIP-010-2 - Security Configuration, Change Management and Vulnerability Assessments".^ "Sarbanes-Oxley Sections 302 & 404 - A White Paper Proposing Practival, Cost Effective Compliance Strategies" (PDF).^ "Payment Card Industry Data Security Standard" (PDF).System File Checker (provided with Windows).Kaspersky Lab Hybrid Cloud Security, Embedded Security, Security for Linux, Security for Windows Server.Advanced Intrusion Detection Environment.SANS Critical Security Controls (Control 3) Īpplications, some examples (where FIM is used) include:.HIPAA - Health Insurance Portability and Accountability Act of 1996 (NIST Publication 800-66).FISMA - Federal Information Security Management Act (NIST SP800-53 Rev3).NERC CIP - NERC CIP Standard (CIP-010-2).SOX - Sarbanes-Oxley Act (Section 404).PCI DSS - Payment Card Industry Data Security Standard (Requirement 11.5).
Several examples of compliance objectives with the requirement for file integrity monitoring include: Multiple compliance objectives indicate file integrity monitoring as a requirement. Values monitored for unexpected changes to files or configuration items include: These changes can also reduce security posture and in some cases may be leading indicators of a breach in progress. Changes to configurations, files and file attributes across the IT infrastructure are common, but hidden within a large volume of daily changes can be the few that impact file or configuration integrity.
0 kommentar(er)
