Symantec ProxySG must implement HTTPS-console to provide replay-resistant authentication mechanisms for network access to privileged accounts.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94697SYMP-NM-000230SV-104527r1_ruleCCI-001941medium
Description
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.
STIGDate
Symantec ProxySG NDM Security Technical Implementation Guide2019-12-20

Related Frameworks

3 paths across 3 frameworks
NIST 800-531 mapping
  • DISA · V1R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.5.4
1.00
  • DISA · V1R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-001941
1.00
  • DISA · V1R2 · disa_xccdf · related

Details

Check Text (C-104527r1_chk)

Verify only TLS management services are enabled. 1. Log on to Web Management Console. 2. Click Configuration >> Services >> Management Services. 3. Verify "HTTP-Console" is not enabled and that "HTTPS-Console" is enabled. If Symantec ProxySG does not implement HTTPS-console, this is a finding.

Fix Text (F-100815r1_fix)

Enable TLS management services. 1. Log on to Web Management Console. 2. Click Configuration >> Services >> Management Services. 3. Make sure that "HTTPS-Console" is "Enabled". 4. Uncheck "Enabled" next to that "HTTP-Console". 5. Click "Apply".