What changed in Symantec Edge SWG NDM STIG V1R3V1R3 changes

Fix text

1. In the Edge SWG Web UI, navigate to the VPM. 2. Click "Add Layer". 3. Scroll down and select "Admin Access", then click "Add". 4. Locate the Admin Access Layer (1) layer that was added and click "Add rule". 5. Inside of the rule, under "Source", left-click and select "Set". 6. Click "Add new Object". 7. Select "Group". 8. Under the group field, type in the full LDAPS Distinguished Name (DN) for the admin group. For example: "CN=roadcom.admins.gsg,OU=BROADCOM,OU=Vendors, DC=dodDoW,DC=local" 9. Under the "Authentication Realm", select the "CAC certificate" realm. 10. Click "Apply", then click "Set". 11. In the same rule, left-click in the "Service" field and click "Set". 12. Select "Service Name: HTTPS-console" and click "Set". 13. In the same rule, left-click in the "Action" field and click "Set". 14. Select the action "Allow Read/Write Access" and click "Set". 15. Repeat these steps to add various read-only or read-write groups for the HTTPS-console. 16. For the SSH-Console click "Add rule". 17. Inside of the rule, under "Source", left-click and select "Set". 18. Click "Add new Object". 19. Select "Group". 20. Under the "Group" field, type in the full LDAPS Distinguished Name (DN) for the admin group. For example: CN=broadcom.admins.gsg,OU=BROADCOM,OU=Vendors, DC=dodDoW,DC=local 21. Under the "Authentication Realm", select the "LDAPS" realm. Do not select the CAC certificate realm. 22. Click "Apply", then click "Set". 23. In the same rule, left-click in the "Service" field and click "Set". 24. Select "Service Name: SSH-console", and then click "Set". 25. In the same rule, left-click in the "Action" field and click "Set". 26. Select the action "Allow Read/Write Access" and click "Set". 27. Repeat these steps to add various read-only or read-write groups for the SSH-console.

Discussion

Successful identification and authentication must not automatically give an entity full access to a network device or security domain. The lack of authorization-based access control could result in the immediate compromise and unauthorized access to sensitive information. All DODDoW systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset or set of resources. Information systems use access control policies and enforcement mechanisms to implement this requirement. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Some network devices are preconfigured with security groups. Other network devices enable operators to create custom security groups with custom permissions. For example, an information system security manager (ISSM) may require read-only access to audit the network device. Operators may create an audit security group, define permissions and access levels for members of the group, and then assign the ISSM's user persona to the audit security group. This is still considered privileged access, but the ISSM's security group is more restrictive than the network administrator's security group. Network devices that rely on AAA brokers for authentication and authorization services may need to identify the available security groups or access levels available on the network devices and convey that information to the AAA operator. Once the AAA broker identifies the user persona on the centralized directory service, the user's security group memberships can be retrieved. The AAA operator may need to create a mapping that links target security groups from the directory service to the appropriate security groups or access levels on the network device. Once these mappings are configured, authorizations can happen dynamically, based on each user's directory service group membership. Satisfies: SRG-APP-000033-NDM-000212, SRG-APP-000038-NDM-000213, SRG-APP-000340-NDM-000288, SRG-APP-000378-NDM-000302, SRG-APP-000380-NDM-000304, SRG-APP-000516-NDM-000335

V-279250 in V1R3

Fix text

