liveBook · Manning

File integrity monitoring

As explained in Azure Security

File integrity monitoring observes selected files and registry entries for changes that may indicate tampering or compromise.

File integrity monitoring observes selected files and registry entries for changes that may indicate tampering or compromise. Microsoft Defender for Servers applies it to OS files, Windows registries, application software, and Linux system files. section 7.2.1

Use it to monitor:

  • Operating-system files and Linux system files. section 7.2.1
  • Windows registries and application software. section 7.2.1
  • Selected resources whose unexpected changes could indicate an attack. section 7.2.1

How Azure Security covers it

How deep it goes
Defines supported monitoring targets and security significance but stops short of configuration steps, detection logic, and response procedures.
Examples
Uses OS files, Windows registries, application software, and Linux system files as monitoring targets.
What it assumes
Assumes awareness of Azure virtual machines and Microsoft Defender for Servers.
What you can do after
Evaluate which server files and registries should be monitored for attack-indicating changes.
How it connects
Connects file integrity monitoring with Microsoft Defender for Servers, vulnerability assessment, adaptive application control, and adaptive network hardening.

Also explained in

Compare how 2 books explain file integrity monitoring →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.