STIGQter STIGQter: STIG Summary: Cisco ISE NDM Security Technical Implementation Guide Version: 2 Release: 4 Benchmark Date: 01 Jul 2026:

The Cisco ISE must initiate session auditing upon startup.

DISA Rule

SV-242662r960888_rule

Vulnerability Number

V-242662

Group Title

SRG-APP-000092-NDM-000224

Rule Version

CSCO-NM-000650

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Enable logging categories for Cisco ISE to send auditable events to the syslog target.

From the Web Admin portal:
1. Choose Administration >> System >> Logging >> Logging Categories.
2. Click the radio button next to the Administrative and Operational Audit logging category and then click "Edit".
3. Choose INFO from the Log Severity Level drop-down list.
4. In the Targets field, move the syslog target name that is being used to the Selected box.
5. Repeat the above steps to enable the AAA Audit logging category and other logging categorized desired. However, note that for some logging categories, the default log severity level and cannot be changed.
5. Click "Save".

Check Contents

Verify logging is initiated upon system startup. Since the production may not be able to be manually started to observe this, review the logging categories setup.

From the Web Admin portal:
1. Choose Administration >> System >> Logging >> Logging Categories.
2. Verify the Administrative and Operational Audit is configured for the INFO log severity level.
3. Verify that logging categories have been configured and have been set to the syslog target.

If logging categories are not configured to send to the central syslog server, this is a finding.

Vulnerability Number

V-242662

Documentable

False

Rule Version

CSCO-NM-000650

Severity Override Guidance

Verify logging is initiated upon system startup. Since the production may not be able to be manually started to observe this, review the logging categories setup.

From the Web Admin portal:
1. Choose Administration >> System >> Logging >> Logging Categories.
2. Verify the Administrative and Operational Audit is configured for the INFO log severity level.
3. Verify that logging categories have been configured and have been set to the syslog target.

If logging categories are not configured to send to the central syslog server, this is a finding.

Check Content Reference

M

Target Key

5384