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

Symantec ProxySG must be configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.

DISA Rule

SV-104491r1_rule

Vulnerability Number

V-94661

Group Title

SRG-APP-000065-NDM-000214

Rule Version

SYMP-NM-000050

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

The lockout policy may be configured for both SSH and Web Management Console sessions.

1. SSH into the ProxySG console, type "enable", press "Enter".
2. Enter the appropriate password, type "config", press "Enter".
3. Type "security local-user-list edit local_user_database", press "Enter".
4. Type "lockout-duration 900", type "max-failed-attempts 3", press "Enter".

Check Contents

Verify the lockout policy is configured.

1. SSH into the ProxySG console, type "enable", press "Enter".
2. Enter the appropriate password, type "config", press "Enter".
3. Type "show security local-user-list", press "Enter".

This should return a value of "3" for the "Max failed attempts" and "900" for the value of both the "lockout duration" and "reset interval" fields.

If Symantec ProxySG is not configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period, this is a finding.

Vulnerability Number

V-94661

Documentable

False

Rule Version

SYMP-NM-000050

Severity Override Guidance

Verify the lockout policy is configured.

1. SSH into the ProxySG console, type "enable", press "Enter".
2. Enter the appropriate password, type "config", press "Enter".
3. Type "show security local-user-list", press "Enter".

This should return a value of "3" for the "Max failed attempts" and "900" for the value of both the "lockout duration" and "reset interval" fields.

If Symantec ProxySG is not configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period, this is a finding.

Check Content Reference

M

Target Key

3517

Comments