GuardMode 2024.2
Catalogic SoftwareKnowledge BaseMySupport
  • Welcome to GuardMode!
  • Intro
  • Installation
    • System requirements
    • Installing GuardMode Agent on Windows
      • Updating GuardMode Agent on Windows
    • Installing GuardMode Agent on Linux
      • Using GuardMode Agent as a Container
    • Uninstalling GuardMode Agent on Windows
    • Uninstalling GuardMode Agent on Linux
    • Configuring GuardMode Agent for SAMBA setup
    • Uninstalling GuardMode Agent on SAMBA setup
  • Agent Configuration
    • General Settings
    • Excluded Paths Configuration
    • Adding malware detection rules
      • Honeypot and Decoy Files
      • Write Operations Threshold
      • Detecting File Renaming with Abnormal File Extensions
      • Special Files Monitoring
    • Security Incident Detection
    • SMB Monitoring (Linux Only)
    • Event Reports
      • Configuring Event Reports
      • Excluding Paths From Event Reports
      • Tagging Agent
    • NFS Share Monitoring
    • Altering Audit Rules
    • Configuring DPX for Automatic Blocklist Updates
    • Using TLS
    • Configuring YARA-X
  • Using GuardMode Agent Command Line
  • REST API Documentation
  • On-demand Scanning
  • Logging
  • FAQ
  • Found an issue?
Powered by GitBook
On this page
  1. Agent Configuration

Excluded Paths Configuration

PreviousGeneral SettingsNextAdding malware detection rules

Last updated 11 months ago

In Excluded Paths, you can define file paths to be excluded from ransomware detection scanning. The required format for these paths depends on your operating system:

  • On Windows:

[disk:]\path\to\directory\

Tip. You cannot exclude entire disks e.g., C:. The specified path must be at least one level lower in the filesystem hierarchy.

  • On Linux:

/directory/to/exclude/

Attention! Always add a slash at the end of the path.

Input the file path you wish to exclude in the first field.

Next to it, there is the User field. If left blank, the exclusion applies to all users on the node. If you specify a user, such as root, the exclusion will apply only to that user, without affecting others on the node: