Solaris 10 SPARC Security Technical Implementation Guide

The Solaris 10 SPARC Security Technical Implementation Guide (V2 R4) has 507 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

507STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V2 · R4

CurrentPublished Thu Jan 26 2023

Access to the at utility must be controlled via the at.allow and/or at.deny file(s).

Solaris 10 SPARC Security Technical Implementation Guide

Assessment Title

Rule Text

Access to the at utility must be controlled via the at.allow and/or at.deny file(s).

Description

Discussion Text

The at facility selectively allows users to execute jobs at deferred times. It is usually used for one-time jobs. The at.allow file selectively allows access to the at facility. If there is no at.allow file, there is no ready documentation of who is allowed to submit at jobs.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-226860

Rule

SV-226860r854425_rule

Severity

medium

Rule Version

GEN003280

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Check for the existence of at.allow and at.deny files.
# ls -lL /etc/cron.d/at.allow
# ls -lL /etc/cron.d/at.deny
If neither file exists, this is a finding.

Implementation Procedure

Fix Text

Create at.allow and/or at.deny files containing appropriate lists of users to be allowed or denied access to the "at" daemon.

STIG check 285 of 507 in the Solaris 10 SPARC STIG checklist

← Previous · V-226859The cron.deny file must be group-owned by root, bin, or sys.Next · V-226861 →The at.deny file must not be empty if it exists.