The cron.deny file must be group-owned by system, bin, sys, or cron.
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.
How this relates to the STIG checklist: STIG vs SCAP benchmark.