STIGQter: STIG Summary: Riverbed SteelHead CX v8 NDM Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 25 Oct 2019:

Riverbed Optimization System (RiOS) must automatically generate a log event for account removal actions.

DISA Rule

SV-77335r1_rule

Vulnerability Number

V-62845

Group Title

SRG-APP-000029-NDM-000211

Rule Version

RICX-DM-000010

Severity

CAT III

CCI(s)

• CCI-001405 - The information system automatically audits account removal actions.

Weight

10

Fix Recommendation

Configure RiOS to generate a log event for account disabling actions.

Navigate to the device Management Console, then
Navigate to:
Configure >> System Settings >> Logging

Under Configuration, set minimum severity to Info
Click "Save"

Under Configuration, set minimum severity to Info.

Check Contents

Verify that RiOS is configured to generate a log event for account creation events.

Create an account
To disable an account
Navigate to the device Management Console, then
Navigate to:
Configure >> Security >> User >> Permissions
Select the account to be removed
Click Remove Selected Account

Navigate to the device Management Console, then
Navigate to:
Reports >> Diagnostics >> System Logs
Enter the account name into the filter and click "Go"
Delete the account that was created.

If no event record for the user removal action exists in the event log, this is a finding.

Vulnerability Number

V-62845

Documentable

False

Rule Version

RICX-DM-000010

Severity Override Guidance

Verify that RiOS is configured to generate a log event for account creation events.

Create an account
To disable an account
Navigate to the device Management Console, then
Navigate to:
Configure >> Security >> User >> Permissions
Select the account to be removed
Click Remove Selected Account

Navigate to the device Management Console, then
Navigate to:
Reports >> Diagnostics >> System Logs
Enter the account name into the filter and click "Go"
Delete the account that was created.

If no event record for the user removal action exists in the event log, this is a finding.

Check Content Reference

M

Target Key

2931

Comments