About Client-Based Connections
- The Cisco Secure Client is installed on the end-user device.
- Users can access resources using any protocol.
- Users access using the internal resource address you specify in the Private Resource.
- The client-based posture profile offers more options for controlling endpoint (device) requirements than the browser-based posture profile offers.
- You can block access to specified subdomains when the resource address for client-based connections is configured as a wildcard FQDN. For more information, see Using Wildcards to Configure Traffic Steering for Private Destinations.
- If traffic is blocked, the user sees a Block page if all requirements are met. For more information, see Block pages for Private Resources.