| Checked | Name | Title |
|---|
| ☐ | SV-216246r986419_rule | The audit system must produce records containing sufficient information to establish the identity of any user/subject associated with the event. |
| ☐ | SV-216249r958430_rule | The operating system must provide the capability to automatically process audit records for events of interest based upon selectable, event criteria. |
| ☐ | SV-216251r958446_rule | The operating system must generate audit records for the selected list of auditable events as defined in DoD list of events. |
| ☐ | SV-216253r958412_rule | Audit records must include what type of events occurred. |
| ☐ | SV-216254r958414_rule | Audit records must include when (date and time) the events occurred. |
| ☐ | SV-216255r958416_rule | Audit records must include where the events occurred. |
| ☐ | SV-216256r958418_rule | Audit records must include the sources of the events that occurred. |
| ☐ | SV-216257r958420_rule | Audit records must include the outcome (success or failure) of the events that occurred. |
| ☐ | SV-216258r959010_rule | The audit system must be configured to audit file deletions. |
| ☐ | SV-216259r958368_rule | The audit system must be configured to audit account creation. |
| ☐ | SV-216260r958590_rule | The audit system must be configured to audit account modification. |
| ☐ | SV-216261r958592_rule | The operating system must automatically audit account disabling actions. |
| ☐ | SV-216262r958594_rule | The operating system must automatically audit account termination. |
| ☐ | SV-216263r959010_rule | The operating system must ensure unauthorized, security-relevant configuration changes detected are tracked. |
| ☐ | SV-216264r959010_rule | The audit system must be configured to audit all administrative, privileged, and security actions. |
| ☐ | SV-216265r958406_rule | The audit system must be configured to audit login, logout, and session initiation. |
| ☐ | SV-216268r959010_rule | The audit system must be configured to audit failed attempts to access files and programs. |
| ☐ | SV-216269r958440_rule | The operating system must protect against an individual falsely denying having performed a particular action. In order to do so the system must be configured to send audit records to a remote audit server. |
| ☐ | SV-216270r959010_rule | The auditing system must not define a different auditing level for specific users. |
| ☐ | SV-216273r958424_rule | The operating system must alert designated organizational officials in the event of an audit processing failure. |
| ☐ | SV-216276r1038966_rule | The operating system must shut down by default upon audit failure (unless availability is an overriding concern). |
| ☐ | SV-216277r958434_rule | The operating system must protect audit information from unauthorized access. |
| ☐ | SV-216280r959010_rule | The System packages must be up to date with the most recent vendor updates and security fixes. |
| ☐ | SV-216282r958610_rule | The operating system must protect audit tools from unauthorized access. |
| ☐ | SV-216283r958612_rule | The operating system must protect audit tools from unauthorized modification. |
| ☐ | SV-216284r958614_rule | The operating system must protect audit tools from unauthorized deletion. |
| ☐ | SV-216285r958634_rule | System packages must be configured with the vendor-provided files, permissions, and ownerships. |
| ☐ | SV-216286r959010_rule | The finger daemon package must not be installed. |
| ☐ | SV-216287r959010_rule | The legacy remote network access utilities daemons must not be installed. |
| ☐ | SV-216288r959010_rule | The NIS package must not be installed. |
| ☐ | SV-216289r959010_rule | The pidgin IM client package must not be installed. |
| ☐ | SV-216290r959010_rule | The FTP daemon must not be installed unless required. |
| ☐ | SV-216291r959010_rule | The TFTP service daemon must not be installed unless required. |
| ☐ | SV-216292r959010_rule | The telnet service daemon must not be installed unless required. |
| ☐ | SV-216293r959010_rule | The UUCP service daemon must not be installed unless required. |
| ☐ | SV-216294r959010_rule | The rpcbind service must be configured for local only services unless organizationally defined. |
| ☐ | SV-216295r959010_rule | The VNC server package must not be installed unless required. |
| ☐ | SV-216297r958478_rule | The operating system must be configured to provide essential capabilities. |
| ☐ | SV-216299r959010_rule | All run control scripts must have mode 0755 or less permissive. |
| ☐ | SV-216300r959010_rule | All run control scripts must have no extended ACLs. |
| ☐ | SV-216301r959010_rule | Run control scripts executable search paths must contain only authorized paths. |
| ☐ | SV-216302r959010_rule | Run control scripts library search paths must contain only authorized paths. |
| ☐ | SV-216303r959010_rule | Run control scripts lists of preloaded libraries must contain only authorized paths. |
| ☐ | SV-216304r959010_rule | Run control scripts must not execute world writable programs or scripts. |
| ☐ | SV-216305r959010_rule | All system start-up files must be owned by root. |
| ☐ | SV-216306r959010_rule | All system start-up files must be group-owned by root, sys, or bin. |
| ☐ | SV-216307r959010_rule | System start-up files must only execute programs owned by a privileged UID or an application. |
| ☐ | SV-216308r959010_rule | Any X Windows host must write .Xauthority files. |
| ☐ | SV-216309r959010_rule | All .Xauthority files must have mode 0600 or less permissive. |
| ☐ | SV-216310r959010_rule | The .Xauthority files must not have extended ACLs. |
| ☐ | SV-216311r959010_rule | X displays must not be exported to the world. |
| ☐ | SV-216312r959010_rule | .Xauthority or X*.hosts (or equivalent) file(s) must be used to restrict access to the X server. |
| ☐ | SV-216313r959010_rule | The .Xauthority utility must only permit access to authorized hosts. |
| ☐ | SV-216314r959010_rule | X Window System connections that are not required must be disabled. |
| ☐ | SV-216315r959010_rule | The graphical login service provides the capability of logging into the system using an X-Windows type interface from the console. If graphical login access for the console is required, the service must be in local-only mode. |
| ☐ | SV-216316r959010_rule | Generic Security Services (GSS) must be disabled. |
| ☐ | SV-216317r959010_rule | Systems services that are not required must be disabled. |
| ☐ | SV-216318r959010_rule | TCP Wrappers must be enabled and configured per site policy to only allow access by approved hosts and services. |
| ☐ | SV-216321r1038967_rule | User passwords must be changed at least every 60 days. |
| ☐ | SV-216322r958364_rule | The operating system must automatically terminate temporary accounts within 72 hours. |
| ☐ | SV-216323r1016269_rule | The operating system must enforce minimum password lifetime restrictions. |
| ☐ | SV-216324r1016270_rule | User passwords must be at least 15 characters in length. |
| ☐ | SV-216326r1016271_rule | The system must require at least eight characters be changed between the old and new passwords during a password change. |
| ☐ | SV-216327r1016272_rule | The system must require passwords to contain at least one uppercase alphabetic character. |
| ☐ | SV-216328r1016273_rule | The operating system must enforce password complexity requiring that at least one lowercase character is used. |
| ☐ | SV-216329r1016274_rule | The system must require passwords to contain at least one numeric character. |
| ☐ | SV-216330r1016275_rule | The system must require passwords to contain at least one special character. |
| ☐ | SV-216331r959010_rule | The system must require passwords to contain no more than three consecutive repeating characters. |
| ☐ | SV-216332r959010_rule | The system must not have accounts configured with blank or null passwords. |
| ☐ | SV-216333r1016276_rule | Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. |
| ☐ | SV-216334r958388_rule | The system must disable accounts after three consecutive unsuccessful login attempts. |
| ☐ | SV-216335r959010_rule | The delay between login prompts following a failed login attempt must be at least 4 seconds. |
| ☐ | SV-216336r958400_rule | The system must require users to re-authenticate to unlock a graphical desktop environment. |
| ☐ | SV-216337r958402_rule | Graphical desktop environments provided by the system must automatically lock after 15 minutes of inactivity. |
| ☐ | SV-216338r959010_rule | The system must prevent the use of dictionary words for passwords. |
| ☐ | SV-216340r1016277_rule | The operating system must require individuals to be authenticated with an individual authenticator prior to using a group authenticator. |
| ☐ | SV-216341r959010_rule | The default umask for system and users must be 077. |
| ☐ | SV-216342r959010_rule | The default umask for FTP users must be 077. |
| ☐ | SV-216343r959010_rule | The value mesg n must be configured as the default setting for all users. |
| ☐ | SV-216344r1016278_rule | User accounts must be locked after 35 days of inactivity. |
| ☐ | SV-216347r959010_rule | Login services for serial ports must be disabled. |
| ☐ | SV-216348r959010_rule | Access to a domain console via telnet must be restricted to the local host. |
| ☐ | SV-216349r959010_rule | Access to a logical domain console must be restricted to authorized users. |
| ☐ | SV-216350r959010_rule | The nobody access for RPC encryption key storage service must be disabled. |
| ☐ | SV-216351r959010_rule | X11 forwarding for SSH must be disabled. |
| ☐ | SV-216353r959010_rule | The rhost-based authentication for SSH must be disabled. |
| ☐ | SV-216354r959010_rule | Direct root account login must not be permitted for SSH access. |
| ☐ | SV-216355r959010_rule | Login must not be permitted with empty/null passwords for SSH. |
| ☐ | SV-216356r970703_rule | The operating system must terminate the network connection associated with a communications session at the end of the session or after 10 minutes of inactivity. |
| ☐ | SV-216357r959010_rule | Host-based authentication for login-based services must be disabled. |
| ☐ | SV-216358r959010_rule | The use of FTP must be restricted. |
| ☐ | SV-216359r959010_rule | The system must not allow autologin capabilities from the GNOME desktop. |
| ☐ | SV-216360r959010_rule | Unauthorized use of the at or cron capabilities must not be permitted. |
| ☐ | SV-216361r959010_rule | Logins to the root account must be restricted to the system console only. |
| ☐ | SV-216362r987814_rule | The operating system, upon successful logon, must display to the user the date and time of the last logon (access). |
| ☐ | SV-216363r1016279_rule | The operating system must provide the capability for users to directly initiate session lock mechanisms. |
| ☐ | SV-216364r958404_rule | The operating system session lock mechanism, when activated on a device with a display screen, must place a publicly viewable pattern onto the associated display, hiding what was previously visible on the screen. |
| ☐ | SV-216365r959010_rule | The operating system must not allow logins for users with blank passwords. |
| ☐ | SV-216366r959010_rule | The operating system must prevent remote devices that have established a non-remote connection with the system from communicating outside of the communication path with resources in external networks. |
| ☐ | SV-216367r958398_rule | The operating system must limit the number of concurrent sessions for each account to an organization-defined number of sessions. |
| ☐ | SV-216368r959010_rule | The system must disable directed broadcast packet forwarding. |
| ☐ | SV-216369r959010_rule | The system must not respond to ICMP timestamp requests. |
| ☐ | SV-216370r959010_rule | The system must not respond to ICMP broadcast timestamp requests. |
| ☐ | SV-216371r959010_rule | The system must not respond to ICMP broadcast netmask requests. |
| ☐ | SV-216372r959010_rule | The system must not respond to broadcast ICMP echo requests. |
| ☐ | SV-216373r959010_rule | The system must not respond to multicast echo requests. |
| ☐ | SV-216374r959010_rule | The system must ignore ICMP redirect messages. |
| ☐ | SV-216375r959010_rule | The system must set strict multihoming. |
| ☐ | SV-216376r959010_rule | The system must disable ICMP redirect messages. |
| ☐ | SV-216377r959010_rule | The system must disable TCP reverse IP source routing. |
| ☐ | SV-216378r959010_rule | The system must set maximum number of half-open TCP connections to 4096. |
| ☐ | SV-216379r959010_rule | The system must set maximum number of incoming connections to 1024. |
| ☐ | SV-216380r959010_rule | The system must disable network routing unless required. |
| ☐ | SV-216381r959010_rule | The system must implement TCP Wrappers. |
| ☐ | SV-216387r1045450_rule | The boundary protection system (firewall) must be configured to deny network traffic by default and must allow network traffic by exception (i.e., deny all, permit by exception). |
| ☐ | SV-216394r959010_rule | The system must prevent local applications from generating source-routed packets. |
| ☐ | SV-216395r1184793_rule | The operating system must display the DOD-approved system use notification message or banner before granting access to the system for general system logons. |
| ☐ | SV-216396r958390_rule | The operating system must display the DoD approved system use notification message or banner for SSH connections. |
| ☐ | SV-216397r1184796_rule | The GNOME service must display the DOD-approved system use notification message or banner before granting access to the system. |
| ☐ | SV-216398r1184798_rule | The FTP service must display the DOD-approved system use notification message or banner before granting access to the system. |
| ☐ | SV-216399r986416_rule | The operating system must terminate all sessions and network connections when nonlocal maintenance is completed. |
| ☐ | SV-216400r959010_rule | The operating system must prevent internal users from sending out packets which attempt to manipulate or spoof invalid IP addresses. |
| ☐ | SV-216401r958358_rule | Wireless network adapters must be disabled. |
| ☐ | SV-216402r958358_rule | The operating system must use mechanisms for authentication to a cryptographic module meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for such authentication. |
| ☐ | SV-216410r958408_rule | The operating system must implement DoD-approved encryption to protect the confidentiality of remote access sessions. |
| ☐ | SV-216411r959010_rule | The operating system must use cryptographic mechanisms to protect and restrict access to information on portable digital media. |
| ☐ | SV-216413r958552_rule | The operating system must protect the confidentiality and integrity of information at rest. |
| ☐ | SV-216415r958576_rule | The operating system must use cryptographic mechanisms to protect the integrity of audit information. |
| ☐ | SV-216417r959010_rule | The sticky bit must be set on all world writable directories. |
| ☐ | SV-216418r959010_rule | Permissions on user home directories must be 750 or less permissive. |
| ☐ | SV-216419r959010_rule | Permissions on user . (hidden) files must be 750 or less permissive. |
| ☐ | SV-216420r959010_rule | Permissions on user .netrc files must be 750 or less permissive. |
| ☐ | SV-216421r959010_rule | There must be no user .rhosts files. |
| ☐ | SV-216422r959010_rule | Groups assigned to users must exist in the /etc/group file. |
| ☐ | SV-216423r959010_rule | Users must have a valid home directory assignment. |
| ☐ | SV-216424r959010_rule | All user accounts must be configured to use a home directory that exists. |
| ☐ | SV-216425r959010_rule | All home directories must be owned by the respective user assigned to it in /etc/passwd. |
| ☐ | SV-216426r958482_rule | Duplicate User IDs (UIDs) must not exist for users within the organization. |
| ☐ | SV-216427r958504_rule | Duplicate UIDs must not exist for multiple non-organizational users. |
| ☐ | SV-216428r959010_rule | Duplicate Group IDs (GIDs) must not exist for multiple groups. |
| ☐ | SV-216429r959010_rule | Reserved UIDs 0-99 must only be used by system accounts. |
| ☐ | SV-216430r959010_rule | Duplicate user names must not exist. |
| ☐ | SV-216431r959010_rule | Duplicate group names must not exist. |
| ☐ | SV-216432r959010_rule | User .netrc files must not exist. |
| ☐ | SV-216433r959010_rule | The system must not allow users to configure .forward files. |
| ☐ | SV-216434r959010_rule | World-writable files must not exist. |
| ☐ | SV-216435r959010_rule | All valid SUID/SGID files must be documented. |
| ☐ | SV-216436r959010_rule | The operating system must have no unowned files. |
| ☐ | SV-216437r959010_rule | The operating system must have no files with extended attributes. |
| ☐ | SV-216438r959010_rule | The root account must be the only account with GID of 0. |
| ☐ | SV-216439r958566_rule | The operating system must reveal error messages only to authorized personnel. |
| ☐ | SV-216441r959010_rule | The operator must document all file system objects that have non-standard access control list settings. |
| ☐ | SV-216442r1155800_rule | The operating system must be a supported release. |
| ☐ | SV-216443r959010_rule | The system must implement non-executable program stacks. |
| ☐ | SV-216444r959010_rule | Address Space Layout Randomization (ASLR) must be enabled. |
| ☐ | SV-216445r959010_rule | Process core dumps must be disabled unless needed. |
| ☐ | SV-216446r959010_rule | The system must be configured to store any process core dumps in a specific, centralized directory. |
| ☐ | SV-216447r959010_rule | The centralized process core dump data directory must be owned by root. |
| ☐ | SV-216448r959010_rule | The centralized process core dump data directory must be group-owned by root, bin, or sys. |
| ☐ | SV-216449r959010_rule | The centralized process core dump data directory must have mode 0700 or less permissive. |
| ☐ | SV-216450r959010_rule | Kernel core dumps must be disabled unless needed. |
| ☐ | SV-216451r959010_rule | The kernel core dump data directory must be owned by root. |
| ☐ | SV-216452r959010_rule | The kernel core dump data directory must be group-owned by root. |
| ☐ | SV-216453r959010_rule | The kernel core dump data directory must have mode 0700 or less permissive. |
| ☐ | SV-216454r959010_rule | The system must require passwords to change the boot device settings. (SPARC) |
| ☐ | SV-216455r959010_rule | The operating system must implement transaction recovery for transaction-based systems. |
| ☐ | SV-216456r1190826_rule | SNMP default community strings and passphrases must be changed from vendor defaults. |
| ☐ | SV-216457r959010_rule | A file integrity baseline must be created, maintained, and reviewed at least weekly to determine if unauthorized changes have been made to important system files located in the root file system. |
| ☐ | SV-216459r959010_rule | Direct logins must not be permitted to shared, default, application, or utility accounts. |
| ☐ | SV-216460r959010_rule | The system must not have any unnecessary accounts. |
| ☐ | SV-216461r959010_rule | The operating system must conduct backups of user-level information contained in the operating system per organization-defined frequency to conduct backups consistent with recovery time and recovery point objectives. |
| ☐ | SV-216462r959010_rule | The operating system must conduct backups of system-level information contained in the information system per organization-defined frequency to conduct backups that are consistent with recovery time and recovery point objectives. |
| ☐ | SV-216463r959010_rule | The operating system must conduct backups of operating system documentation including security-related documentation per organization-defined frequency to conduct backups that is consistent with recovery time and recovery point objectives. |
| ☐ | SV-216464r958544_rule | The operating system must prevent the execution of prohibited mobile code. |
| ☐ | SV-216465r959010_rule | The operating system must employ PKI solutions at workstations, servers, or mobile computing devices on the network to create, manage, distribute, use, store, and revoke digital certificates. |
| ☐ | SV-216467r959010_rule | The operating system must employ malicious code protection mechanisms at workstations, servers, or mobile computing devices on the network to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means. |
| ☐ | SV-216469r958574_rule | The operating system must back up audit records at least every seven days onto a different system or system component than the system or component being audited. |
| ☐ | SV-216470r1099906_rule | All manual editing of system-relevant files shall be done using the pfedit command, which logs changes made to the files. |
| ☐ | SV-216473r958528_rule | The operating system must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial of service attacks. |
| ☐ | SV-216474r959010_rule | The /etc/zones directory, and its contents, must have the vendor default owner, group, and permissions. |
| ☐ | SV-216475r959010_rule | The limitpriv zone option must be set to the vendor default or less permissive. |
| ☐ | SV-216476r959010_rule | The systems physical devices must not be assigned to non-global zones. |
| ☐ | SV-216477r959010_rule | The audit system must identify in which zone an event occurred. |
| ☐ | SV-216478r959010_rule | The audit system must maintain a central audit trail for all zones. |
| ☐ | SV-216479r959010_rule | The operating system must monitor for unauthorized connections of mobile devices to organizational information systems. |
| ☐ | SV-219959r958768_rule | The audit system must support an audit reduction capability. |
| ☐ | SV-219960r958774_rule | The audit system records must be able to be used by a report generation capability. |
| ☐ | SV-219961r958442_rule | The audit records must provide data for all auditable events defined at the organizational level for the organization-defined information system components. |
| ☐ | SV-219962r958442_rule | The operating system must support the capability to compile audit records from multiple components within the system into a system-wide (logical or physical) audit trail that is time-correlated to within organization-defined level of tolerance. |
| ☐ | SV-219963r958442_rule | The audit system must be configured to audit all discretionary access control permission modifications. |
| ☐ | SV-219964r958442_rule | The audit system must be configured to audit the loading and unloading of dynamic kernel modules. |
| ☐ | SV-219965r971542_rule | The audit system must alert the SA when the audit storage volume approaches its capacity. |
| ☐ | SV-219966r958758_rule | The audit system must alert the System Administrator (SA) if there is any type of audit failure. |
| ☐ | SV-219967r958752_rule | The operating system must allocate audit record storage capacity. |
| ☐ | SV-219968r1207680_rule | The operating system must configure auditing to reduce the likelihood of storage capacity being exceeded. |
| ☐ | SV-219969r1016281_rule | The system must verify that package updates are digitally signed. |
| ☐ | SV-219970r958794_rule | The operating system must employ automated mechanisms, per organization-defined frequency, to detect the addition of unauthorized components/devices into the operating system. |
| ☐ | SV-219971r958804_rule | The operating system must employ automated mechanisms to prevent program execution in accordance with the organization-defined specifications. |
| ☐ | SV-219972r958548_rule | The operating system must disable information system functionality that provides the capability for automatic execution of code on mobile devices without user direction. |
| ☐ | SV-219973r958726_rule | The system must restrict the ability of users to assume excessive privileges to members of a defined group and prevent unauthorized users from accessing administrative tools. |
| ☐ | SV-219975r987791_rule | The operating system must employ FIPS-validate or NSA-approved cryptography to implement digital signatures. |
| ☐ | SV-219976r958908_rule | The operating system must protect the integrity of transmitted information. |
| ☐ | SV-219977r1117271_rule | The operating system must employ cryptographic mechanisms to recognize changes to information during transmission unless otherwise protected by alternative physical measures. |
| ☐ | SV-219978r958912_rule | The operating system must maintain the integrity of information during aggregation, packaging, and transformation in preparation for transmission. |
| ☐ | SV-219979r958908_rule | The operating system must protect the confidentiality of transmitted information. |
| ☐ | SV-219980r1117271_rule | The operating system must employ cryptographic mechanisms to prevent unauthorized disclosure of information during transmission unless otherwise protected by alternative physical measures. |
| ☐ | SV-219981r958912_rule | The operating system must maintain the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission. |
| ☐ | SV-219982r1207682_rule | The operating system must employ cryptographic mechanisms to protect information in storage. |
| ☐ | SV-219984r958908_rule | The operating system must protect the integrity of transmitted information. |
| ☐ | SV-219985r958732_rule | The operating system must protect the audit records resulting from non-local accesses to privileged accounts and the execution of privileged functions. |
| ☐ | SV-219986r1016282_rule | The operating system must synchronize internal information system clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). |
| ☐ | SV-219987r958944_rule | The operating system must verify the correct operation of security functions in accordance with organization-defined conditions and in accordance with organization-defined frequency (if periodic verification). |
| ☐ | SV-224670r958726_rule | The operating system must prevent non-privileged users from circumventing malicious code protection capabilities. |
| ☐ | SV-224671r958944_rule | The operating system must identify potentially security-relevant error conditions. |
| ☐ | SV-233300r959010_rule | The sshd server must bind the X11 forwarding server to the loopback address. |
STIGQter: STIG Summary: