Solaris 11 SPARC Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
The pidgin IM client package must not be installed.
<VulnDiscussion>Instant messaging is an insecure protocol.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegati...Rule Low Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The FTP daemon must not be installed unless required.
<VulnDiscussion>FTP is an insecure protocol.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></Fa...Rule High Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The TFTP service daemon must not be installed unless required.
<VulnDiscussion>TFTP is an insecure protocol.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></F...Rule High Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The telnet service daemon must not be installed unless required.
<VulnDiscussion>Telnet is an insecure protocol.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives><...Rule High Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The UUCP service daemon must not be installed unless required.
<VulnDiscussion>UUCP is an insecure protocol.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></F...Rule Low Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
Duplicate user names must not exist.
<VulnDiscussion>If a user is assigned a duplicate user name, it will create and have access to files with the first UID for that username in ...Rule Medium Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The root account must be the only account with GID of 0.
<VulnDiscussion>All accounts with a GID of 0 have root group privileges and must be limited to the group account only.</VulnDiscussion>...Rule Medium Severity -
SRG-OS-000206
<GroupDescription></GroupDescription>Group -
SRG-OS-000404
<GroupDescription></GroupDescription>Group -
The system must disable accounts after three consecutive unsuccessful login attempts.
<VulnDiscussion>Allowing continued access to accounts on the system exposes them to brute-force password-guessing attacks.</VulnDiscussion...Rule Medium Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
SRG-OS-000003
<GroupDescription></GroupDescription>Group -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The rhost-based authentication for SSH must be disabled.
<VulnDiscussion>Setting this parameter forces users to enter a password when authenticating with SSH.</VulnDiscussion><FalsePositive...Rule Medium Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
Direct root account login must not be permitted for SSH access.
<VulnDiscussion>The system should not allow users to log in as the root user directly, as audited actions would be non-attributable to a spec...Rule Medium Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
Login must not be permitted with empty/null passwords for SSH.
<VulnDiscussion>Permitting login without a password is inherently risky.</VulnDiscussion><FalsePositives></FalsePositives>&...Rule High Severity -
SRG-OS-000163
<GroupDescription></GroupDescription>Group -
The system must ignore ICMP redirect messages.
<VulnDiscussion>Ignoring ICMP redirect messages reduces the likelihood of denial of service attacks.</VulnDiscussion><FalsePositives...Rule Low Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The operating system must reveal error messages only to authorized personnel.
<VulnDiscussion>Proper file permissions and ownership ensures that only designated personnel in the organization can access error messages.&l...Rule Low Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group -
The audit system must be configured to audit all administrative, privileged, and security actions.
<VulnDiscussion>Without auditing, individual system accesses cannot be tracked, and malicious activity cannot be detected and traced back to ...Rule Medium Severity -
SRG-OS-000032
<GroupDescription></GroupDescription>Group -
The operating system must provide the capability to automatically process audit records for events of interest based upon selectable, event criteria.
<VulnDiscussion>Without an audit reporting capability, users find it difficult to identify specific patterns of attack.</VulnDiscussion>...Rule Medium Severity -
SRG-OS-000064
<GroupDescription></GroupDescription>Group -
The audit system must be configured to audit account creation.
<VulnDiscussion>Without auditing, malicious activity cannot be detected.</VulnDiscussion><FalsePositives></FalsePositives>&...Rule Medium Severity -
SRG-OS-000239
<GroupDescription></GroupDescription>Group -
The audit system must be configured to audit account modification.
<VulnDiscussion>Without auditing, malicious activity cannot be detected.</VulnDiscussion><FalsePositives></FalsePositives>&...Rule Medium Severity -
SRG-OS-000240
<GroupDescription></GroupDescription>Group -
SRG-OS-000054
<GroupDescription></GroupDescription>Group -
The operating system must generate audit records for the selected list of auditable events as defined in DoD list of events.
<VulnDiscussion>Without auditing, individual system accesses cannot be tracked, and malicious activity cannot be detected and traced back to ...Rule Medium Severity -
SRG-OS-000037
<GroupDescription></GroupDescription>Group -
Audit records must include what type of events occurred.
<VulnDiscussion>Without proper system auditing, individual system accesses cannot be tracked, and malicious activity cannot be detected and t...Rule Medium Severity -
SRG-OS-000038
<GroupDescription></GroupDescription>Group -
Audit records must include when (date and time) the events occurred.
<VulnDiscussion>Without accurate time stamps malicious activity cannot be accurately tracked.</VulnDiscussion><FalsePositives><...Rule Medium Severity -
SRG-OS-000039
<GroupDescription></GroupDescription>Group -
Audit records must include where the events occurred.
<VulnDiscussion>Without auditing, individual system accesses cannot be tracked, and malicious activity cannot be detected and traced back to ...Rule Medium Severity -
SRG-OS-000040
<GroupDescription></GroupDescription>Group -
Audit records must include the sources of the events that occurred.
<VulnDiscussion>Without accurate source information malicious activity cannot be accurately tracked.</VulnDiscussion><FalsePositives...Rule Medium Severity -
SRG-OS-000041
<GroupDescription></GroupDescription>Group -
Audit records must include the outcome (success or failure) of the events that occurred.
<VulnDiscussion>Tracking both the successful and unsuccessful attempts aids in identifying threats to the system.</VulnDiscussion><F...Rule Medium Severity -
SRG-OS-000480
<GroupDescription></GroupDescription>Group
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.