Tenable.sc

Vulnerability Management

Overview

The Tenable Security Center (Tenable.sc) connector integrates with a Tenable.sc deployment to synchronize host assets, asset groups, mobile devices, vulnerability findings, compliance violations, audit-file controls, and plugin-based vulnerability definitions into the Brinqa platform. Findings, hosts, mobile devices, and violations are sourced from the Tenable.sc analysis API; asset groups, audit-file controls, and plugin definitions are sourced from their dedicated endpoints.

---

Data retrieved from Tenable Security Center

Connector Object	Required	Maps to Data Model
Host	Yes	Host
Asset Group	Yes	(none — SDM only)
Control	Yes	Violation Definition
Mobile Device	Yes	Mobile Device
Vulnerability	Yes	Vulnerability
Violation	Yes	Violation
Vulnerability Definition	Yes	Vulnerability Definition

Model relationships

note

For detailed steps on how to view the data retrieved from Tenable Security Center in the Brinqa Platform, see How to view your data.

note

The Tenable Security Center connector supports Tenable Security Center versions 5 and above (testing for 6.4 is ongoing).

note

Tenable Security Center refers to Vulnerability Definitions as Plugins. When the Sync data from setting is enabled, the connector filters patched vulnerabilities using the lastMitigated timestamp; for cumulative and other types it uses lastSeen.

note

Asset Group intentionally maps to no unified data model. It is published as a source data model (SDM) only, so it participates in no out-of-the-box consolidation.

note

rest/asset returns the complete asset-group list in a single response — it exposes no offset/limit parameters and applies no server-side cap — so Asset Group performs no paging and the configured page size does not apply. On very large instances the member IP list can be excluded via the fields operation option to reduce response size.

Setup

Connection settings

When setting up a data integration, select Tenable Security Center from the Connector dropdown and provide the following:

Setting	Required	Default	Description
Server URL	Yes	—	Tenable Security Center server URL
Access key	Yes	—	Tenable Security Center API access key
Secret key	Yes	—	Tenable Security Center API secret key
Page size	No	1000	Maximum number of records to get per API request
Parallel requests	No	min(8, available processors)	Maximum number of parallel API requests
Maximum retries	No	10	The maximum number of retry attempts before giving up a request
SSL / TLS	No	false	Skip certificate verification

Authentication

Method

API Key authentication using an Access Key and Secret Key pair.

Endpoint

