Cisco 300-730 Practice Test - Questions Answers, Page 5

Reference: https://tools.cisco.com/security/center/resources/next_generation_cryptography

Reference: https://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curvecryptography/

Reference: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_getvpn/configuration/xe-3s/sec-get- vpn-xe-3s-book/sec-get-vpn.html

https://www.cisco.com/c/en/us/support/docs/security/dynamic-multipoint-vpn-dmvpn/111976-dmvpn-troubleshoot-00.html

The reason is that by default, the SSL VPN clients use split tunneling, which means they only send trafficdestined for the corporate network through the VPN tunnel, and use their local gateway for other

traffic, such as browsing the internet. This means that when they search for their IP address on abrowser, they will see their local IP address, not the IP address of the ASA.To change this behavior, you need to configure the Group Policy on the ASA to tunnel all networks,which means that all traffic from the SSL VPN clients will go through the VPN tunnel, regardless of thedestination. This way, when they search for their IP address on a browser, they will see the IP address ofthe ASA, which is 3.3.3.3.To configure tunnel all networks under Group Policy, you can use either ASDM or CLI.For example, usingASDM, you can follow these steps1:Choose Configuration > Remote Access VPN > Network (Client) Access > Group Policies.Select the group policy that you want to modify and click Edit.In the Edit Internal Group Policy window, choose Advanced > Split Tunneling.In the Policy drop-down list, choose Tunnel All Networks.Click OK and then Apply.Using CLI, you can enter these commands:ciscoasa(config)# group-policy <group_policy_name> attributes ciscoasa(config-group-policy)# split-tunnel-policy tunnelall

Reference: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_vpnips/configuration/zZArchive/IPsec_Virtual_Tunnel_Interface.html#GUID-EB8C433B-2394-42B9-997F-B40803E58A91