Skip to main content
Version: 0.10

Tenable Security Center (WIP)

Reads Tenable Security Center (on-premises, formerly Tenable.sc) and does two things:

  • Endpoints. Every host Security Center has scanned is created or enriched as an endpoint, like any other endpoint integration.
  • Vulnerabilities. Every finding on those hosts, open and fixed, is kept with its history in the tenant's vulnerability index, apart from the endpoints. Dashboards, risk and remediation reporting read it.
Type nametenable_sc
CreatesEndpoints
Runs onA sensor with HTTPS reach to Security Center
Presence flagtsc_exists
Field prefixtsc_
Vulnerability indexvulns-<tenant id>

How it reads Security Center​

Everything comes from Security Center's analysis API, which only queries: nothing is changed in Security Center. Each run reads, for the configured repositories:

WhatSecurity Center's viewBecomes
Scanned hostsThe IP summary of the cumulative databaseEndpoints
Open findingsVulnerability details, cumulative databaseFindings in the vulnerability index
Fixed findingsVulnerability details, mitigated databaseFindings in the vulnerability index

Each run reads them whole. Security Center answers a few thousand findings in a few seconds, and reading everything is what lets a run tell which findings are no longer reported at all.

A configured repository that the user cannot read, or that does not exist, fails the run with a message listing the repositories the user can read. If the findings cannot be read, the hosts are still delivered and the findings already kept are left as they are.

Endpoints​

Matching​

A host is matched to the endpoint it already is by, strongest first:

  1. Its Security Center host key: the repository and Security Center's host UUID, or the repository and the IP address for a host without a UUID.
  2. The Nessus agent that scanned it: the same agent the Nessus agents integration records.
  3. Its name and its IP address together.
  4. Its name, short or fully qualified.
  5. Its IP address, only on an endpoint whose name does not say it is another host.

A host known by nothing but an address (no name and no MAC), which is typical of an uncredentialed sweep, enriches the endpoint it matches but never creates one.

What it writes​

Security Center is a scanner's view of the host. The shared fields names, fqdn, domains, os, type and private_ip are written only when empty, so what an agent on the host reported stays. The MACs the scan saw are added to mac beside what other sources reported; placeholder MACs that many machines share are never written. os_vendor is written from Security Center's operating system on every run. The endpoint's last_seen is its most recent scan, credentialed or not, and only moves forward.

FieldHolds
tsc_host_key, tsc_host_uuidHow Security Center tells the host apart
tsc_agent_uuidThe Nessus agent behind an agent scan
tsc_ip, tsc_dns_name, tsc_netbios_name, tsc_macThe host's addresses and names
tsc_os, tsc_bios_guidIts operating system, from Security Center's CPE, and its BIOS GUID
tsc_repository, tsc_policy, tsc_plugin_setWhere its data lives and how it was last scanned
tsc_last_auth_scan, tsc_last_unauth_scanIts last credentialed and uncredentialed scans
tsc_critical, tsc_high, tsc_medium, tsc_lowIts open findings by severity
tsc_score, tsc_acr, tsc_aesSecurity Center's vulnerability score, asset criticality rating and asset exposure score

The two last-scan dates are decommissioning evidence: a scan only finds a host that is there.

Vulnerabilities​

One document per finding​

A finding is one plugin on one host, port and protocol. It keeps the same document for its whole life, open, fixed or back again, so a run never duplicates one.

FieldHolds
asset_idThe endpoint the host is. Findings are written after the endpoints are synced, so a host created by the same run is linked at once. A link made by an earlier run stays when this run cannot make one
source, source_finding_idtenable_sc, and Security Center's own ID for the finding
check_id, title, categoryWhat was found: the plugin ID, plugin name and plugin family
severity, severity_name, source_severityHow bad: 0 Info to 4 Critical
cve, cvss2, cvss3, cvss3_vector, cvss4, epssScores and the CVEs it covers
exploit_available, exploit_frameworksWhether it can be exploited
port, protocolWhere on the host
summary, solution, description, evidence, see_alsoThe plugin's synopsis, solution, description, plugin output and references, each cut to between 1,000 and 4,000 characters
vuln_published, patch_publishedPublication dates
risk_acceptedWhether the finding's risk was accepted in Security Center
ip, hostname, fqdn, mac, os, host_key, host_uuidThe host as Security Center reported it
scope_id, scope_name, scope_uuidThe Security Center repository the finding is in
vendorWhat only Security Center reports: vpr, risk_factor, exploit_ease, check_type, xref, plugin_published, plugin_modified, recast_risk, dns_name, netbios_name
collected_at, updated_atWhen the run wrote the document

The field names are scanner-neutral so that findings from other scanners can share the index; what is specific to Security Center sits under vendor.

Its lifecycle​

FieldHolds
stateopen, fixed, reopened (fixed once and found again) or removed
first_seen, last_seenFirst and last time a scan found it
fixed_atThe scan that found it fixed, the most recent time
reopened_at, reopen_countWhen it last came back, and how often
removed_atWhen Security Center stopped reporting it at all
historyEvery change of state with its time, the latest 50

A finding is removed when a run that read everything finds it neither open nor fixed. Its host was removed from Security Center, or its data aged out, without a scan finding the finding fixed. It is not counted as remediated. Only open and reopened findings in the repositories the run read, and at a severity the run looked for, can become removed: switching Include informational findings off does not remove the Info findings already kept.

Security Center forgets fixed findings; the index does not

Security Center keeps fixed findings for a short while only, often a few weeks. The vulnerability index keeps every finding it has seen, so history builds up from the first run onwards. What was fixed before the first run and has already gone from Security Center cannot be recovered.

Informational findings​

Findings of severity Info are mostly inventory and configuration facts, and are usually the large majority of what a scan reports. They are left out unless Include informational findings is on.

Requirements​

Network access​

FromToProtocolPort
The sensor running the integrationSecurity CenterHTTPS over TCP443

Access in Security Center​

NeedWhy
API keys of a Security Center userGenerated in Security Center under the user's API keys. API keys must be enabled for the organisation
That user able to list the repositoriesEach run, and the connection test, starts by listing the repositories the user can read, to resolve the configured names
That user able to read the vulnerability data of the repositoriesEvery read is an analysis query scoped to those repositories

Give the integration a user of its own whose role can only read the repositories it needs. An administrator's keys work, but carry far more than the integration needs.

TODO

Confirm the least-privileged Security Center role that can run vulnerability analysis on a repository.

Configuration​

FieldRequiredNotes
NameYesLabel for this instance
URLYesSecurity Center, e.g. https://securitycenter.contoso.com
Access KeyYesThe API access key
Secret KeyYesThe API secret key
RepositoriesNoComma-separated repository names or IDs that belong to this tenant, matched without regard to case. Empty reads every repository the user can see
CookiesNoFor a Security Center behind an access gateway: name=value; name2=value2
Proxy settingsNohttp://host:port
Ignore SSLNoSkips certificate validation. Install Security Center's CA on the sensor instead where possible: the API keys are sent on every request
SensorYesSensor that will run the integration

Secret Key and Cookies are secrets: once saved, the console shows each as a locked box with Replace (and Remove for Cookies), never the value, and sends it only to the sensor.

Repositories separate tenants

When one Security Center serves several organisations, list each tenant's repositories on its own instance. An instance with no repositories listed reads everything its user can see.

Its scan template adds, under the advanced settings:

OptionDefaultEffect
VulnerabilitiesOnKeeps every finding in the vulnerability index. Off reads the hosts only
Include informational findingsOffAlso keeps severity Info findings

See also​