The Cisco ASA remote access VPN server must be configured to produce log records containing information to establish the outcome of the events.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-239974	CASA-VN-000530	SV-239974r666328_rule		Medium

Description

Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the network. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the network after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.

STIG	Date
Cisco ASA VPN Security Technical Implementation Guide	2021-08-16

Details

Check Text ( C-43207r666326_chk )

Verify the ASA generates log records containing information to establish the outcome of the events as shown in the example below. logging class vpn trap notifications logging class vpnc trap notifications logging class vpnfo trap notifications logging class webfo trap notifications logging class webvpn trap notifications logging class svc trap notifications Note: A logging list can be used as an alternative to using class. If the ASA does not generate log records containing information to establish the source of the events, this is a finding.

Fix Text (F-43166r666327_fix)

Configure the ASA to generate log entries containing information to establish the outcome of the events as shown in the example below. ciscoasa(config)# logging class vpn trap notifications ciscoasa(config)# logging class vpnc trap notifications ciscoasa(config)# logging class vpnfo trap notifications ciscoasa(config)# logging class webvpn trap notifications ciscoasa(config)# logging class webfo trap notifications ciscoasa(config)# logging class svc trap notifications ciscoasa(config)# end