The at.deny file must not be empty if it exists.
On some systems, if there is no at.allow file and there is an empty at.deny file, then the system assumes everyone has permission to use the "at" facility. This could create an insecure setting in the case of malicious users or system intruders.
How this relates to the STIG checklist: STIG vs SCAP benchmark.