The cron.deny file must be group-owned by root, bin, or sys.

From SOLARIS 10 SPARC SECURITY TECHNICAL IMPLEMENTATION GUIDE

Associated with IA controls: ECLP-1

Associated with: CCI-000225

SV-26563r1_rule The cron.deny file must be group-owned by root, bin, or sys.

Vulnerability discussion

Cron daemon control files restrict the scheduling of automated tasks and must be protected. Unauthorized modification of the cron.deny file could result in Denial of Service to authorized cron users or could provide unauthorized users with the ability to run cron jobs.

Check content

Check the group ownership of the file. Procedure: # ls -lL /etc/cron.d/cron.deny If the file is not group-owned by root, bin, or sys, this is a finding.

Fix text

Change the group ownership of the file to root, sys, or bin. Procedure: # chgrp root /etc/cron.d/cron.deny

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.