In the Edge SWG Web UI, navigate to the Configuration tab. 1. Under the "Authentication" section under "Configuration and Realms and Domains", click "Add Realm and LDAP". 2. Add a name. 3. Under "Primary Server", enter the fully qualified domain name (FDQN) of the LDAPS primary domain controller (e.g., dc1.dodDoW.mil), then enter the port number, e.g., 636. 4. Click "Enable SSL". 5. Select the SSL device profile created in SYME-ND-000800. 6. Under "User attribute Type": userPrincipalName. 7. Click "Add DN". 8. Enter the path of the domain (e.g., dc=dodDoW,dc=mil). 9. Click "Show" under "Advanced Settings". 10. Click "Use the same refresh time for all" and set the refresh time to 10 seconds. 11. Set the Inactivity Timeout to 600 seconds. 12. Select "Local" for Group Comparison. 13. Under Alternate Server, type the secondary LDAPS domain controller (e.g., dc2.dodDoW.mil), then enter the port number, e.g., 636. 14. Under "Search", click "only Authorized" and add the search user and password (i.e., the LDAPS service account) in DN format (e.g., CN=broadcom_svc,OU=BROADCOM,DC=dodDoW,DC=mil) 15. Under "Groups" select "user" for membership type and attribute as member of. 16. Under "Object Classes" ensure "container" is selected. 17. Click the "test Configuration" to ensure all configuration has been entered correctly. In the Edge SWG Web UI, navigate to the Configuration tab. 1. Under the Authentication section under "Configuration and Realms and Domains", click "Add Realm and Certificate". 2. Make the name: "CAC" 3. Under username enter: $(SubjectAltName.OtherName) 4. Under full username enter: $(SubjectAltName.OtherName.1) 5. Ensure "Authorization Realm" is checked and the previous LDAPS realm is selected. 6. Under "Authorization Username", select "Determined by Search". 7. Ensure the LDAPS search realm is selected. 8. Enter the following in the search filter: (userPrincipalName=$(cs-username)) and ensure the user attribute "Use FQDN" is selected. 9. Click "Show" advanced settings. 10. Ensure "Use persistent cookies" and "Verify the IP address in the cookie" are not checked. In the Edge SWG Web UI, navigate to the Configuration tab. 1. Under "Services", click "Proxy Services". 2. Click "Add Service". 3. Name the service "CAC-MC-Notify". 4. Under "Proxy type", select "HTTPS Reverse Proxy". 5. Under "Key Ring and CCL", use those created under SYME-ND-000800. 6. Ensure SSL version is TLS 1.2 or 1.3 only. 7. Under "Listeners", add the management IPv4 address intercepting on port 444. 8. Under "Listeners", add the management IPv6 address intercepting on port 444. In the Edge SWG Web UI, navigate to the VPM. 1. Go to the Symantec web portal to download the CPL text file called "AdminLoginBanner.txt", which will be used at https://knowledge.broadcom.com/external/article/388134. 2. Click "Add Layer". 3. Select "CPL". 4. Download the exact CPL file hosted on the Symantec website. 5. Click "Apply Policy" and ensure it loaded correctly. Go back to the main portion of the VPM. 1. Click "Add Layer". 2. Scroll down and select "Admin Access", then click "Add". 3. Locate the Admin Access Layer (1) that was added and click "Add rule". 4. Inside of the rule, under "Source", left-click and select "Set". 5. Click "Add new Object". 6. Select "Group". 7. Under "Group" type in the full LDAPS full Distinguished Name (DN) for the admin group. e.g., CN=broadcom.admins.gsg,OU=BROADCOM,OU=Vendors,DC=dodDoW,DC=local 8. Under the "Authentication Realm", select the "CAC Certificate Realm". 9. Click "Apply", then click "Set". 10. In the same rule, left-click in the "Service" field and click "Set". 11. Select Service Name: HTTPS-console and click "Set". 12. In the same rule, left-click in the "Action" field and click "Set". 13. Select the action "Allow Read/Write Access" and click "Set". 14. Repeat these steps to add various read-only or read-write groups for the HTTPS-console. 15. For the SSH-Console click "Add rule". 16. Inside of the rule, under "Source", left-click and select "Set". 17. Click "Add new Object". 18. Select "Group". 19. Under the "Group" field type in the full LDAPS full Distinguished Name (DN) for the admin group. e.g., CN=broadcom.admins.gsg,OU=BROADCOM,OU=Vendors,DC=dodDoW,DC=local 20. Under the "Authentication Realm", select the "LDAPS" realm; do not select the CAC certificate realm. 21. Click "Apply", then click "Set". 22. In the same rule, left-click in the "Service" field and click "Set". 23. Select "Service Name: SSH-console" and click "Set". 24. In the same rule, left-click in the "Action" field and click "Set". 25. Select the action "Allow Read/Write Access" and click "Set". 26. Repeat these steps to add various read-only or read-write groups for the SSH-console. 27. Click "Apply Policy" and ensure it loaded correctly. In the Edge SWG Web UI, navigate to the Configuration tab. 1. Under "Services", click "Management Services". 2. Click to edit the HTTPS-Console. 3. Ensure the keyring and CCL are those created in SYME-ND-000800. 4. Check "Verify Client" and select "Apply then save". 5. Close, then re-open the browser, then go to the URL associated with the login banner, https://proxy.dodDoW.mil:444. 6. Once the login banner is presented, click "Accept". 7. Select the CAC certificate. Provide the PIN. The user must be authenticated. Note: If it is unsuccessful, it is possible the LDAPS credential is not valid, the group does not match, or there is an OCSP revocation issue.

V-279251 in V1R3

Fix text

