Skip to main content
Cisco Meraki Documentation

Cisco Secure Connect - Remote Access Start


Cisco Secure Connect enables remote users to access private applications from anywhere through Secure Connect fabric using Cisco Secure Client (formerly the Cisco AnyConnect client). Identity-based access control is available using SAML authentication through customer’s IdP (Identity Provider) solution. Endpoint Compliance, also known as Endpoint Posture, is also evaluated when connecting to remote access.

2 Remote Access Traffic Steering.png







DNS server IP address(es) DNS Servers is used to resolve private application host-names.
Default domain(s) Default domain is used to complete any unqualified host names input by users when accessing private applications through the secure tunnel.
Client assigned IP address pools

Each region specified must have a minimum of two locations configured with a private address pool.

(Notice: We recommend to use contiguous private address pools for an easy route summarization and rule updates.)

These pools cannot be overlapping with any existing addresses/subnets used in customer internal network.

At least one region is required.

For a complete list of supported regions and data center locations please check here.

Next Step - Network and Policy Setup

After completing the Remote Access setup, the rest of tasks can be complete depending on your situation. 

5-3 Checklist- expanded.png