A cPanel host operator is rarely the “personal information custodian” under PIPEDA or Quebec Law 25 — the customer is. But the operator holds the infrastructure logs that the custodian needs when an incident touches personal information. If those logs do not exist, or rotated last week, the customer cannot meet their notification obligation. The host’s job is to keep the evidence.
What’s happening
PIPEDA requires reasonable safeguards and breach notification when personal information is at risk of “significant harm.” Quebec Law 25 raises that bar — confidentiality incidents require notification to the Commission d’accès à l’information and to affected individuals, with specific record-keeping. A cPanel host serves as a sub-processor: when a customer asks “did anyone outside our team access our database between Tuesday and Friday,” the operator needs to answer.
How to verify
ls -lh /etc/apache2/logs/access_log* /usr/local/cpanel/logs/access_log /var/log/secure*
grep -c "^" /var/log/exim_mainlog
logrotate -d /etc/logrotate.d/cpanel 2>&1 | head
cat /etc/logrotate.d/httpd /etc/logrotate.d/cpanel
journalctl --disk-usage
If logs rotate after 4 days, the customer’s 72-hour notification window may run past the evidence horizon.
The fix
- Set a minimum retention for logs that touch personal information access:
- Apache access logs (per-account): 90 days minimum, 365 days for accounts under contract obligations.
- Exim mainlog: 90 days minimum.
- WHM/cPanel access log: 365 days (operator actions matter for chain of custody).
- SSH/auth.log: 365 days.
- ModSecurity audit log: 30 days minimum, longer if you can.
- Edit
/etc/logrotate.d/cpanel,/etc/logrotate.d/httpd: setrotate 90(or 365) andcompress. Verify withlogrotate -d. - Off-host archive: ship rotated logs to object storage. On-host logs are vulnerable to whoever compromises the host; off-host logs are evidence.
- Document the retention in the customer contract. The customer needs to know what they can rely on you for.
- Incident response runbook: when a customer reports a suspected incident, the operator must be able to produce, within 48 hours: who accessed the cPanel account, when, from where; what mail was sent; what files changed; what database queries ran (if MySQL general log was on — which is rare).
- Records of the request: every customer-initiated evidence pull is itself a log. Document the request, who handled it, what was produced.
- Bilingual incident communications: customer-facing notifications under Law 25 must be available in French if the customer or affected individuals reside in Quebec.
Stack Harbor maintains a 365-day infrastructure log retention policy on managed cPanel hosts as part of cPanel server administration.