Connectors
Tenable Security Center Connec...
Tenable.SC Connector
10 min
asset setup the asset setup is straightforward for tenable sc when using the built in actions currently available with the connector note at the time of the original documentation screenshot, the access key and secret key were not obfuscated in the asset ui this has since been resolved http connector asset setup for tenable sc to configure tenable sc using the generic http connector, you need to create a new http api key authentication asset set the following fields during asset creation key x apikey value include both keys in the following format (ensure spacing and punctuation are correct) accesskey=########; secretkey=########; the add to field should remain at the default of header http connector actions for tenable sc when configuring actions with the http asset, the following settings are required url the base url must include /rest followed by the specific resource name for example https //host domain tld/rest/plugin ssl validation must be turned off under the settings tab of the http action according to tenable's api guide, the full format is http //host\ port/rest/resource name however, the port is not required, and https works if ssl validation is disabled example query parameters for plugins to retrieve active plugins, include the following query parameters on the parameters tab filterfield=type op=eq value=active this setup successfully returned active plugin data on a test system using the http connector to query vulnerability data for a proof of value (pov) effort, vulnerability data needed to be pulled from the tenable sc dashboard using the analysis endpoint, which is not yet available in the built in connector a request has been made to add this (spt 28099) in the meantime, you can use the http connector to access this data using the following setup method post url https //x x x x 443/rest/analysis authentication use the http api key asset format mentioned above ssl validation must be turned off body a json object to define the query, for example { 	 "query" { 	 "startoffset" 0, 	 "endoffset" 50, 	 "type" "vuln", 	 "tool" "vulndetails" 	 }, 	 "sourcetype" "cumulative", 	 "type" "vuln" 	 } this setup successfully returned vulnerability data from the test system additional docs tenable sc api reference https //docs tenable com/security center/api/ tenable best practices for vulnerability data https //docs tenable com/security center/best practices/api/content/retrievevulnerabilitydataforspecifictimerange htm