STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Symantec ProxySG NDM Security Technical Implementation Guide

V-94681

CAT II (Medium)

Symantec ProxySG must employ automated mechanisms to centrally verify authentication settings.

Rule ID

SV-104511r1_rule

STIG

Symantec ProxySG NDM Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000366CCI-000372

Discussion

The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local administrator accounts for daily usage on each network device without centralized management is not scalable or feasible. Without centralized management, it is likely that credentials for some network devices will be forgotten, leading to delays in administration, which itself leads to delays in remediating production problems and in addressing compromises in a timely fashion.

Check Content

Verify a AAA server is used for access by system administrators as required in DoD.

1. Log on to the Web Management Console.
2. Click Configuration >> Authentication >> RADIUS.
3. Confirm that a RADIUS realm has been configured.
4. Click Configuration >> Policy >> Visual Policy Manager.
5. Click "Launch", select the "Admin Authentication" layer.
6. Confirm the "Action" in each rule references the RADIUS realm in step 3.

If Symantec ProxySG does not employ automated mechanisms to centrally verify authentication settings, this is a finding.

Fix Text

Configure the Symantec ProxySG to use a centrally administered AAA server.

1. Log on to the Web Management Console.
2. Click Configuration >> Authentication >> RADIUS.
3. Click "New" then enter a Realm name.
4. Under "Realm configuration" enter the IP address for the primary RADIUS server and modify port (if necessary).
5. Enter a Secret pre-shared key, and enter the same Secret pre-shred key for confirmation, click "OK".
6. Click Radius Servers.
7. Enter an IP address for the Alternate Server and modify port (if necessary).
8. Click "Apply".
9. Click Configuration >> Policy >> Visual Policy Manager.
10. Click "Launch", select the "Admin Authentication" layer.
11. Right-click the "Action" in each rule and click "Set".
12. Click "New", then "Authenticate", and choose the RADIUS realm configured in step 3.
13. Click "File", click "Install Policy on SG Appliance".