Contents

Introduction

Prerequisites

Requirements and Limitations

Components Used

Background Information

Configure

Step 1. Create a Service Access Object

Step 2. Apply the Service Object configuration in RAVPN.

Verify

Syslogs and Monitoring

Monitor Blocked Connections

Monitor Allowed Connections

Troubleshoot

Related Information

Introduction

This document describes the process to permit or deny RAVPN connections based on specific geolocations on Secure Firewall Threat Defense (FTD).

Prerequisites

Requirements and Limitations

Cisco recommends that you have knowledge of these topics:

- Secure Firewall Management Center (FMC)

- Remote Access VPN (RAVPN)

- Basic Geolocation configuration

The current requirements and limitations for Geolocation-based policies are:

- Supported only on FTD version 7.7.0+, managed by FMC version 7.7.0+.

- Not supported on FTD managed by Secure Firewall Device Manager (FDM).

- Not supported in cluster mode

- Geolocation-based unclassified IP addresses are not categorized by geographic origin. For these, the FMC enforces the default service access policy action.

- Geolocation-based service access policies do not apply to WebLaunch pages, allowing you to download the Secure Client without restrictions.

Components Used

The information in this document is based on these software versions:

- Secure Firewall version 7.7.0

- Secure Firewall Management Center version 7.7.0

Full details about this feature can be found in the Manage VPN Access of Remote Users Based on Geolocation section within the Cisco Secure Firewall Management Center 7.7 Device Configuration Guide.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Background Information

Geolocation-based access policies offer significant value in network security today, allowing traffic to be blocked based on its geographical origin. Traditionally, organizations could define traffic access policies for general network traffic that passes through the firewall. Now, with the introduction of this feature, it is possible to apply geolocation-based access control for Remote Access VPN session requests.

This feature provides the next benefits:

- Geolocation-Based Rules: Customers can create rules to permit or deny RAVPN requests based on specific geolocations, such as countries or continents. This allows for precise control over which geographical locations can initiate VPN sessions.

- Pre-Authentication Blocking: Sessions identified by these rules for a deny action are blocked before authentication, and these attempts are properly logged for security purposes. This preemptive action helps in mitigating unauthorized access attempts.

- Compliance and Security: This feature aids in ensuring adherence to local organizational and governance policies, while also reducing the attack surface of the VPN server.

Given that VPN servers have public IP addresses accessible via the internet, the introduction of geolocation-based rules enables organizations to effectively restrict user requests from specific geolocations, thereby reducing vulnerability to brute force attacks.

Configure

Step 1. Create a Service Access Object

1. Log in to the Secure Firewall Management Center.

2. Navigate to Objects > Object Management > Access List > Service Access and click Add Service Access Object.

3. Define the rule name, then click Add Rule.

4. Configure the Service Access Rule:

- Select the action of the rule: Allow or Deny.

- From Available Countries, select countries, continents, or user-defined geolocation objects and move them to the Selected Geolocation list.

- Click Add to create the rule.

Note: In a service access object, a geolocation object (country, continent, or custom geolocation) can only be used in one rule.

Note: Ensure to configure the service access rules in the correct order, as these rules cannot be reordered.

5. Choose the Default Action: either Allow All Countries or Deny All Countries. This action applies to connections that do not match any of the configured Service Access Rules.

6. Click Save.

Step 2. Apply the Service Object configuration in RAVPN.

1. Navigate to the RAVPN configuration in Devices > Remote Access > RAVPN configuration object > Access interface.

2. In the Service Access Control section, select the Service Access Object you created earlier.

3. The Service Access object you selected now displays the rules summary and the default action. Ensure this is correct.

4. Finally, Save the changes and Deploy the configuration.

Verify

Once the configuration is saved, the rules appear in the Service Access Control section, allowing you to validate which groups and countries are blocked or allowed.

Run the show running-config service-access command to ensure the service access rules are available from the FTD CLI.

firepower# show running-config service-access

service-access deny ra-ssl-client geolocation FMC_GEOLOCATION_146028889448_536980902

service-access permit ra-ssl-client geolocation any

firepower# show running-config object-group idFMC_GEOLOCATION_146028889448_536980902

object-group geolocation FMC_GEOLOCATION_146028889448_536980902

location "Country X"

location "Country Y"

Syslogs and Monitoring

Secure Firewall introduces new syslog IDs to capture events related to RAVPN connections blocked by geolocation-based policies:

- 761031: Indicates when an IKEv2 connection is denied by a geolocation-based policy. This syslog is part of the existing VPN logging class.

%FTD-6-751031: Denied IKEv2 remote access session for faddr <client_ip> laddr <device_ip> by a geo-based rule (geo=<country_name>, id=<country_code>)

- 751031: Indicates when an SSL connection is denied by a geolocation-based policy. This syslog is part of the existing WebVPN logging class.

%FTD-6-716166: Denied SSL remote access session for faddr <client_ip> by a geo-based rule (geo=<country_name>, id=<country_code>)

Note: The default severity level for these new syslogs is informational when enabled from the respective logging classes. However, you can enable these syslog IDs individually and customize their severity.

Monitor Blocked Connections

To validate blocked connections, navigate to Devices > Troubleshoot > Troubleshooting Logs. Here, logs related to blocked connections are displayed, including information about the rules affecting the connection and the type of session.

Note: Syslog must be configured to collect this information in the Troubleshooting Logs.

Monitor Allowed Connections

The allowed sessions are monitored in Overview > Remote Access VPN dashboard, where session information is displayed, including the country of origin.

Note: Only connections from allowed countries and users who are permitted to connect, are displayed in this dashboard. Connections that are rejected are not displayed in this dashboard.

Troubleshoot

For troubleshooting purposes, follow these steps:

1. Verify that the rules are correctly configured in the Service Access object.

2. Check if a deny syslog appears in the Troubleshooting Logs section when an allowed geolocation requests a session.

3. Ensure that the configuration shown in the FMC matches what is in the FTD CLI.

4. Use the next commands to gather more details that are useful for troubleshooting purposes:

- debug geolocation <1-255>

- show service-access

- show service-access detail

- show service-access interface

- show service-access location

- show service-access service

- show geodb ipv4 location <Country> detail

- show geodb counters

- show geodb ipv4 [lookup <IP address>]

- show geodb ipv6

Related Information

- For additional assistance, please contact TAC. A valid support contract is required:Cisco Worldwide Support Contacts.

- You can also visit the Cisco VPN Communityhere.