Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Interview the network administrator and attempt to logon to several devices.
Ensure all communication devices are in compliance with password policy.
Review the device configuration or request that the administrator to login to the device and observe the terminal. Verify that either Option A or Option B (for systems with sever character limitations) of the Standard Mandatory DoD Notice and Consent Banner is displayed at log. The required banner verbiage follows and must be displayed verbatim: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. If the system is incapable of displaying the required banner verbiage due to its size, a smaller banner must be used. The mandatory verbiage follows: “I've read & consent to terms in IS user agreem't. .
Configure all management ports and interfaces to the network device to display the DoD mandated warning banner verbiage at login regardless of the means of connection or communication. The required banner verbiage that must be displayed verbatim is as follows: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. If the system is incapable of displaying the required banner verbiage due to its size, a smaller banner must be used. The mandatory verbiage follows: “I've read & consent to terms in IS user agreem't.
Visually inspect location of modems to determine compliance.
Ensure that all modems are physically protected.
Review the configuration for the RAS. Verify that PPP is used as the communication protocol that enables a remote computer to connect to a network over standard asynchronous serial lines.
Ensure the RAS is configured to accept only communications protocols that use an accepted method of encryption to authenticate the remote node (e.g. CHAP with MD5 or MS-CHAP with MD4).
Review the configuration for the RAS . Verify use of an approved encryption algorithm if PPP is used for remote access.
Ensure that an accepted method of encryption to authenticate the remote node is used (e.g. CHAP with MD5 or MS-CHAP with MD4).
Request that the IAO/NSO provide the list for visual inspection.
Ensure an accurate listing of all RAS modems is maintained.
To verify, check the configuration of the RAS or the remote access policy server.
Ensure that if callback procedures are used, then upon establishment of the callback connection, the communications device will require the user to authenticate to the system.
Inspect the configuration of the RAS dial-up lines by using the RAS configuration screens. Verify the modem lines are configured for single line operation and multiplexing is not selected as an option available to the user or the system.
Ensure that all modem lines are restricted to single line operation.
Interview the network administrator. Verify the modem lines are configured as required with no special features.
Ensure that all modem lines are not configured to allow users to use special calling features.
Interview the network administrator. Verify the modem lines are configured as required.
Ensure all modem lines are not configured to assign either dial-in or dial-out usage for each line but not both.
Interview the IAO and ask to see a copy of the logs.
Maintain and review call logs. Audit records should be stored for a period of 1 year.
Inspect the configuration of the VPN or RAS gateway and verify that it is does not provide NAT services to the remote access end points.
Ensure that the remote access gateway is not configured to provide NAT services for remote access connections.
Review the PKI certificate menu in the device configuration to see if DoD PKI has been implement. The certificate used with contain "DoD". If a certificate is used but it is not DoD-approved, this as a finding.
If PKI is used for DEVICE authentication then ensure that a DoD approved certificate is installed. If the device does not have the option to replace the default manufacturer certificate, then the product should be replaced.
Ask if digital certificates are generated by the remote access gateway for device authentication. Examine the authentication configuration using the management interface of the remote access gateway. Verify that the key length and hashing algorithm used conform to DoD requirements.
If digital certificates are generated by the remote access solution for device authentication, then the key length and hashing algorithm used must conform to DoD requirements.
Work with the system administrator to verify that device authentication is implemented. Also, verify that mutual authentication between the remote access gateway and the endpoint is implemented.
Ensure device authentication and mutual authentication between the remote access gateway and the endpoint is implemented.
View the vendor documentation or device configuration to verify that the device is capable of generating certificate-signing requests and using DoD-approved PKI digital certificates when available.
Ensure all devices which provide remote access services are capable of generating certificate-signing requests and using DoD-approved PKI digital certificates when available.
Verify that an authentication server is required to access the remote access server by reviewing the currently running configuration. The remote access server will be configured to redirect user authentication requests to the authentication server.
The system administrator will configure the TACACS+, Radius or Diameter server with remote access accounts and user passwords. The remote access server will be configured to redirect user authentication requests to the authentication server.
Review the remote access gateway (RAS or VPN) configuration. Verify that resources and priviledges are assigned to groups not individual users. Verify that the user groups are defined on the authentication server unless not technologically feasible.
Ensure the default network access control policy is modified to restrict remote access based on group policy rather than configured for each individual user.
Work with the SA to examine the RAS. Verify the setting for the number of concurrent end user remote sessions is not set to a value which means unlimited. Value set should be reasonable based on local policy.
Ensure the setting for the number of conncurrent end user remote sessions is set to a resonable value and is not unlimited.
Work with the SA to examine the policies for the host integrity setting. Ensure there are settings and policies applicable to the listed compliance areas. Verify the following settings: - Sensitivity of information accessed such as public, non-public, administrator, classified; - Authentication method used (PKI, password, open); - User identification and authorization; - Type of user such as mobile, teleworker from home, remote DoD site enclave user, or contractor site; - Endpoint type and location (laptop, PDA, virtual, managed/unmanaged; - Other (browser type, day/time, accessed resource type).
Ensure remote access host integrity check is compliant.
Interview the site representative and review network or operating system SRR or self-assessment documentation.
Ensure remote users do not have permissions to access databases, files, and configuration management applications resident on the remote access gateway.