Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
SRG-NET-000077-NDM-000051 | SRG-NET-000077-NDM-000051 | SRG-NET-000077-NDM-000051_rule | Low |
Description |
---|
It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured network device. If the originator of the log record is not recorded, it will be difficult to establish and correlate the series of events leading up to an outage or attack. |
STIG | Date |
---|---|
Network Device Management Security Requirements Guide | 2013-07-30 |
Check Text ( C-SRG-NET-000077-NDM-000051_chk ) |
---|
Examine the audit log configuration on the network device or view several alert records on the organization's central audit log server. Verify the entries sent to the audit log include sufficient information to ascertain the source of the events (e.g., IP address, session or packet ID). If the audit log event records do not include sufficient information to ascertain the source of the events, this is a finding. |
Fix Text (F-SRG-NET-000077-NDM-000051_fix) |
---|
Configure the network device to ensure entries sent to the audit log include sufficient information to ascertain the source of each audit event (e.g., IP address, session or packet ID). |