nerdexam
Cisco

300-730 · Question #159

Refer to the exhibit. A network administrator is setting up Cisco AnyConnect on an ASA headend. When users attempt to connect to the VPN, they are presented with this message. The administrator has…

The correct answer is A. Trust the issuing CA for the ASA identity certificate on the user's PC. B. Enroll and import an SSL certificate with the CN value example.cisco.com on the ASA. The AnyConnect warning about an untrusted server certificate with a name mismatch requires both a certificate whose CN matches the server FQDN and the issuing CA being trusted on the client machine.

Troubleshooting VPNs

Question

Refer to the exhibit. A network administrator is setting up Cisco AnyConnect on an ASA headend. When users attempt to connect to the VPN, they are presented with this message. The administrator has replaced the ASA's self-signed certificate with a certificate enrolled with the external CA and has confirmed that the certificate is not revoked. Which two tasks will the administrator need to do to prevent users from seeing this message? (Choose two.) [Exhibit: Cisco AnyConnect Secure Mobility Client window showing "Security Warning: Untrusted Server Certificate!". Details include "AnyConnect cannot verify server: example.cisco.com", "Certificate does not match the server name", "Certificate is from an untrusted source". Buttons: Connect Anyway, Cancel Connection.]

Options

  • ATrust the issuing CA for the ASA identity certificate on the user's PC.
  • BEnroll and import an SSL certificate with the CN value example.cisco.com on the ASA.
  • CAdd the CN example.cisco.com to the AnyConnect XML certificate matching section.
  • DEnable certificate authentication under the connection profile.
  • EAdd example.cisco.com to the server name list within the AnyConnect Local Policy.

How the community answered

(25 responses)
  • A
    72% (18)
  • C
    4% (1)
  • D
    16% (4)
  • E
    8% (2)

Why each option

The AnyConnect warning about an untrusted server certificate with a name mismatch requires both a certificate whose CN matches the server FQDN and the issuing CA being trusted on the client machine.

ATrust the issuing CA for the ASA identity certificate on the user's PC.Correct

Trusting the issuing CA on the user's PC resolves the 'Certificate is from an untrusted source' warning because TLS chain validation requires the CA that signed the ASA identity certificate to be present in the client OS or browser trust store.

BEnroll and import an SSL certificate with the CN value example.cisco.com on the ASA.Correct

Enrolling an SSL certificate with CN value example.cisco.com on the ASA resolves the 'Certificate does not match the server name' error because TLS requires the CN or Subject Alternative Name in the server certificate to match the hostname the client is connecting to.

CAdd the CN example.cisco.com to the AnyConnect XML certificate matching section.

The AnyConnect XML certificate matching section is used to match client certificates for certificate-based user authentication, not to control how the client evaluates the server's identity certificate.

DEnable certificate authentication under the connection profile.

Enabling certificate authentication under the connection profile configures the method by which users authenticate to the VPN and has no effect on how the client validates the server's certificate trust chain.

EAdd example.cisco.com to the server name list within the AnyConnect Local Policy.

Adding example.cisco.com to the AnyConnect Local Policy server name list can suppress the warning locally on a single endpoint but does not fix the underlying certificate trust or CN mismatch for all users.

Concept tested: AnyConnect SSL certificate trust chain and CN name validation

Source: https://www.cisco.com/c/en/us/support/docs/security/anyconnect-secure-mobility-client/116026-configure-anyconnect-00.html

Topics

#AnyConnect#certificate trust#CA#SSL VPN

Community Discussion

No community discussion yet for this question.

Full 300-730 Practice