| Finding ID |
Severity |
Title |
Description |
|
V-256844
|
High |
Compliance Guardian must use multifactor authentication for network access to privileged accounts. |
Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased.
Multifactor authentication requires using two or more factors to achieve authentication. Factors include:
(i) Something a user knows (e.g., password/PIN);
(ii) Something a user has (e.g., cryptographic identification device, token); or
(iii) Something a... |
|
V-256841
|
High |
Compliance Guardian must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access. |
Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol.
This requirement applies to Transport Layer Security (TLS) gateways (also known as Secure Sockets Layer [SSL] gateways), web servers, and web applications and is not applicable... |
|
V-256848
|
Medium |
Compliance Guardian must only allow the use of DOD PKI established certificate authorities for verification of the establishment of protected sessions. |
Untrusted Certificate Authorities (CAs) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DOD-approved CA, trust of this CA has not been established.... |
|
V-256847
|
Medium |
Compliance Guardian must conform to FICAM-issued profiles. |
Without conforming to FICAM-issued profiles, the information system may not be interoperable with FICAM-authentication protocols, such as SAML 2.0 and OpenID 2.0.
This requirement addresses open identity management standards. |
|
V-256846
|
Medium |
Compliance Guardian must accept FICAM-approved third-party credentials. |
Access may be denied to legitimate users if FICAM-approved third-party credentials are not accepted.
This requirement typically applies to organizational information systems that are accessible to nonfederal government agencies and other partners. This allows federal government-relying parties to trust such credentials at their approved assurance levels.
Third-party credentials are those... |
|
V-256845
|
Medium |
Compliance Guardian must control remote access methods. |
Remote access applications (such as those providing remote access to network devices and information systems) which lack automated control capabilities, increase risk, and make remote user access management difficult at best.
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through... |
|
V-256843
|
Medium |
Compliance Guardian must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems. Applications are capable of providing a wide variety of functions and services.... |
|
V-256842
|
Medium |
Compliance Guardian must provide automated mechanisms for supporting account management functions. |
Remote access (e.g., Remote Desktop Protocol [RDP]) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include dial-up, broadband, and wireless.
Satisfies: SRG-APP-000023, SRG-APP-000025, SRG-APP-000065, SRG-APP-000163, SRG-APP-000164, SRG-APP-000165, SRG-APP-000166, SRG-APP-000167, SRG-APP-000168, SRG-APP-000169, SRG-APP-000170, SRG-APP-000171, SRG-APP-000173,... |
|
V-256840
|
Medium |
Compliance Guardian must initiate a session timeout after a 15-minute period 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 temporary nature of the absence. Rather than relying on the user to manually lock their application... |
|
V-256839
|
Medium |
Compliance Guardian must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types. |
Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks.
This requirement may be met via the application or by utilizing information system... |
