Controlling Access to crontab

Access to crontab can be controlled through using two files in the /etc/cron.d directory: cron.allow and cron.deny. These files allow only specified users to perform crontab tasks like as creating, displaying, editing or removing their own crontab files.

The cron.deny and cron.allow files consist of a list of user names for one per line. These access control files work together as given below:

Edit, display, or remove crontab files if cron.allow exists, only the users listed in this file can create.

Except for users listed in cron.deny if cron.allow does not exist, all users may submit crontab files. superuser privileges are required to run crontab if neither cron.allow nor cron.deny exists. The Superuser privileges are needed to edit or create cron.deny, cron.allow.

Note: Within  Solaris  environment access  to crontab  can     be  controlled   through  using  two   files  in  the /etc/cron.d  directory  cron.deny  and     cron.allow.   These   files   permit   just   particular   users   to perform crontab tasks like as creating, displaying, editing, or removing their own crontab files.