How to Generate Certificate Signing Request (CSR) in Cisco ASA 5510


This document uses an ASA 5510 that runs software version 8.0(2) and ASDM version 6.0(2) and provides instructions for generating a Certificate Signing Request (CSR) for Cisco ASA 5510. If you are unable to use these instructions for your server, RapidSSL recommends that you contact Cisco.

NOTE: To generate a CSR, you will need to create a key pair for your server. These two items are a digital certificate key pair and cannot be separated. If you lose your public/private key file or your password and generate a new one, your SSL Certificate will no longer match.

Step 1:  Generate a key pair

1.    Within ASDM, click Configuration > Device Management

2.    Click Certificate Management > Identity Certificates > Add > Add a new identity certificate

3.    For the Key Pair, click New > Enter new key pair name

4.    Enter a unique key pair name for the certificate

5.    Select the key size as 2048

6.    To complete the generation of the key pair, click Generate Now

Step 2: Generate a certificate signing request (CSR) file

1.    To enter certificate information, click Select

2.    From the drop-down list, select the following attributes > enter value > click Add

3.    The following fields are required: 

Country Name (C): Use the two-letter code without punctuation for country, for example: US or CA.

State or Province (S): Spell out the state completely; do not abbreviate the state or province name, for example: California.

Locality or City (L): The Locality field is the city or town name, for example: Berkeley.

Organization (O): If your company or department has an &, @, or any other symbol using the shift key in its name, you must spell out the symbol or omit it to enroll, for example: XY & Z Corporation would be XYZ Corportation or XY and Z Corportation.

Organizational Unit (OU): This field is the name of the department or organization unit making the request.

Common Name (CN): The Common Name is the Host + Domain Name. 

NOTE: RapidSSL certificates can only be used on Web servers using the Common Name specified during enrollment. For example, a certificate for the domain "" will receive a warning if accessing a site named or "", because "" and "" are different from "". 

4.    Once the appropriate values are added, click OK > Advanced

5.    In the FQDN field, enter the FQDN that will be used to access the device from the Internet: 

       NOTE - If enrolling for a Subject Alternative Name certificate leave this field blank.

6.    Click OK >  Add Certificate > Browse

7.    Choose a location where to save the request file

8.    Verify your CSR

9.    Proceed with Enrolment.

       For more information, refer to Cisco Support




WarungSSL has made efforts to ensure the accuracy and completeness of the information in this document. However, WarungSSL makes no warranties of any kind (whether express, implied or statutory) with respect to the information contained herein. WarungSSL assumes no liability to any party for any loss or damage (whether direct or indirect) caused by any errors, omissions, or statements of any kind contained in this document.

Further, WarungSSL assumes no liability arising from the application or use of the product or service described herein and specifically disclaims any representation that the products or services described herein do not infringe upon any existing or future intellectual property rights. Nothing herein grants the reader any license to make, use, or sell equipment or products constructed in accordance with this document. Finally, all rights and privileges related to any intellectual property right described herein are vested in the patent, trademark, or service mark owner, and no other person may exercise such rights without express permission, authority, or license secured from the patent, trademark, or service mark owner. Geotrust reserves the right to make changes to any information herein without further notice.


We uses cookies to remember and process the items in your shopping cart as well as to compile aggregate data about site traffic and interactions so that we can continue improving your experience on our site.