Skip to content

Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • TOSS must not allow blank or null passwords in the system-auth file.

    If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.
    Rule High Severity
  • TOSS must not be performing packet forwarding unless the system is a router.

    Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unn...
    Rule Medium Severity
  • The TOSS SSH daemon must not allow compression or must only allow compression after successful authentication.

    If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, pote...
    Rule Medium Severity
  • TOSS must limit the number of concurrent sessions to 256 for all accounts and/or account types.

    Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is hel...
    Rule Low Severity
  • TOSS must automatically lock graphical user sessions after 15 minutes of inactivity.

    A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporar...
    Rule Medium Severity
  • TOSS duplicate User IDs (UIDs) must not exist for interactive users.

    To ensure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system. Interactive users incl...
    Rule Medium Severity
  • TOSS must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.

    Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may...
    Rule Medium Severity
  • All TOSS local interactive user home directories must be group-owned by the home directory owner's primary group.

    If the Group Identifier (GID) of a local interactive user's home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user's files, and users that s...
    Rule Medium Severity
  • The x86 Ctrl-Alt-Delete key sequence in TOSS must be disabled if a graphical user interface is installed.

    A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the...
    Rule High Severity
  • All TOSS local interactive user home directories must be owned by the user's primary group.

    Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with an SA through shared resources.
    Rule Medium Severity

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.

Capacity
Modules