STIGQter STIGQter: STIG Summary: Symantec ProxySG NDM Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 24 Jan 2020:

The Symantec ProxySG Web Management Console and SSH sessions must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications.

DISA Rule

SV-104539r1_rule

Vulnerability Number

V-94709

Group Title

SRG-APP-000412-NDM-000331

Rule Version

SYMP-NM-000290

Severity

CAT I

CCI(s)

Weight

10

Fix Recommendation

Configure the Symantec ProxySG to use only AES ciphers for nonlocal maintenance and diagnostic communications.

1. Log on to the CLI via SSH.
2. Type "enable", enter the enable password.
3. Type "configure terminal" and press "Enter".
4. Type "management-services" and press "Enter", type "edit HTTPS-Console" and press "Enter".
5. Type "view" to display the list of configured cipher suites.
6. Type "attribute cipher-suite" followed by a space-delimited list of only cipher suites from step 5 containing AES and press "Enter".

Check Contents

Verify only AES ciphers are used for nonlocal maintenance and diagnostic communications.

1. Log on to the CLI via SSH.
2. Type "enable", enter the enable password.
3. Type "configure terminal", press "Enter".
4. Type "show management services" and confirm that the Cipher Suite parameter contains only ciphers that use AES.

If Web Management Console and SSH sessions does not implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, this is a finding.

Vulnerability Number

V-94709

Documentable

False

Rule Version

SYMP-NM-000290

Severity Override Guidance

Verify only AES ciphers are used for nonlocal maintenance and diagnostic communications.

1. Log on to the CLI via SSH.
2. Type "enable", enter the enable password.
3. Type "configure terminal", press "Enter".
4. Type "show management services" and confirm that the Cipher Suite parameter contains only ciphers that use AES.

If Web Management Console and SSH sessions does not implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, this is a finding.

Check Content Reference

M

Target Key

3517

Comments