| Checked | Name | Title |
|---|
| ☐ | SV-234162r960777_rule | The FortiGate device must automatically audit account creation. |
| ☐ | SV-234163r960780_rule | The FortiGate device must automatically audit account modification. |
| ☐ | SV-234164r960786_rule | The FortiGate device must automatically audit account removal actions. |
| ☐ | SV-234165r1051115_rule | The FortiGate device must have only one local account to be used as the account of last resort in the event the authentication server is unavailable. |
| ☐ | SV-234166r1137875_rule | The FortiGate device must allow full access to only those individuals or roles designated by the ISSM. |
| ☐ | SV-234167r961362_rule | The FortiGate device must audit the execution of privileged functions. |
| ☐ | SV-234168r960840_rule | The FortiGate device must enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes. |
| ☐ | SV-234169r960843_rule | The FortiGate device must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device. |
| ☐ | SV-234170r960846_rule | The FortiGate device must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access. |
| ☐ | SV-234171r960864_rule | The FortiGate device must log all user activity. |
| ☐ | SV-234172r961800_rule | The FortiGate device must generate audit records when successful/unsuccessful attempts to modify administrator privileges occur. |
| ☐ | SV-234173r961812_rule | The FortiGate device must generate audit records when successful/unsuccessful attempts to delete administrator privileges occur. |
| ☐ | SV-234174r961824_rule | The FortiGate device must generate audit records when successful/unsuccessful logon attempts occur. |
| ☐ | SV-234175r961827_rule | The FortiGate device must generate audit records for privileged activities or other system-level access. |
| ☐ | SV-234176r961830_rule | The FortiGate device must generate audit records showing starting and ending time for administrator access to the system. |
| ☐ | SV-234177r961833_rule | The FortiGate device must generate audit records when concurrent logons from different workstations occur. |
| ☐ | SV-234178r960906_rule | The FortiGate device must generate audit records containing information that establishes the identity of any individual or process associated with the event. |
| ☐ | SV-234179r960909_rule | The FortiGate device must generate audit records containing the full-text recording of privileged commands. |
| ☐ | SV-234180r961392_rule | The FortiGate device must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-234181r961860_rule | The FortiGate device must off-load audit records on to a different system or media than the system being audited. |
| ☐ | SV-234182r961401_rule | The FortiGate device must generate an immediate real-time alert of all audit failure events requiring real-time alerts. |
| ☐ | SV-234183r987682_rule | The FortiGate device must synchronize internal information system clocks using redundant authoritative time sources. |
| ☐ | SV-234184r961443_rule | The FortiGate device must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
| ☐ | SV-234185r960936_rule | The FortiGate device must protect audit information from unauthorized deletion. |
| ☐ | SV-234186r960939_rule | The FortiGate device must protect audit tools from unauthorized access. |
| ☐ | SV-234187r960942_rule | The FortiGate device must protect audit tools from unauthorized modification. |
| ☐ | SV-234188r984110_rule | The FortiGate device must prohibit installation of software without explicit privileged status. |
| ☐ | SV-234189r961461_rule | The FortiGate device must enforce access restrictions associated with changes to device configuration. |
| ☐ | SV-234190r960960_rule | The FortiGate device must limit privileges to change the software resident within software libraries. |
| ☐ | SV-234191r961863_rule | The FortiGate device must enforce access restrictions associated with changes to the system components. |
| ☐ | SV-234192r1137887_rule | The FortiGate device must use LDAP for authentication. |
| ☐ | SV-234193r961863_rule | The FortiGate device must be running an operating system release that is currently supported by the vendor. |
| ☐ | SV-234194r961863_rule | The FortiGate device must generate log records for a locally developed list of auditable events. |
| ☐ | SV-234195r961863_rule | The FortiGate device must conduct backups of system-level information contained in the information system when changes occur. |
| ☐ | SV-234196r961863_rule | The FortiGate device must support organizational requirements to conduct backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner. |
| ☐ | SV-234197r961545_rule | FortiGate devices performing maintenance functions must restrict use of these functions to authorized personnel only. |
| ☐ | SV-234198r961863_rule | The FortiGate device must use DoD-approved Certificate Authorities (CAs) for public key certificates. |
| ☐ | SV-234199r1043177_rule | The FortiGate device must prohibit the use of all unnecessary and/or non-secure functions, ports, protocols, and/or services. |
| ☐ | SV-234200r960993_rule | The FortiGate device must implement replay-resistant authentication mechanisms for network access to privileged accounts. |
| ☐ | SV-234201r961506_rule | The FortiGate device must authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC). |
| ☐ | SV-234202r961506_rule | The FortiGate device must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based. |
| ☐ | SV-234203r984092_rule | The FortiGate device must enforce a minimum 15-character password length. |
| ☐ | SV-234204r984095_rule | The FortiGate device must enforce password complexity by requiring that at least one uppercase character be used. |
| ☐ | SV-234205r984098_rule | The FortiGate device must enforce password complexity by requiring that at least one lowercase character be used. |
| ☐ | SV-234206r984099_rule | The FortiGate device must enforce password complexity by requiring at least one numeric character be used. |
| ☐ | SV-234207r984100_rule | The FortiGate device must enforce password complexity by requiring that at least one special character be used. |
| ☐ | SV-234208r961029_rule | The FortiGate device must use LDAPS for the LDAP connection. |
| ☐ | SV-234209r984088_rule | The FortiGate device must not have any default manufacturer passwords when deployed. |
| ☐ | SV-234210r961050_rule | The FortiGate device must use FIPS 140-2 approved algorithms for authentication to a cryptographic module. |
| ☐ | SV-234211r961554_rule | The FortiGate devices must use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of nonlocal maintenance and diagnostic communications. |
| ☐ | SV-234212r961557_rule | The FortiGate device must implement cryptographic mechanisms using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions. |
| ☐ | SV-234213r984105_rule | The FortiGate device must terminate idle sessions after 10 minutes of inactivity. |
| ☐ | SV-234214r961068_rule | The FortiGate device must terminate idle sessions after 10 minutes of inactivity. |
| ☐ | SV-234215r1043181_rule | The FortiGate device must generate unique session identifiers using a FIPS 140-2-approved random number generator. |
| ☐ | SV-234216r961128_rule | The FortiGate device must only allow authorized administrators to view or change the device configuration, system files, and other files stored either in the device or on removable media (such as a flash drive). |
| ☐ | SV-234217r961620_rule | The FortiGate device must protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards. |
| ☐ | SV-234218r1137890_rule | The FortiGate device must be configured to send log data to a central log server for the purpose of forwarding alerts to the administrators and the ISSO. |
| ☐ | SV-234219r960735_rule | The FortiGate device must limit the number of logon and user sessions. |
| ☐ | SV-234220r984089_rule | The FortiGate device must only install patches or updates that are validated by the vendor via digital signature or hash. |
| ☐ | SV-234221r1153456_rule | The FortiGate device must require that when a password is changed, the characters are changed in at least eight of the positions within the password. |
STIGQter: STIG Summary: