Use File Integrity to compare the included files with an existing trusted baseline. The result identifies differences; it does not decide whether a change was authorised or repair the installation.

Run a new comparison

1. Confirm Pro is active and a baseline exists.
2. Open PD Modules → Guard → File Integrity.
3. Check the displayed baseline and last-scan times.
4. Choose Scan now when you intend to run a new comparison.
5. Wait for the result, then check that the scan time and file count reflect this attempt.

Opening the tab shows the last stored result rather than starting a scan. Reopening it repeatedly does not prove a fresh comparison. A manual integrity scan stores its result; it is not the scheduled alert-delivery test.

Interpret the differences

Added means an included file was absent from the baseline. Changed means its fingerprint differs. Removed means a baseline entry was absent from the current comparison. Changes can reflect legitimate updates, customisation, missing files or tampering; the group name alone does not establish the cause.

Expand Changed, Added and Removed as available. The full totals can exceed the displayed lists: the stored result limits how many names it retains and labels shorter lists as a partial display. An absent filename from the visible subset is not proof that it was unaffected.

Check completeness before reassurance

Read any File cap reached warning. An incomplete walk, changed exclusions or unreadable files can affect a comparison; “No changes” only concerns the included files successfully represented. If a result is unexpected, preserve the evidence and investigate before replacing the baseline. The baseline is a comparison record, not an immutable history or a file backup.

See the PD Guard Blesta guide for related tasks, or explore PD Guard.