| Checked | Name | Title |
|---|
| ☐ | SV-91153r1_rule | Upon successful login, the Akamai Luna Portal must notify the administrator of the date and time of the last login. |
| ☐ | SV-91155r1_rule | The Akamai Luna Portal must notify the administrator of the number of successful login attempts. |
| ☐ | SV-91157r1_rule | The Akamai Luna Portal must initiate a session logoff after a 15-minute period of inactivity. |
| ☐ | SV-91159r1_rule | The Akamai Luna Portal must automatically audit account creation. |
| ☐ | SV-91161r1_rule | The Akamai Luna Portal must automatically audit account modification. |
| ☐ | SV-91163r1_rule | The Akamai Luna Portal must automatically audit account removal actions. |
| ☐ | SV-91165r1_rule | The Akamai Luna Portal must generate alerts that can be forwarded to the SAs and ISSO when accounts are created. |
| ☐ | SV-91167r1_rule | The Akamai Luna Portal must generate alerts that can be forwarded to the SAs and ISSO when accounts are modified. |
| ☐ | SV-91169r1_rule | The Akamai Luna Portal must generate alerts that can be forwarded to the SAs and ISSO when accounts are removed. |
| ☐ | SV-91171r1_rule | The Akamai Luna Portal must automatically audit account enabling actions. |
| ☐ | SV-91173r1_rule | The Akamai Luna Portal must notify the SAs and ISSO when accounts are created, or enabled when previously disabled. |
| ☐ | SV-91175r1_rule | The Akamai Luna Portal must audit the execution of privileged functions. |
| ☐ | SV-91177r1_rule | The Akamai Luna Portal must provide audit record generation capability for DoD-defined auditable events within the network device. |
| ☐ | SV-91179r1_rule | The Akamai Luna Portal must generate audit records when successful/unsuccessful attempts to access privileges occur. |
| ☐ | SV-91181r1_rule | The Akamai Luna Portal must enforce a minimum 15-character password length. |
| ☐ | SV-91183r1_rule | If multifactor authentication is not supported and passwords must be used, the Akamai Luna Portal must enforce password complexity by requiring that at least one upper-case character be used. |
| ☐ | SV-91185r1_rule | If multifactor authentication is not supported and passwords must be used, the Akamai Luna Portal must enforce password complexity by requiring that at least one lower-case character be used. |
| ☐ | SV-91187r1_rule | If multifactor authentication is not supported and passwords must be used, the Akamai Luna Portal must enforce password complexity by requiring that at least one numeric character be used. |
| ☐ | SV-91189r1_rule | If multifactor authentication is not supported and passwords must be used, the Akamai Luna Portal must enforce password complexity by requiring that at least one special character be used. |
| ☐ | SV-91191r1_rule | The Akamai Luna Portal must enforce a 60-day maximum password lifetime restriction. |
| ☐ | SV-91193r1_rule | The Akamai Luna Portal must prohibit password reuse for a minimum of five generations. |
| ☐ | SV-91195r1_rule | The Akamai Luna Portal must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 15 minutes of inactivity except to fulfill documented and validated mission requirements. |
| ☐ | SV-91197r1_rule | The Akamai Luna Portal must employ Security Assertion Markup Language (SAML) to automate central management of administrators. |
| ☐ | SV-91199r1_rule | The Akamai Luna Portal must employ Single Sign On (SSO) with Security Assertion Markup Language (SAML) integration to verify authentication settings. |
STIGQter: STIG Summary: