Configuring Remote Access VPN on Firepower

-

In this article we are going to take a look at how to configure remote access VPN's on Firepower devices.


This demonstration is based on the following lab environment:
  • Cisco Virtual Firepower Management Center
  • Cisco Virtual Firepower Threat Defense
  • Cisco ISE 2.6
  • Windows host with AnyConnect VPN
  • Windows Server 2019 (CA Server)

All Firepower devices are running version 6.5

Note: ISE is used for authentication and authorization in the following lab however the configuration elements of ISE are out of scope for this demonstration.

Generate a CSR for Remote Access VPN's


Those accessing your network remotely need to trust the service you're running. Without the correct trust users could face issues connecting via VPN.

With access to the FMC navigate to Objects > Object Management > PKI > Cert Enrollment

Assuming you are opting for manual enrollment, select 'Manual' in Enrollment Type and copy the CA Certificate BASE-64 into the field.

Now select the 'Certificate Parameters' tab and select 'Custom FQDN'. We will use a separate FQDN for remote access VPN services. It is also worth making sure the FQDN is added to your internal DNS.

Continue to populate the remaining fields with the relevant information necessary to your organization.



On the 'Key' tab give the RSA key a name and specify the key length. Decide whether you would like to enable advanced options and certificate revocation checks. For the purpose of this demonstration, we will not enable advanced key features or use revocation checks.



Once done, click 'Save'.

Navigate to Devices > Certificates and click 'Add' to add a new certificate. When the pop-up box appears, select the relevant FTD appliance followed by the cert enrollment that was previously created.

Click 'Ok' when done.


Once configured, click 'ID' to generate the CSR. Copy the CSR to the CA and have it signed.

Once the certificate has been signed by your CA, download the newly signed certificate and import it to the FMC by clicking 'Import'.



Configure RADIUS Servers


Navigate to Objects > RADIUS Server Group and add a new RADIUS server group.



Configure VPN Address Pools


Navigate to Objects > Object Management > Address Pools and create your VPN address pools.



You have the option to modify the AnyConnect profile and add the new VPN FQDN if you wish. For the purpose of this demonstration we won't be going through those steps.

Upload Cisco AnyConnect Images


Upload the relevant AnyConnect images to the FMC by navigating to Objects > Object Management > VPN > AnyConnect File.



Configuring the Remote Access VPN


Navigate to Devices > VPN > Remote Access and click 'Add'.


A wizard will appear where you will run through 5 steps.

Starting with Step 1, populate the fields with the relevant settings required for your deployment. Ensure that you select the correct managed device based on where the VPN is to be deployed and select the the VPN protocols you wish to use. For the purpose of this lab, the default VPN protocol settings will be applied.

Once you are happy with the settings, proceed to step 2.

Step 2 focuses on configuration of connection profiles.

Proceed to populate the AAA fields with the objects created earlier followed by the selection of the VPN Pool you created earlier in this article.

Before moving along to step 3, you may want to edit the default group policy settings or create a new one. For the purpose of this lab, the default group policy has been modified to include split-tunneling options and DNS Servers.


Proceeding to Step 3, you will be required to select the AnyConnect images you want to be enabled.

If no images exist you will be required to upload at least one before proceeding to Step 4.



In step 4 you are required to select the VPN termination interface as well as the certificate that should be used. You can optionally choose to bypass the ACP applied to the managed device for VPN connections. In this demonstration, we will bypass the ACP and applied access controls once users have been authorized by ISE.


Once you are happy with the settings applied in Step 4, the configuration for Remote Access VPN is complete. Proceed to Step 5 and verify the configuration settings that will be applied.


Return to Devices > VPN > Remote Access and click on the 'Access Interfaces' tab. Verify the interface and port settings.

Additional Configuration


Depending on your setup, you may need to configure additional settings such as NAT. In the lab used in this demonstration NAT is enabled on the Firepower device so the following NAT rule is to be configured.

