ConfigServer eXploit Scanner (CXS) quarantines suspicious files by moving them to a quarantine directory. If this directory does not exist or has incorrect permissions, CXS cannot quarantine files and will log errors. This guide shows how to create and configure the CXS quarantine directory.
mkdir -p /home/cxsquarantine
chown root:root /home/cxsquarantine
chmod 700 /home/cxsquarantine
01. Create the Quarantine Directory
mkdir -p /home/cxsquarantine
chown root:root /home/cxsquarantine
chmod 700 /home/cxsquarantine
02. Configure CXS to Use It
Edit the CXS configuration file /etc/cxs/cxs.conf and set the quarantine path:
quar_dir = /home/cxsquarantine
If the directive is already present, verify the path matches the directory you created.
03. Verify
# Test CXS is working
cxs --test
# Check quarantine directory is accessible
ls -la /home/cxsquarantine/
# Review recent quarantine activity
ls -lt /home/cxsquarantine/ | head -20
Quarantined files accumulate over time. Review and clean them periodically:
# See total size
du -sh /home/cxsquarantine/
# Remove files older than 90 days
find /home/cxsquarantine/ -type f -mtime +90 -delete
Do not set the quarantine directory to /tmp. On servers with /tmp mounted as a separate partition with limited space, quarantined files can fill it up and cause system-wide issues.
Need Help With CXS Configuration?
Contact our team for assistance with malware scanning and CXS setup.
Open a Support TicketFrequently Asked Questions
What is the CXS quarantine directory for?
ConfigServer eXploit Scanner (CXS) moves suspicious files it detects into a quarantine directory so they are isolated from your site. If that directory is missing or has wrong permissions, CXS cannot quarantine and logs errors.
How do I create the CXS quarantine directory?
As root, create a directory for quarantine (for example /home/quarantine or a path you choose), set restrictive permissions so only root can access it, then point CXS at it with its quarantine option. This requires root, so it applies to VPS and dedicated servers.
What permissions should the quarantine directory have?
Lock it down to root only, typically 700 and owned by root, so quarantined malware cannot be executed or accessed by any account. The point of quarantine is isolation, so restrictive permissions are important.
Do shared hosting customers need to do this?
No. CXS and its quarantine are server-level and managed by us on shared hosting. This guide is for VPS and dedicated administrators configuring CXS themselves.
Quick Recap
- Create:
mkdir -p /home/cxsquarantine - Own:
chown root:root,chmod 700 - Configure: set
quar_dirin/etc/cxs/cxs.conf - Verify:
cxs --test - Maintain: periodically clean old quarantined files
10,424 users found this article useful · Last updated November 2026 · Browse all Server Maintenance articles
