The Juniper router must be configured to produce audit records containing information to establish where the events occurred.
An XCCDF Rule
Description
<VulnDiscussion>Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. To compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as router components, modules, device identifiers, node names, and functionality. Associating information about where the event occurred within the network provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-253996r844021_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Configure the router to record the interface in the log record for packets being dropped.
Example firewall filter with logging enabled:
set firewall family inet filter <filter name> term 1 from <match conditions>
set firewall family inet filter <filter name> term 1 then log
set firewall family inet filter <filter name> term 1 then syslog <<< Must be enabled for all discarding terms