Source interface: Any
Destination interface: Any
Original Source: Any (or specific public IPs)
Original Destination: Any
Translated Source: VPN Pool
Translated Destination: VPN Pool
No proxy-arp: enabled


If using ISE to provide policy decisions, ensure that the managed device is configured as a NAD in ISE and ensure that your policies are configured correctly.

In this demonstration, ISE is used for Authentication and Authorization of VPN clients.



You should now be able to connect to to your managed device using your AnyConnect client.

Accompanying Video Demonstration




















Kelvin Charles - Network and Cyber Security Professional.

Popular Posts

Capturing EAPOL and RADIUS Using Wireshark

-
Image
In this article we are going to take a look at how to capture Extensible Authentication Protocol Over LAN (EAPOL) and Remote Authentication Dial-In User Service (RADIUS) packets using Wireshark. This article can be useful for troubleshooting 802.1x within your environment and can also be used for learning purposes. The following topology has been used to gather the required output for this article. Note: This article will only cover the switch configurations that are required to gather EAPOL and RADIUS configuration. Overview of the Topology The supplicant is configured to perform 802.1x using EAP-TLS as the authentication method The user certificate on the supplicant will be used for authentication The supplicant has Wireshark installed Cisco ISE is used for authentication and authorisation The supplicant is assigned to VLAN 10 upon authentication and all other endpoint ports are assigned to VLAN 99 Sniffer device is running Wireshark in order to capture RADIUS flows via SPAN 802.1x
Read more

Configuring Cisco Smart License Software

-
In this article, I would like to demonstrate how to configure Cisco Smart Licensing on the virtual Cisco Adaptive Security Appliance (ASAv). This post assumes that readers already have access to there own Smart Account and would like to know the process of applying licenses. Step 1: Generate ID Token Sign into your Cisco Software Portal: software.cisco.com and navigate to “Smart Software Licensing” You will now need to create an ID token for your device, this is required for communication between the device and the licensing authority. Follow the steps below to create a new token. Click Inventory >>> General >>> New Token and select your preferred options and enter a description for your token. Once you are happy with your token settings click Create Token . You should now have a token created which can be copied over to the device you wish to license. All commands and output from this point will be related to the ASA so please seek out further advice if you wish
Read more

Cisco :: FXOS Authentication Using TACACS

-
In this article, I will describe how to enable authentication and authorization for Firepower eXtensible Operating System (FXOS) devices. The use case presented in this document illustrates how Cisco Identity Services Engine (ISE) can be utilised with attribute-value pairs (AV-Pairs) to authenticate and authorize users accessing the Firepower Chassis Manager (FCM) or FXOS platforms via TACACS+. At the time of writing this post, I found that limited documentation existed and of that documentation that did exist, the examples given weren’t as straightforward. In an effort to make this process easier for my colleagues and customers to understand I have put together the following instructions based on a previous use case given to me. Extracts of this document have been taken from a wider document I am currently creating. I will update this article with the complete document when it has been finalized. Requirements A ‘Device Administration’ license is required in order to use TACACS+ with
Read more

Kali Linux :: CAM Table Overflow Attack Demonstration

-
Image
As part of my on-going studying for the CCNA Security 210 – 260 certification I have been exploring different types of network attacks, one of which is CAM table overflow attacks. In this article I would like to share what I have learnt and provide a demonstration of the attack carried out in a lab environment. To understand my demonstration, you first need to understand how a CAM table overflow attack works and what happens as a result of the attack.   Switches build Content Addressable Memory (CAM) tables based on mac-addresses and port numbers. When a switch receives a frame it checks the table to see if the source mac-address is already known, if the source mac-address is unknown the switch will add the mac-address to the table along with the port number. The switch then checks the destination layer two frame and if no entry exists the switch broadcasts the frame out of all ports except the port in which the frame was received. Presuming the destination mac-address wants to respond
Read more