Configuring Scan Exclusions for Developers

Scan Exclusions for Developers

Software developers often work with tools, compilers, and build systems that generate large numbers of temporary files. These can trigger frequent scanning and slow down development workflows. True Protection by Jag allows you to configure exclusions to maintain performance without compromising security.

Recommended Developer Exclusions

Consider adding the following types of directories to your exclusion list:

• Build Output: bin, obj, dist, build, out, target directories
• Package Managers: node_modules, vendor, .gradle, .m2, .nuget directories
• Version Control: .git directories (but not the working tree)
• Virtual Environments: venv, .venv, .virtualenv directories
• Container and VM Files: Docker image layers, Vagrant box files, VDI/VMDK disk images
• IDE Indices: .idea, .vscode, .vs cache directories

Adding Exclusions

• Step 1: Navigate to Settings > Exclusions.
• Step 2: Click Add Exclusion.
• Step 3: Choose the exclusion type: File Path, Folder, File Extension, or Process.
• Step 4: Enter the path or pattern. You can use wildcards (for example, **/node_modules/**).
• Step 5: Choose which scan types the exclusion applies to: Real-Time, Scheduled, or All.

Security Considerations

While exclusions improve performance, they create blind spots. Follow these best practices:

• Only exclude directories you fully trust and control.
• Run periodic full scans without exclusions to verify excluded areas remain clean.
• Never exclude your Downloads folder or email attachment directories.
• Regularly review your exclusion list and remove entries for projects that are no longer active.