1. In the Edge SWG Web UI, navigate to the Administration tab. 2. Select the "Logging" and "Event Logging" areas. Note: This section sets the "SSL Keyring", which is needed for the "SSL Device Profile". Once the SSL Device Profile has been created properly, scroll down to the "Syslog Loghosts". 3. Click "Add loghost". 4. Click "TLS". 5. Enter the fully qualified domain name of the log server. 6. Enter the port, by default TLS syslog is 6514. 7. Under "SSL Device Profile" select the profile associated with the DODDoW PKI certificate and key created previously. 8. Click "Add". 9. Scroll down to "Default Notifications", ensure "Syslog" is set to "Enabled", and the "Level" is "All Messages". 10. On the syslog server, ensure the server is receiving the messages and troubleshoot any TLS-related communications issues.

V-279252 in V1R3

Title

The Edge SWG must display the Standard Mandatory DODoW Notice and Consent Banner before granting access to the device.

Fix text

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "serial-console". 4. Enter "inline pre-authentication-terms ~", then press enter. 5. Paste the exact required text below along with the EOF marker of ~: 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 communication and work product are private and confidential. See User Agreement for details. ~ 6. Enter "exit". 7. Enter "ssh-console". 8. Enter "inline pre-authentication-terms ~". 9. Paste the exact DODDoW required text below along with the EOF marker of ~: 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 communication and work product are private and confidential. See User Agreement for details. ~ Note: To add the required login banner for the HTTPS-console, the complete required fix detailed in SYME-ND-000190 must first be implemented.

Discussion

Display of the DODDoW-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users. Satisfies: SRG-APP-000068-NDM-000215, SRG-APP-000069-NDM-000216

V-279254 in V1R3

Fix text

1. In the Edge SWG Web UI, navigate to the Administration tab. 2. Select the "Logging" and "Event Logging" areas. Note: This section sets the "SSL Keyring", which is needed for the "SSL Device Profile". 3. Once the SSL Device Profile has been created properly, scroll down to the "Syslog Loghosts". 4. Click "Add loghost". 5. Click "TLS". 6. Enter the fully qualified domain name of the log server. 7. Enter the port, by default TLS syslog is 6514. 8. Under "SSL Device Profile", select the profile associated with the DODDoW PKI certificate and key created previously. 9. Click "Add". 10. Scroll down to "Default Notifications". Ensure that "Syslog" is set to "Enabled" and the "Level" is "All Messages". 11. On the syslog server, ensure the server is receiving the messages and troubleshoot any TLS-related communications issues.

V-279255 in V1R3

Title

The Edge SWG must enforce a 6180-day password lifetime.

Check text

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "security local-user-list edit local". 4. Enter "view". If the "Password expiration:" and "Max password age:" do not state "60180 days", this is a finding.

Fix text

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "security local-user-list edit local". 4. Enter "max-password-age 6180".

V-279259 in V1R3

Discussion

DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of network devices to mitigate the impact of DoS attacks that have occurred or are ongoing on device availability. For each network device, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or restricting the number of sessions the device opens at one time). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks. The security safeguards cannot be defined at the DODDoW level because they vary according to the capabilities of the individual network devices and the security controls applied on the adjacent networks (for example, firewalls performing packet filtering to block DoS attacks).

V-279271 in V1R3

Check text

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Issue the command "ssl", then issue the command "view keyring". 4. Find the keyrings that state: "FIPS compliant: yes". 1. Log in to the Edge SWG Web UI. 2. Navigate to the Configuration tab. 3. Click the SSL, and then keyrings section. If the keyring in use was not FIPS compliant from step #3 above, this is a finding. Click the keyring in use. If the certificate in the keyring was not issued by a DODDoW certificate authority this is a finding.

Fix text

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "ssl". 4. Enter "create fips keyring show fips-keyring 2048". The "fips-keyring" name can be changed to whatever the site wants to use. 5. Enter "create signing-request fips-keyring". 6. Enter "view signing-request fips-keyring". Copy the signing request PEM data and provide it to the CA for certificate issuance. 7. Once the DODDoW CA issues/signs the certificate for the keyring type "inline certificate fips-keyring ~", paste the raw certificate data into a text editor, then press enter. Ensure the "~" is present at the end of the inserted text. 8. For each LDAP server, CA certificate, and CAC authentication CA certificate, issue the following command: "inline fips ca-certificate DODCA1 ~". Ensure the ~ is entered at the end of the certificate data paste. Note: DODCA1 is used as an example. 9. Repeat the "inline fips ca-certificate" command for all CA certificates in use for LDAPS and CAC authentication. 10. Create a new FIPS-enabled CCL by entering: "create fips ccl fips-ccl". The fips-ccl name can be changed to whatever the site wants to use. 11. Enter "edit ccl fips-ccl". 12. Enter "add", then enter all the CAs added in all previous steps. 13. Create an SSL device profile by entering: "create fips ssl-device-profile fips-profile fips-keyring". The "fips-profile" name can be changed to whatever the site wants to use.

V-279273 in V1R3