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 name | tenable_sc |
| Creates | Endpoints |
| Runs on | A sensor with HTTPS reach to Security Center |
| Presence flag | tsc_exists |
| Field prefix | tsc_ |
| Vulnerability index | vulns-<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:
| What | Security Center's view | Becomes |
|---|---|---|
| Scanned hosts | The IP summary of the cumulative database | Endpoints |
| Open findings | Vulnerability details, cumulative database | Findings in the vulnerability index |
| Fixed findings | Vulnerability details, mitigated database | Findings 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.
Endpoints
Matching
A host is matched to the endpoint it already is by, strongest first:
- Its Security Center host key: the repository and Security Center's host UUID.
- The Nessus agent that scanned it: the same agent the Nessus agents integration records.
- Its name and its IP address together.
- Its name, short or fully qualified.
- Its IP address, only on an endpoint whose name does not say it is another host.
A host known by nothing but an address, 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, mac and private_ip are written only when empty, so what an
agent on the host reported stays.
| Field | Holds |
|---|---|
tsc_host_key, tsc_host_uuid | How Security Center tells the host apart |
tsc_agent_uuid | The Nessus agent behind an agent scan |
tsc_ip, tsc_dns_name, tsc_netbios_name, tsc_mac | The host's addresses and names |
tsc_os, tsc_bios_guid | Its operating system, from Security Center's CPE, and its BIOS GUID |
tsc_repository, tsc_policy, tsc_plugin_set | Where its data lives and how it was last scanned |
tsc_last_auth_scan, tsc_last_unauth_scan | Its last credentialed and uncredentialed scans |
tsc_critical, tsc_high, tsc_medium, tsc_low | Its open findings by severity |
tsc_score, tsc_acr, tsc_aes | Security 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.
| Field | Holds |
|---|---|
asset_id | The endpoint the host is. Findings are written after the endpoints are synced, so a host created by the same run is linked at once |
plugin_id, plugin_name, family | What was found |
severity, severity_name, risk_factor | How bad: 0 Info to 4 Critical |
cve, cvss2, cvss3, cvss3_vector, cvss4, vpr, epss | Scores and the CVEs it covers |
exploit_available, exploit_ease, exploit_frameworks | Whether it can be exploited |
port, protocol | Where on the host |
synopsis, solution, description, plugin_output, see_also, xref | The plugin's text, cut to a few thousand characters |
vuln_published, patch_published, plugin_published, plugin_modified | Publication dates |
accept_risk, recast_risk | Whether the finding's risk was accepted or recast in Security Center |
ip, dns_name, netbios_name, host_key, repository_* | The host as Security Center reported it |
Its lifecycle
| Field | Holds |
|---|---|
state | open, fixed, reopened (fixed once and found again) or removed |
first_seen, last_seen | First and last time a scan found it |
fixed_at | The scan that found it fixed, the most recent time |
reopened_at, reopen_count | When it last came back, and how often |
removed_at | When Security Center stopped reporting it at all |
history | Every 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.
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
| From | To | Protocol | Port |
|---|---|---|---|
| The sensor running the integration | Security Center | HTTPS over TCP | 443 |
Access in Security Center
| Need | Why |
|---|---|
| API keys of a Security Center user | Generated in Security Center under the user's API keys. API keys must be enabled for the organisation |
| That user able to read the vulnerability data of the repositories | Every 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.
Confirm the least-privileged Security Center role that can run vulnerability analysis on a repository.
Configuration
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Label for this instance |
| URL | Yes | Security Center, e.g. https://securitycenter.contoso.com |
| Access Key | Yes | The API access key |
| Secret Key | Yes | The API secret key |
| Repositories | No | Comma-separated repository names or IDs that belong to this tenant. Empty reads every repository the user can see |
| Cookies | No | For a Security Center behind an access gateway: name=value; name2=value2 |
| Proxy settings | No | http://host:port |
| Ignore SSL | No | Skips certificate validation. Install Security Center's CA on the sensor instead where possible: the API keys are sent on every request |
| Sensor | Yes | Sensor that will run the integration |
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:
| Option | Default | Effect |
|---|---|---|
| Vulnerabilities | On | Keeps every finding in the vulnerability index. Off reads the hosts only |
| Include informational findings | Off | Also keeps severity Info findings |
See also
- Nessus agents: the agents behind Security Center's agent scans
- Integrations overview: the shared configuration model