A file-integrity baseline records fingerprints of the current files as a trusted comparison point. It does not certify that those files are safe or store copies you can restore.

Prepare a trusted starting point

1. Confirm PD Guard Pro is active and the installation is in a state you have independently reviewed.
2. Open PD Modules → Guard → File Integrity.
3. Read No baseline yet if no baseline is present.
4. Choose Set baseline only when you intend to trust the current included files.
5. Read the confirmation, then confirm that choice if it is correct.
6. Check the stored file count and baseline time afterwards.

Opening File Integrity does not automatically create a baseline or scan the tree. The action is deliberate. Do not establish a trusted state during an unexplained incident merely to remove warnings.

Record any coverage warning

The baseline scanner includes selected PHP files and has a 20,000-file limit. Review any file cap reached result when setting it. The baseline screen does not retain a complete independent record of that original cap warning, so preserve it in your own investigation notes.

Excluded directories, symbolic links and content outside the selected file types are not part of this trust decision. A baseline with a plausible count is not proof that every file was included. If the count is unexpectedly zero or saving fails, check the resulting state before retrying.

Make the first later comparison

After establishing the baseline, choose Scan now when you intend to compare the installation with it. Not scanned yet means no saved comparison against this baseline; it is not a clean scan result. Keep an appropriate backup separately because fingerprints cannot restore file contents.

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