--- title: "Adding supplemental CA certificates using the CLI" slug: "adding-supplemental-ca-certificates-using-the-cli-1" tags: ["File Protect (FX)", "Malware Analysis (AX)", "IAM", "Email Security - Cloud", "Network Security (NX)", "Email Security — Server", "Central Management System", "Helix Enterprise", "Endpoint Security (HX)", "Product Usage", "Install and Get Started", "Helix", "Intelligent Virtual Execution "] updated: 2026-10-01T11:46:13Z published: 2026-10-01T11:46:13Z canonical: "docs.trellix.com/adding-supplemental-ca-certificates-using-the-cli-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Adding supplemental CA certificates using the CLI Use the commands in this section to add a certificate to the certificate database, and then add it to the default CA list as a supplemental certificate. ### Note You can also download the certificate, as described in [Downloading a certificate using the CLI](/network-and-platform/docs/downloading-a-certificate-using-the-cli-1). There are two ways you can import a CA certificate: - Import a private key directly. - Import a private key by entering it when prompted. To add a supplemental CA certificate: 1. Go to CLI configuration mode: ```plaintext hostname > enable hostname # configure terminal ``` 2. Use the following command to import the supplemental certificate: ```plaintext hostname (config) # crypto certificate name public-cert pem "" [comment ""] ``` The command parameters are defined as follows: - `<certName>`—Unique certificate name; it cannot be the name of an existing certificate in the certificate database. - `<pemString>`—The public certificate PEM string. - `<comment>`—An optional comment. ### Important The PEM string and comment must be formatted as described in [Format requirements](/network-and-platform/docs/adding-supplemental-ca-certificates-using-the-cli-1#format_requirements). Example: ```plaintext hostname (config) # crypto certificate name cert0 public-cert pem "MIIEujCCA6KgAwIBAgIJAI/1cFcdOeykMA0GCSqGSIb3DQEBBQ UAMIGZMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p YTERMA8GA1UEBxMITWlscGl0YXMTJDE3GDS9DYEDLO9EWS6Fx=..." comment "certificate import example ``` 3. If you want to import a private key directly, use the following command: ```plaintext hostname (config) # crypto certificate name private-key pem "" ``` The command parameters are defined as follows: - `<certName>`—Unique certificate name; it cannot be the name of an existing certificate in the certificate database. - `<pemString>`—The public certificate PEM string, formatted as described in [Format requirements](/network-and-platform/docs/adding-supplemental-ca-certificates-using-the-cli-1#format_requirements). Example: ```plaintext hostname (config) # crypto certificate name cert1 private-key pem "MIIEujCCA6KgAwIBAgIJAI/1cFcdOeykMA0GCSqGSIb3DQEBBQ UAMIGZMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p YTERMA8GA1UEBxMITWlscGl0YXMTJDE3GDS9DYEDLO9EWS6Fx=..." ``` 4. If instead you want to import the private key by entering it when prompted and with secure echo of your response, use the following command: ```plaintext hostname (config) # crypto certificate name prompt-private-key ``` The` <certName> `parameter is the unique name by which the certificate is identified. The following example imports a private key that you enter when prompted. ```plaintext hostname (config) # crypto certificate name Cert2 prompt-private-key ``` 5. Add the certificate to the default CA list: ```plaintext hostname (config) # crypto certificate ca-list default-ca-list name cert3 ``` 6. Verify your changes: ```plaintext hostname (config) # show crypto certificate ca-list ``` 7. Save your changes. ```plaintext hostname (config) # write memory ``` ### Format requirements The PEM string must be formatted in the following order: 1. Double quotation marks 2. A new line 3. BEGIN delimiter string 4. ASCII block 5. END delimiter string 6. A new line 7. Double quotation marks ### Note You can press Enter in the CLI to add a new line. If a comment is added, it must follow the final double quotation marks and be on the same line. Any commentary outside the BEGIN and END delimiter strings is ignored. The following is an example PEM string (with a truncated ASCII block): ```plaintext >" >>----BEGIN CERTIFICATE----- >MIIEujCCA6KgAwIBAgIJAI/1cFcdOeykMA0GCSqGSIb3DQEBBQ >UAMIGZMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p >YTERMA8GA1UEBxMITWlscGl0YXMTJDE3GDS9DYEDLO9EWS6Fx= >. >. >. >----END CERTIFICATE----- > >" ``` :