Detections
Analytics
SOL-11.1-040420 - Unauthorized use of the at or cron capabilities must not be permitted.
Information
On many systems, only the system administrator needs the ability to schedule jobs.Even though a given user is not listed in the "cron.allow" file, cron jobs can still be run as that user. The "cron.allow" file only controls administrative access to the "crontab" command for scheduling and modifying cron jobs. Much more effective access controls for the cron system can be obtained by using Role-Based Access Controls (RBAC).
Solution
The root role is required.Modify the cron configuration files.
# mv /etc/cron.d/cron.deny /etc/cron.d/cron.deny.temp
# mv /etc/cron.d/at.deny /etc/cron.d/at.deny.temp
Skip the remaining steps only if using the "solaris.jobs.user" RBAC role.
# echo root > /etc/cron.d/cron.allow
# cp /dev/null /etc/cron.d/at.allow
# chown root:root /etc/cron.d/cron.allow /etc/cron.d/at.allow
# chmod 400 /etc/cron.d/cron.allow /etc/cron.d/at.allow
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_SOL_11_SPARC_V3R6_STIG.zip
Item Details
Audit Name: DISA Solaris 11 SPARC STIG v3r6
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-6b., CAT|II, CCI|CCI-000366, Rule-ID|SV-216360r959010_rule, STIG-ID|SOL-11.1-040420, STIG-Legacy|SV-60997, STIG-Legacy|V-48125, Vuln-ID|V-216360
Plugin: Unix
Control ID: fa2016ba7f70c43f1f950e3f157b6b3367392b2b84c97556cd873bc253f25436