Surf Wiki
Save to docs
general/change-management

From Surf Wiki (app.surf) — the open knowledge base

File integrity monitoring

File integrity monitoring (FIM) is an internal control or process that performs the act of validating the integrity of operating system and application software files using a verification method between the current file state and a known, good baseline. This comparison method often involves calculating a known cryptographic checksum of the file's original baseline and comparing with the calculated checksum of the current state of the file. Other file attributes can also be used to monitor integrity.

Generally, the act of performing file integrity monitoring is automated using internal controls such as an application or process. Such monitoring can be performed randomly, at a defined polling interval, or in real-time.

Security objectives

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. These changes can also reduce security posture and in some cases may be leading indicators of a breach in progress. Values monitored for unexpected changes to files or configuration items include:

  • Credentials
  • Privileges and security settings
  • Content
  • Core attributes and size
  • Hash values
  • Configuration values

Compliance objectives

Multiple compliance objectives indicate file integrity monitoring as a requirement. Several examples of compliance objectives with the requirement for file integrity monitoring include:

  • PCI DSS - Payment Card Industry Data Security Standard (Requirement 11.5)
  • SOX - Sarbanes-Oxley Act (Section 404)
  • NERC CIP - NERC CIP Standard (CIP-010-2)
  • FISMA - Federal Information Security Management Act (NIST SP800-53 Rev3)
  • HIPAA - Health Insurance Portability and Accountability Act of 1996 (NIST Publication 800-66)
  • SANS Critical Security Controls (Control 3)

References

References

  1. "Verisys - How it Works". Ionx.
  2. "File Integrity Monitoring". nCircle.
  3. "Payment Card Industry Data Security Standard". PCI Security Council.
  4. "Sarbanes-Oxley Sections 302 & 404 - A White Paper Proposing Practival, Cost Effective Compliance Strategies". Card Decisions, Inc..
  5. "Standard CIP-010-2 - Security Configuration, Change Management and Vulnerability Assessments". North American Electric Reliability Corporation (NERC).
  6. "Applying NIST SP 800-53 to Industrial Control Systems". National Institute of Standards and Technology (NIST).
  7. (2008). "An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule". National Institute of Standards and Technology.
  8. "Critical Control 3: Secure Configurations for Hardware and Software on Mobile Devices, Laptops, Workstations, and Servers". SANS Institute.
  9. "AFICK (Another File Integrity ChecKer)".
  10. "CimTrak Integrity Suite {{!}} Cimcor".
  11. "HarfangLab plans".
  12. "Lockpath Announces Significant Updates to Blacklight Platform".
  13. "Netwrix Change Tracker".
Info: Wikipedia Source

This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.

change-management computer-forensics
Want to explore this topic further?

Ask Mako anything about File integrity monitoring — get instant answers, deeper analysis, and related topics.

Research with Mako

Free with your Surf account

Content sourced from Wikipedia, available under CC BY-SA 4.0.

This content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.

Report