Remote access. With the onslaught of the pandemic, those two words have brought on a whole new meaning over the past two years.

Companies from all industries rushed to move into the remote access realm with varying degrees of success. To that end, the National Security Agency (NSA) and Cybersecurity and Infrastructure Security Agency (CISA) released and information sheet entitled “Selecting and Hardening Standards-based Remote Access VPN Solutions” to address the potential security risks associated with using Virtual Private Networks (VPNs).

Remote-access VPN servers allow off-site users to tunnel into protected networks, making these entry points vulnerable to exploitation by malicious cyber actors.

Exploitation of these devices can enable:

  1. Credential harvesting
  2. Remote code execution on the VPN device
  3. Cryptographic weakening of encrypted traffic sessions
  4. Hijacking of encrypted traffic sessions
  5. Arbitrary reads of sensitive data (e.g., configurations, credentials, keys) from the device

The information sheet helps organizations select standards-based (rather than proprietary) VPN solutions and provides hardening guidance to prevent compromise and respond to attacks.

Schneider Bold

VPN servers are entry points into protected networks, making them attractive targets. Multiple nation-state advanced persistent threat (APT) actors have weaponized common vulnerabilities and exposures (CVEs) to gain access to vulnerable VPN devices. Exploitation of these CVEs can enable a malicious actor to steal credentials, remotely execute code, weaken encrypted traffic’s cryptography, hijack encrypted traffic sessions, and read sensitive data from the device. If successful, these effects usually lead to further malicious access and could result in a large-scale compromise to the corporate network.

When choosing a remote access VPN, consider these recommendations:

  • Avoid selecting non-standard VPN solutions, including a class of products referred to as Secure Sockets Layer/Transport Layer Security (SSL/TLS) VPNs.
  • Carefully read vendor documentation to ensure potential products support IKE/IPsec VPNs.
  • Identify whether the product uses SSL/TLS in a proprietary or non-standards- based VPN protocol when unable to establish an IKE/IPsec VPN.
  • Ensure that potential products use FIPS-validated cryptographic modules and can be configured to use only approved cryptographic algorithms.
  • Check that a product supports strong authentication credentials and protocols and disables weak credentials and protocols by default.
  • Research and select a vendor with a proven track record of supporting products via regular software updates and quickly remediating known vulnerabilities.
  • Request and validate a product’s Software Bill of Materials (SBOM) so the risk of the underlying software components can be adjudicated.
  • Ensure the product has a robust method to validate the integrity of its own code and regularly perform code validation.
  • Ensure the product includes protections against intrusions, such as: Use of signed binaries or firmware images; A secure boot process that verifies boot code before it runs, and integrity validation of runtime processes and files
  • Understand the risk of not being able to inspect the product on your own. Some VPN vendors encrypt the devices in a manner that prevents timely incident response..
  • Review additional features of the prospective device against your organization’s risk appetite.

Click here to view the full information sheet.

Pin It on Pinterest

Share This