TOC & Recently Viewed

Recently Viewed Topics

Upload Custom CA Certificate

  1. Copy your PEM encoded certificate into a text file and name it Make sure you include the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines and everything in between. (If you need to upload multiple certificates, paste them all in back-to-back.)
  2. Create a text file named and include the following 2 lines:
    Note: The plugin set date should be the same as the time the bundle is uploaded to SecurityCenter. It cannot be after the present date/time in SC

    PLUGIN_SET = "201310161758";

    PLUGIN_FEED = "Custom";

    Note: The typical format for PLUGIN_SET is a string of numbers in the format "YYYYMMDDHHMM" for the regular feed so that format is copied here.

  3. Tar the 2 files into a .tar.gz archive, 7-Zip or running tar on a Mac will not work for this:

    # tar -zcvf upload_this.tar.gz

  4. Upload the archive.

a. Log in to SecurityCenter as admin

b. Click the admin's user name in the upper right-hand corner of the screen and select "Plugins"

c. Click "Upload Custom Plugins," then "Submit"

  1. Verify upload was successful

a. Go to System -> System Logs

b. You should see logs similar to the following:

  1. Verify issue is resolved by running another scan including plugin 51192. You can verify that Nessus has the custom plugin bundle by checking it's plugin directory.
Note: The file is overwritten every time it is uploaded. When adding additional CA certificates, start with a copy of the existing and append the new certificate. If there are multiple certificates in the file, it should look like this:











Note: Step 6 above, updating SecurityCenter plugins to initiate a plugin push to the Nessus scanners, will only work if the plugin feed being downloaded by SC is newer than the plugin set on the Nessus scanners. If it is still the same plugin set because Tenable has not released a newer plugin feed yet, wait a few hours for the next plugin feed to be available and then update again, or wait for the scheduled plugin update to run overnight.


If this process does not work, check the following items:

  1. format - The CA certificate should be in PEM (Base64) format. To verify, open it in a text editor. The certificate should be between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----. If you do not see those lines, it is in the wrong format and should be changed to PEM (Base64) format.
  2. /opt/sc/data/customNasl/ - If the SecurityCenter installation is not on the Appliance, check the uploaded with the following command: # cat /opt/sc/data/customNasl/

    The output should match the file that you checked in a text editor in step T1 above. If the file does not exist, the upload was not successful. If the file does not match, the most recent upload may not have been successful. Go over the steps above for creating and uploading upload_this.tar.gz and ensure it is being done correctly.

  3. /opt/nessus/lib/nessus/plugins/ or \ProgramData\Tenable\Nessus\nessus\plugins\

    If Nessus is not on the Appliance, navigate to the plugins folder and cat or type to verify it exists and matches the file contents verified in steps 1 and 2 above. If does not exist in the plugins folder, or does not match the most recent in SecurityCenter, it has not propagated to the scanner. Check Resources > Nessus Scanners in SecurityCenter to see if the scanner is still updating plugins. If it is in a Working state, try updating the active plugins in SecurityCenter to prompt a plugin push. See note N2 above about plugin feed versions. If the plugin feed version has not incremented and the customer really has to push plugins right now, see the following article: Force plugin update on scanner managed by SecurityCenter (Comparable to nessus-update-plugins -f)

  4. Plugin ouput

    Adding the custom CA certificate to will not resolve the issue if the issue is something else - the service is missing intermediate certificate(s), the service has a self-signed or default certificate (if not self-signed with the server name, it may be issued by a vendor name like "Nessus Certification Authority") and not a certificate signed by their custom CA at all, the certificate is expired, etc. Look at the detailed plugin output of 51192 to see exactly why the certificate is untrusted. If will fix it, the output will say that the certificate at the top of the certificate chain is unrecognized, and the certificate it shows will be either issued by the custom CA (matching the name *exactly*) or the actual custom CA self-signed certificate.

    Delete this text and replace it with your own content.

Copyright 2017. Tenable Network Security, Inc. All rights reserved. Tenable Network Security, Nessus, SecurityCenter Continuous View, Passive Vulnerability Scanner, and Log Correlation Engine are registered trademarks of Tenable Network Security, Inc. All other products or services are trademarks of their respective owners.