Method	URL
GET / POST	{url}/*

{url} is the base URL of the Tenable.sc deployment (the url configuration property).

Request Headers

Header	Value
x-apikey	accesskey={accessKey}; secretkey={secretKey};
Accept	application/json

Usage

Every API request carries the API key pair in the x-apikey header. No separate token exchange or login step is required.

---

Sync Behavior

The connector performs a mix of full and incremental (delta) syncs depending on the model. Most models filter their analysis or API results by a since timestamp (see each model's Sync Duration Parameter); the Asset Group model applies no incremental filter and performs a full sync every run.

How to obtain Tenable Security Center credentials

Obtain the required credentials (url, accessKey, secretKey) from your Tenable Security Center administrator or the Tenable Security Center admin console, then enter them in the connection settings above.

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Host

Source Field Name	SDM Attribute
constant	CATEGORIES
constant	STATUS
derived asset id (identifier / serial / repo+ip+dns)	UID
host createdTime	SOURCE_CREATED_DATE
host dns (or record dnsName)	PUBLIC_DNS_NAMES
host dns (or record dnsName)	PRIVATE_DNS_NAMES
host firstSeen	FIRST_SEEN
host ipAddress (or record ip)	IP_ADDRESSES
host ipAddress (or record ip)	PUBLIC_IP_ADDRESSES
host ipAddress (or record ip)	PRIVATE_IP_ADDRESSES
host lastSeen / record lastRun	LAST_SEEN
host macAddress (or record macAddress)	MAC_ADDRESSES
host modifiedTime	SOURCE_LAST_MODIFIED
host name / dns / netBios (or record)	HOSTNAMES
host name / dns / netBios / ipAddress (or record)	NAME
host os (or record osCPE)	DESCRIPTION
host os (or record osCPE)	OPERATING_SYSTEM
host repository.id	REPO_ID
host repository.name	REPO_NAME
host systemType	SYSTEM_TYPE
host tenableUUID	TENABLE_UUID
host uuid	UUID
Instant.now()	LAST_CAPTURED
record lastAuthRun	LAST_AUTH_RUN
record lastRun	LAST_SCANNED
record lastUnauthRun	LAST_UNAUTH_RUN
record osCPE	OS_CPE

Asset Group

Source Field Name	SDM Attribute
asset.context	CONTEXT
asset.createdTime	SOURCE_CREATED_DATE
asset.creator	CREATOR
asset.description	DESCRIPTION
asset.id	UID
asset.ipCount	IP_COUNT
asset.modifiedTime	SOURCE_LAST_MODIFIED
asset.name	NAME
asset.owner	OWNER
asset.ownerGroup	GROUP
asset.repositories	REPOSITORIES
asset.status	PROVIDER_STATUS
asset.tags	TAGS
asset.type	TYPE
asset.viewableIPs	IP_LIST
Instant.now()	LAST_CAPTURED
—	STATUS

Control

Source Field Name	SDM Attribute
(schema)	AUDIT_FILE_ID
auditFile.auditFileTemplate.id	AUDIT_FILE_TEMPLATE_ID
auditFile.auditFileTemplate.name	AUDIT_FILE_TEMPLATE_NAME
auditFile.context	CONTEXT
auditFile.createdTime	CREATED_TIME
auditFile.creator	CREATOR
auditFile.description	DESCRIPTION
auditFile.filename	FILE_NAME
auditFile.id	UID
auditFile.lastRefreshedTime	LAST_REFRESHED_TIME
auditFile.modifiedTime	MODIFIED_TIME
auditFile.name	NAME
auditFile.originalFilename	ORIGINAL_FILE_NAME
auditFile.owner	OWNER
auditFile.ownerGroup	OWNER_GROUP
auditFile.status	STATUS
auditFile.targetGroup	TARGET_GROUP
auditFile.type	TYPE
auditFile.uuid	TENABLE_UUID
auditFile.version	AUDIT_FILE_VERSION
Instant.now()	LAST_CAPTURED

Mobile Device

Source Field Name	SDM Attribute
device.deviceVersion	DEVICE_VERSION
device.identifier	UID
device.lastSeen	LAST_SCANNED
device.mdmType	MDM_TYPE
device.model	MODEL
device.osCPE	OS_CPE
device.serial	SERIAL
device.user	USER
Instant.now()	LAST_CAPTURED

Vulnerability

Source Field Name	SDM Attribute
acceptRisk	RISK_ACCEPTED
derived from source type	PROVIDER_STATUS
derived from source type	SOURCE_STATUS
derived from source type	STATUS
derived from status	STATUS_CATEGORY
dnsName	PUBLIC_DNS_NAMES
dnsName	PRIVATE_DNS_NAMES
firstSeen	FIRST_FOUND
identifier / serial / unique asset id	TARGETS
Instant.now()	LAST_CAPTURED
ip	IP_ADDRESSES
lastSeen	LAST_FOUND
macAddress	MAC_ADDRESSES
MD5(assetId, PID-{pluginID}, port, protocol)	UID
netbiosName	HOSTNAMES
pluginID	TYPE
pluginText (plugin_output)	RESULTS
port	PORT
protocol	PROTOCOL
recastRisk	RISK_RECASTED
repository.id	REPO_ID
repository.name	REPO_NAME
severity	SOURCE_SEVERITY_SCORE
severity	SEVERITY
severity	SEVERITY_SCORE
severity.name	SOURCE_SEVERITY

Violation

Source Field Name	SDM Attribute
acceptRisk	RISK_ACCEPTED
audit file id	AUDIT_FILE_ID
dnsName	DNS_NAME
firstSeen	FIRST_SEEN
hasBeenMitigated	MITIGATED
Instant.now()	LAST_CAPTURED
ip	IP_ADDRESS
lastSeen	LAST_SEEN
macAddress	MAC_ADDRESS
netbiosName	NET_BIOS
pluginID	UID
pluginID	PLUGIN_ID
pluginText (compliance-actual-value)	ACTUAL_VALUE
pluginText (compliance-audit-file)	AUDIT_FILE
pluginText (compliance-info)	INFORMATION
pluginText (compliance-policy-value)	POLICY_VALUE
pluginText (compliance-reference)	COMPLIANCE_REFERENCE
pluginText (compliance-result)	RESULT
pluginText (plugin_output)	PLUGIN_OUTPUT
port	PORT
protocol	PROTOCOL
recastRisk	RISK_RECASTED
repository.id	REPO_ID
repository.name	REPO_NAME
severity.name	SEVERITY

Vulnerability Definition

Source Field Name	SDM Attribute
Instant.now()	LAST_CAPTURED
plugin.baseScore	CVSS_V2_BASE_SCORE
plugin.checkType	CHECK_TYPE
plugin.cpe	AFFECTED
plugin.cvssV3BaseScore	CVSS_V3_BASE_SCORE
plugin.cvssV3TemporalScore	CVSS_V3_TEMPORAL_SCORE
plugin.cvssV3Vector	CVSS_V3_VECTOR, CVSS_V3_AC, CVSS_V3_AI, CVSS_V3_AV, CVSS_V3_CI, CVSS_V3_E, CVSS_V3_II, CVSS_V3_PR, CVSS_V3_RC, CVSS_V3_RL, CVSS_V3_SEVERITY, CVSS_V3_UI
plugin.cvssVector	CVSS_V2_VECTOR, CVSS_V2_AC, CVSS_V2_AI, CVSS_V2_AU, CVSS_V2_AV, CVSS_V2_CI, CVSS_V2_E, CVSS_V2_II, CVSS_V2_RC, CVSS_V2_RL, CVSS_V2_SEVERITY
plugin.description	DESCRIPTION
plugin.exploitAvailable	EXPLOIT_AVAILABLE
plugin.exploitEase	EXPLOIT_EASE
plugin.exploitFrameworks	EXPLOITS
plugin.family.name	CATEGORIES
plugin.id	UID
plugin.modifiedTime / plugin.pluginModDate	SOURCE_LAST_MODIFIED
plugin.name	NAME
plugin.patchPubDate	PATCHABLE
plugin.patchPubDate	PATCH_PUBLICATION_DATE
plugin.pluginPubDate	PUBLISHED_DATE
plugin.riskFactor	SOURCE_SEVERITY / SOURCE_SEVERITY_SCORE
plugin.riskFactor	SEVERITY / SEVERITY_SCORE
plugin.seeAlso	SEE_ALSO
plugin.solution	RECOMMENDATION
plugin.synopsis	SUMMARY
plugin.temporalScore	CVSS_V2_TEMPORAL_SCORE
plugin.type	PLUGIN_TYPE
plugin.vprContext (age_of_vuln)	VULNERABILITY_AGE
plugin.vprContext (cvssV3_impactScore)	CVSS_V3_IMPACT_SCORE
plugin.vprContext (exploit_code_maturity)	EXPLOIT_CODE_MATURITY
plugin.vprContext (predicted_impactScore)	CVSS_IMPACT_SCORE_PREDICTED
plugin.vprContext (product_coverage)	PRODUCT_COVERAGE
plugin.vprContext (threat_intensity_last_28)	THREAT_INTENSITY
plugin.vprContext (threat_model_type)	THREAT_MODEL_TYPE
plugin.vprContext (threat_model_version)	THREAT_MODEL_VERSION
plugin.vprContext (threat_recency)	THREAT_RECENCY
plugin.vprContext (threat_sources_last_28)	THREAT_SOURCES
plugin.vprScore	VPR_SCORE
plugin.vulnPubDate	VULNERABILITY_PUBLISHED_DATE
plugin.xrefs (CVE entries)	CVE_IDS / CVE_RECORDS
plugin.xrefs (non-CVE)	REFERENCES

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

Host

Operation options

Option	Type	Default	Description
sourceType	String	cumulative, patched	Comma-separated analysis source types to query
tool	String	model-specific	Analysis tool (sumip for Host, vulndetails for findings)
type	String	model-specific	Analysis type (mobile for Mobile Device)
per_repo_distinct_asset_uuid	Boolean	false	Generate a distinct asset UID per repository

Delta sync

Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on lastSeen.

API

• Type: REST endpoint · Endpoint: POST rest/analysis

Asset Group

Operation options

Option	Type	Default	Description
fields	String	(built-in field set)	Comma-separated asset fields to request from rest/asset
filter	String	excludeAllDefined,usable	Filter applied to the asset query

Delta sync

Not supported. The connector performs a full sync of Asset Group on every run and applies no incremental date filter.

API

• Type: REST endpoint · Endpoint: GET rest/asset

Control

Operation options

This object does not support any operation options.

Delta sync

Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on since.

API

• Type: REST endpoint · Endpoint: GET rest/auditFile

Mobile Device

Operation options

Option	Type	Default	Description
tool	String	model-specific	Analysis tool (sumip for Host, vulndetails for findings)
type	String	model-specific	Analysis type (mobile for Mobile Device)

Delta sync

Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on lastSeen.

API

• Type: REST endpoint · Endpoint: POST rest/analysis

Vulnerability

Operation options

Option	Type	Default	Description
sourceType	String	cumulative, patched	Comma-separated analysis source types to query
tool	String	model-specific	Analysis tool (sumip for Host, vulndetails for findings)
type	String	model-specific	Analysis type (mobile for Mobile Device)
per_repo_distinct_asset_uuid	Boolean	false	Generate a distinct asset UID per repository
infoPlugin	String	—	Additionally retrieve informational findings for the given plugin
plugin / pluginID / pluginID>= / pluginID<= / pluginID!=	String	—	Filter findings by plugin ID using the given operator

Delta sync

Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on lastSeen.

API

• Type: REST endpoint · Endpoint: POST rest/analysis

Violation

Operation options

Option	Type	Default	Description
sourceType	String	cumulative, patched	Comma-separated analysis source types to query
tool	String	model-specific	Analysis tool (sumip for Host, vulndetails for findings)
type	String	model-specific	Analysis type (mobile for Mobile Device)

Delta sync

Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on lastSeen.

API

• Type: REST endpoint · Endpoint: GET rest/auditFile

Vulnerability Definition

Operation options

This object does not support any operation options.

Delta sync

Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on since.

API

• Type: REST endpoint · Endpoint: GET rest/plugin

Changelog

Changelog

The Tenable Security Center connector has undergone the following changes:

Version	Description	Migration Steps
3.1.51	New Features - Asset Group is now available for synchronization. Tenable.sc asset groups are retrieved with their tags, description, type, status, owner, creator, owner group, repositories, creation and modification times, and the member assets they cover — including each member's IP address and identifier — plus a count of covered IP addresses. Because Tenable.sc does not provide asset-level tags natively, this makes group tags and membership available in Brinqa for use in prioritization, ownership, and reporting. Asset Group is a standalone object: it is not consolidated into another data model, and applying group tags to individual assets requires configuration in Brinqa. Asset Group performs a full sync on each run.	N/A
3.1.50	No changes in this release.	N/A
3.1.49	Bug Fixes - Vulnerability Definition — Fixed an error that could prevent the "CVSS v3 impact score" from being stored when the source reported the value as a whole number or as text rather than a decimal. The score is now reliably recorded as a decimal value.	N/A
3.1.48	Bug Fixes - Violation — Corrected the "First seen" and "Last seen" attributes to be stored as proper timestamps. The Violation model declared its own "First seen"/"Last seen" attributes as numbers while the SecurityCenter API returns timestamp values, so the values were being stored with the wrong type. These attributes now use the platform's standard timestamp attributes, consistent with the Host model.	• Violation: the date attributes listed above changed from numbers to timestamps. Re-sync the Tenable SC connector to repopulate these records with the corrected type.
3.1.47	No changes in this release.	N/A
3.1.46	Improvements Dependency Upgrades - Refreshed internal model and CVSS scoring libraries to the latest stable releases to pick up upstream fixes and stay aligned with the rest of the Brinqa connector platform. Cross-Connector Attribute Consolidation - Every connector-defined custom attribute now participates in cross-connector consolidation by default. When the same asset or finding is observed by another connector, Brinqa will merge values for these attributes consistently rather than treating each connector's values as independent. Tenable.sc Schema Alignment - Asset Group, Mobile Device, Control, Violation now use the standard platform UID attribute as the identifier in their schemas, replacing the previous redundant Sys ID attribute that mirrored the same value. The Asset Group and Mobile Device schemas now also publish UID as an explicit identifier alongside their existing display key. Control and Violation now declare proper schema metadata (target ViolationDefinition and Violation respectively) so that platform features that depend on schema metadata work consistently for these models. - Tenable.sc attribute names are now standard. Previously, the connector emitted attributes such as Name, Description, Status, Tags, Owner, Type, Severity, Port, Protocol, and File name with title-case names that did not match other Brinqa connectors. The same attributes are now emitted under the platform-standard names (NAME, DESCRIPTION, STATUS, TAGS, OWNER, TYPE, SEVERITY, PORT, PROTOCOL, FILE_NAME, etc.), matching Tenable IO VM, Tenable IO WAS, and Tenable Nessus. - Vulnerability now exposes both PROVIDER_STATUS and SOURCE_STATUS. Previously the connector stored the raw API status under SOURCE_STATUS and the normalized status under STATUS. After the upgrade, the raw API status is stored under the new PROVIDER_STATUS attribute, and SOURCE_STATUS holds the normalized status (matching Tenable IO VM behavior). - Mobile Device "Last scanned" is now under the standard LAST_SCANNED attribute rather than the previous Last scanned custom attribute. The value (epoch milliseconds) is unchanged. - Mobile Device "Device version" is now under DEVICE_VERSION (previously emitted as Device version). - Control's distinct Tenable UUID field (previously emitted as Uuid) is now TENABLE_UUID, matching how other Tenable models expose the Tenable-specific UUID. - A latent type mismatch on the Violation Severity attribute has been corrected: the schema declared Integer but the connector wrote the severity name as a string. The attribute is now declared String, aligning the schema with the values actually stored. - A copy/paste defect in Control that overwrote the Audit file template ID with the template name (and never populated the template name) has been fixed; Audit file template ID and Audit file template name are now populated independently.	• Re-sync the connector after upgrading so that previously synced records pick up the new consolidation mappings. Existing data remains intact; the re-sync ensures consolidated values for assets and findings shared with other connectors converge correctly. • For Asset Group, Mobile Device, Control, and Violation records, any UI views, reports, or rules that referenced the Sys ID attribute should be updated to use the standard UID instead. The values are identical to what was previously stored under Sys ID. • Attribute renames. Update any UI views, queries, reports, or rules that reference the following old attribute names; the values they hold are unchanged, only the attribute name changes: | Model | Old Attribute | New Attribute | |:---|:---|:---| | Asset Group | Name | NAME | | Asset Group | Description | DESCRIPTION | | Asset Group | Type | TYPE | | Asset Group | Status | STATUS | | Asset Group | Owner | OWNER | | Asset Group | Tags | TAGS | | Asset Group | Creator | CREATOR | | Asset Group | Group | GROUP | | Asset Group | IP list | IP_LIST | | Asset Group | Repositories | REPOSITORIES | | Asset Group | Created time | CREATED_TIME | | Asset Group | Modified time | MODIFIED_TIME | | Mobile Device | Serial | SERIAL | | Mobile Device | Model | MODEL | | Mobile Device | Device version | DEVICE_VERSION | | Mobile Device | MDM type | MDM_TYPE | | Mobile Device | User | USER | | Mobile Device | OS CPE | OS_CPE | | Mobile Device | Last scanned | LAST_SCANNED | | Control | Name | NAME | | Control | File name | FILE_NAME | | Control | Audit file version | AUDIT_FILE_VERSION | | Control | Uuid | TENABLE_UUID | | Control | Type | TYPE | | Control | Status | STATUS | | Control | Description | DESCRIPTION | | Control | Owner | OWNER | | Control | Creator | CREATOR | | Control | Context | CONTEXT | | Control | Original file name | ORIGINAL_FILE_NAME | | Control | Last refreshed time | LAST_REFRESHED_TIME | | Control | Audit file template id | AUDIT_FILE_TEMPLATE_ID | | Control | Audit file template name | AUDIT_FILE_TEMPLATE_NAME | | Control | Created time | CREATED_TIME | | Control | Modified time | MODIFIED_TIME | | Control | Owner group | OWNER_GROUP | | Control | Target group | TARGET_GROUP | | Violation | Plugin ID | PLUGIN_ID | | Violation | Asset ID | ASSET_ID | | Violation | Repository ID | REPO_ID | | Violation | Repository name | REPO_NAME | | Violation | Severity | SEVERITY | | Violation | Mitigated | MITIGATED | | Violation | Risk accepted | RISK_ACCEPTED | | Violation | Risk recasted | RISK_RECASTED | | Violation | IP address | IP_ADDRESS | | Violation | DNS name | DNS_NAME | | Violation | MAC address | MAC_ADDRESS | | Violation | NetBIOS | NET_BIOS | | Violation | Port | PORT | | Violation | Protocol | PROTOCOL | | Violation | Plugin output | PLUGIN_OUTPUT | | Violation | Audit file | AUDIT_FILE | | Violation | Policy value | POLICY_VALUE | | Violation | Information | INFORMATION | | Violation | Actual value | ACTUAL_VALUE | | Violation | Result | RESULT | | Violation | Compliance reference | COMPLIANCE_REFERENCE | | Violation | First seen | FIRST_SEEN | | Violation | Last seen | LAST_SEEN | | Violation | Audit file id | AUDIT_FILE_ID | • Vulnerability finding status semantics changed. If you have downstream logic that depends on SOURCE_STATUS containing the raw Tenable.sc status value, update it to read from the new PROVIDER_STATUS attribute instead. SOURCE_STATUS now contains the normalized Brinqa status (the same value previously stored under STATUS).
3.1.45 — Withdrawn	This release shipped a regression and has been superseded by 3.1.46. Customers should skip 3.1.45 and upgrade directly from 3.1.44 to 3.1.46.	N/A
3.1.44	Improvements Dependency Upgrades - Upgraded internal framework and storage libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.	Several attributes were removed in the underlying framework and replaced with renamed multi-valued (or boolean-equivalent) counterparts. Values previously stored under the old attribute names remain in place but will no longer be updated; new syncs populate the new attribute names. Action: Re-sync the connector after upgrade. | Model | Old Attribute | New Attribute | |:---|:---|:---| | Host | HOSTNAME | HOSTNAMES | | Host | PRIVATE_DNS_NAME | PRIVATE_DNS_NAMES | | Host | PUBLIC_DNS_NAME | PUBLIC_DNS_NAMES | | Host | PUBLIC_IP_ADDRESS | PUBLIC_IP_ADDRESSES | | Vulnerability | HOSTNAME | HOSTNAMES | | Vulnerability | PRIVATE_DNS_NAME | PRIVATE_DNS_NAMES | | Vulnerability | PUBLIC_DNS_NAME | PUBLIC_DNS_NAMES | | Vulnerability Definition | PATCH_AVAILABLE | PATCHABLE |
3.1.43	No changes in this release.	N/A
3.1.42	No changes in this release.	N/A
3.1.41	Improvements - Host now records when it was last observed by the connector under the standard LAST_CAPTURED attribute, making it easier to distinguish the most recent sync time from the host's own last-seen timestamp.	N/A
3.1.40	No changes in this release.	N/A
3.1.39	Improvements - The connector now treats Tenable.sc gateway-timeout (504) and service-unavailable (503) responses as transient: it retries them and, if the resource still cannot be retrieved, skips that resource and continues the sync instead of failing the entire run. Dependency Upgrades - Upgraded the shared connector framework to the latest stable version.	N/A
3.1.38	Bug Fixes - Vulnerability and Violation no longer publish a separate "Last fixed" attribute that mirrored the last-mitigated timestamp. The redundant attribute is removed; the last-mitigated value continues to be reflected through the existing last-seen handling.	• Vulnerability, Violation: the LAST_FIXED attribute is no longer populated. Update any UI views, reports, or rules that referenced it. Re-sync the connector after upgrade.
3.1.37	No changes in this release.	N/A
3.1.36	No changes in this release.	N/A
3.1.35	No changes in this release.	N/A
3.1.34	No changes in this release.	N/A
3.1.33	No changes in this release.	N/A
3.1.32	Improvements - The connector now detects Tenable.sc service-unavailable (503) responses, retries them, and skips the affected resource rather than aborting the sync when it remains unavailable. Dependency Upgrades - Upgraded the shared connector framework to the latest stable version.	N/A
3.1.31	No changes in this release.	N/A
3.1.30	No changes in this release.	N/A
3.1.29	No changes in this release.	N/A
3.1.28	No changes in this release.	N/A
3.1.27	Bug Fixes - Hardened parsing of Tenable.sc host asset-criticality (ACR) data so that records missing a host UUID no longer cause sync errors.	N/A
3.1.26	Improvements Dependency Upgrades - Upgraded the internal model and storage libraries to the latest stable versions.	N/A
3.1.25	No changes in this release.	N/A
3.1.24	Improvements Dependency Upgrades - Upgraded the shared connector framework and internal model libraries to the latest stable versions.	N/A
3.1.23	Improvements - Reworked CVSS v2/v3 vector parsing onto the shared scoring utility for more consistent and reliable CVSS attribute extraction on Vulnerability Definition records. Dependency Upgrades - Upgraded the CVSS scoring and code-generation libraries to the latest stable versions.	N/A
3.1.22	Improvements Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.1.21	No changes in this release.	N/A
3.1.20	Improvements - Vulnerability Definition: the "Exploit available" attribute is now a true/false value instead of free-form text, making it directly usable in filters and rules.	• Vulnerability Definition: the EXPLOIT_AVAILABLE attribute changed from text to a boolean. Update any UI views, reports, or rules that compared it as a string, and re-sync the connector after upgrade.
3.1.19	Improvements Dependency Upgrades - Upgraded the internal model and storage libraries to the latest stable versions.	N/A
3.1.18	Improvements - Vulnerability Definition now captures the vulnerability publication date from Tenable.sc under the new VULNERABILITY_PUBLISHED_DATE attribute.	N/A
3.1.17	No changes in this release.	N/A
3.1.16	Improvements - CVSS and VPR scores on Vulnerability and Vulnerability Definition are now captured with full double precision, eliminating rounding artifacts that could appear with the previous single-precision handling. Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	• Vulnerability, Vulnerability Definition: CVSS/VPR score attributes (e.g. VPR_SCORE, CVSS_V3_IMPACT_SCORE) changed from single- to double-precision numbers. Re-sync the connector after upgrade so existing records pick up the corrected values.
3.1.15	Improvements - Vulnerability now publishes both a normalized severity score (SEVERITY_SCORE) and the source severity score (SOURCE_SEVERITY_SCORE) alongside the existing severity values. - Vulnerability Definition: corrected the data types of the "Product coverage" and "Vulnerability age" attributes to text so they reflect the values Tenable.sc actually returns. Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	• Vulnerability Definition: the PRODUCT_COVERAGE and VULNERABILITY_AGE attribute types changed. Re-sync the connector after upgrade to repopulate these records with the corrected types.
3.1.14	Improvements - Host now publishes multi-valued counterparts for hostname, public IP, and public/private DNS name (HOSTNAMES, PUBLIC_IP_ADDRESSES, PUBLIC_DNS_NAMES, PRIVATE_DNS_NAMES) and uses these as additional cross-connector identifiers, improving asset correlation. Hostnames are also normalized more consistently. Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.1.13	Improvements - Added a per_repo_distinct_asset_uuid sync option for Host and Vulnerability. When enabled, the asset identifier incorporates the Tenable.sc repository ID so that the same UUID appearing in multiple repositories is treated as distinct assets.	• Host, Vulnerability: enabling per_repo_distinct_asset_uuid changes how the asset identifier is derived and will re-key affected records. Only enable it for environments that require per-repository asset separation, and re-sync the connector after changing this option.
3.1.12	Improvements - Added a configurable maximum-retries setting so the connector's retry behavior against Tenable.sc can be tuned per environment. Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.1.11	New Features - Vulnerability now exposes the raw Tenable.sc status under the SOURCE_STATUS attribute in addition to the normalized STATUS. Improvements - Violation now records the last-mitigated time under a dedicated "Last fixed" attribute instead of overwriting "Last seen". Dependency Upgrades - Upgraded the shared connector framework and internal model libraries to the latest stable versions.	• Violation: the boolean attributes "Mitigated", "Risk accepted", and "Risk recasted" now allow an unset (null) value rather than always defaulting to false, and a new "Last fixed" attribute is published. Re-sync the connector after upgrade.
3.1.10	Improvements - Added a per_repo_distinct_asset_uuid analysis option to Vulnerability sync for environments that need repository-scoped asset uniqueness. Dependency Upgrades - Upgraded the internal storage library to the latest stable version.	N/A
3.1.9	Improvements - Date/time values on Host, Vulnerability, Violation, and Mobile Device (first seen, last seen, last scanned, last run, created/modified times) are now parsed directly as timestamps from Tenable.sc, improving accuracy and consistency.	• Host, Vulnerability, Violation, Mobile Device: the date/time attributes listed above are now populated from properly typed timestamp values. Re-sync the connector after upgrade so existing records reflect the corrected values.
3.1.8	No changes in this release.	N/A
3.1.7	Improvements - Vulnerability finding status is now derived consistently from the Tenable.sc record's source type, correctly distinguishing fixed, risk-accepted, and reopened findings.	N/A
3.1.6	Improvements - Refined the "accept risk" sync filter so that selecting "not accepted" no longer sends an unsupported filter value to Tenable.sc.	N/A
3.1.5	Improvements - The "accept risk" sync filter now defaults to including all findings regardless of their accept-risk status, so risk-accepted findings are no longer omitted unless explicitly filtered out.	N/A
3.1.4	Improvements - Vulnerability findings that Tenable.sc reports as risk-accepted are now reflected in the finding's status.	N/A
3.1.3	No changes in this release.	N/A
3.1.2	Bug Fixes - Vulnerability Definition now guards against invalid (zero or negative) date values from Tenable.sc, so published, patch-publication, and last-modified dates are only set when a valid value is present. Patch availability now defaults to false when no patch date is reported.	N/A
3.1.1	No changes in this release.	N/A
3.1.0	Improvements Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.0.16	Improvements Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.0.15	Improvements Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.0.14	No changes in this release.	N/A
3.0.13	Improvements Dependency Upgrades - Upgraded the shared connector framework and internal model libraries to the latest stable versions.	N/A
3.0.12	Improvements - Added a sync-interval option and a configurable maximum-retries setting, giving more control over how the connector schedules incremental syncs and retries requests against Tenable.sc. Dependency Upgrades - Upgraded the shared connector framework and internal model libraries to the latest stable versions.	N/A
3.0.11	No changes in this release.	N/A
3.0.10	No changes in this release.	N/A
3.0.9	No changes in this release.	N/A
3.0.8	Improvements Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.0.7	No changes in this release.	N/A
3.0.6	No changes in this release.	N/A
3.0.5	Improvements - Vulnerability Definition: the patch publication date is now published under its own PATCH_PUBLICATION_DATE attribute instead of overwriting the vulnerability's published date, so both dates are now available independently.	• Vulnerability Definition: patch publication date moved from PUBLISHED_DATE to the new PATCH_PUBLICATION_DATE attribute. Update any UI views, reports, or rules that relied on patch dates appearing under "Published date", and re-sync the connector after upgrade.
3.0.4	Improvements - Vulnerability Definition: severity is now published as a normalized severity score (SEVERITY_SCORE) on a 0–10 scale, replacing the previous integer severity-number value.	• Vulnerability Definition: the previous SEVERITY_NUMBER attribute is replaced by SEVERITY_SCORE, which uses a different (0–10) scale. Update any UI views, reports, or rules that referenced SEVERITY_NUMBER or assumed the old values, and re-sync the connector after upgrade.
3.0.3	No changes in this release.	N/A
3.0.2	Improvements - Vulnerability Definition now publishes a numeric severity value (SEVERITY_NUMBER) alongside the normalized severity. Dependency Upgrades - Upgraded the internal model libraries to the latest stable version.	N/A
3.0.1	No changes in this release.	N/A
3.0.0	Overview The Tenable Security Center connector integrates with Tenable.sc to synchronize host assets, vulnerability findings, and the vulnerability definitions (plugins) behind them. Category: Vulnerability Management Models	N/A