AOS, when used as a VPN Gateway, must authenticate all network-connected endpoint devices before establishing a connection.
An XCCDF Rule
Description
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of authentication claims may be made by services separate from the services acting on those decisions. In such situations, it is necessary to provide authentication decisions (as opposed to the actual authenticators) to the services that need to act on those decisions. This requirement applies to applications that connect either locally, remotely, or through a network to an endpoint device (including, but not limited to, workstations, printers, servers (outside a datacenter), VoIP Phones, and VTC codecs). Gateways and SOA applications are examples of where this requirement would apply. Device authentication is a solution enabling an organization to manage devices. It is an additional layer of authentication ensuring only specific preauthorized devices can access the system.
- ID
- SV-266988r1040893_rule
- Version
- ARBA-VN-001370
- Severity
- Medium
- References
- Updated
Remediation Templates
A Manual Procedure
Configure AOS using the web interface:
1. Navigate to Configuration >> Services >> VPN and expand "Site-to-Site".
2. Select the configured site-to-site VPN IPsec maps. Select the applicable Server certificate. Select the applicable trusted DOD root CA under "CA certificate:".
3. Click Submit >> Pending Changes >> Deploy Changes.
4. Navigate to Configuration >> Access Points >> Remote APs tab.