Phew. It’s been a great start to the year here at Nucleus Security with another release jam packed full of new functionality. See below to find out more!
In this release we have turbo-charged our ticketing automation functionality so you can get more out of ticket workflow management.
Tickets that have been raised using one of our ticketing connectors are now responsive to changes in the vulnerability source tool. For example, when a new instance of a vulnerability that has been previously raised in an open ticket is found, that existing ticket will be automatically updated with new information. What’s more, you can optionally have a ticket close in the downstream system when it’s been identified as remediated in Nucleus!
It’s now also easier to retrospectively run ticketing rules over existing data sets. This means that if you decide to turn on ticketing in a Nucleus project later down the line, you can raise tickets against existing vulnerabilities that match your ticketing rule at the tap of a button.
Finally, where supported within the ticketing system, Nucleus will automatically upload a csv file containing all of the affected assets for easier data export and parsing by support teams. We hope that this change will make it simpler to remediating vulnerabilities for technical teams.
We’ve made a change to our notifications section which we hope you’ll agree, make a lot more sense: we’ve moved the automation rule configuration for chat connectors to the Notifications section within Automation, rather than Ticketing & Issue Tracking.
We’ve also released a brand new connector for Microsoft Teams. This one has been asked for by a lot of customers, so if you haven’t yet had a chance to check it out, do so today!
API & Nucleus Custom File Schema
There are a few improvements to the Nucleus Custom File Schema, making it easier to get asset and finding data in to Nucleus:
- the scan date can now also include the timezone
- secondary hostnames and ip addresses can be set for host assets
- you can now pass HTTP requests and responses within a finding encoded using base 64, which Nucleus will automatically decode
The API has also been updated to return a container image’s tag, repository URL, digest and distro when querying for assets.
Multi Factor Authentication via TOTP
This release we’ve introduced improved support for Multi Factor Authentication (MFA) by enabling the use of TOTP tokens for users. User can now configure a TOTP token by navigating to their User Profile, selecting the 2-Factor Auth tab and following the steps to set it up with their app of choice (e.g. Google Authenticator).
Tenable.io & Tenable.sc
The Tenable.io connector now supports ingesting by asset tag and network in addition to the existing ingestion by scan functionality. This update makes the connector far more flexible, as you can now ingest large volumes of data across different scan types using a single tag.
The Tenable.sc connector has similarly been updated to also be a host-based connector. In addition to importing by asset, this connector can now leverage Queries to import vulnerabilities in to a Nucleus project using custom logic that is defined in your instance of Tenable.sc.
Both connectors have also been updated to improve the speed of vulnerability ingestion, and to ingest any additional asset information as Additional Metadata, which can be used as asset criteria in Automation rules.
Note: Tenable has decommissioned the API’s which are used for ingesting by scan in both Tenable.io and Tenable.sc. Nucleus will continue to support ingesting by scan until these scan API’s have been removed. Consequently we highly encourage customers to migrate existing vulnerability ingestion automation rules to leverage one of the new ingestion methods.
SonarQube & SonarCloud
The SonarQube and SonarCloud connectors have both been updated to allow for more configurability on import. Now when setting up the connector, you can choose which types of findings (vulnerabilities, security hotspots, bugs and/or code smells) to import in to Nucleus.
We’ve also updated the connectors to ingest far more data in to Nucleus:
- asset ingesting is now branch aware so that vulnerabilities appear in the asset’s correct branch in Nucleus
- additional asset information is now ingested as Additional Metadata, which can be used as asset criteria in Automation rules
- the Sonar vulnerability database is synchronised with Nucleus so that each vulnerability has a lot more information such as code examples and relevant links.
We’ve made some minor updates to the Qualys WAS connector to improve the speed of import. The connector now also ingests CVSSv3 scores for each vulnerability where available.
Complete list of changes and bug fixes
- NEW There is a new Microsoft Teams connector.
- NEW Tickets can be automatically closed once remediated in Nucleus
- NEW Tickets will automatically update when new instances of the same vulnerability are identified
- NEW Tickets now include a CSV file containing affect assets
- NEW Ticketing rules can be run retrospectively against all existing vulnerabilities
- NEW We now support MFA by TOTP.
- NEW The Tenable.io connector now allows import by asset tag and network.
- NEW The Tenable.sc connector now allows import by asset and query.
- NEW The Tenable.io, Tenable.sc, SonarQube and SonarCloud connectors now ingest additional asset information as Additional Metadata.
- NEW The Nucleus Custom Finding schema now supports setting a timezone in the scan date.
- NEW The Nucleus Custom Finding schema now supports setting secondary hostnames and ip addresses for host assets.
- NEW The Nucleus Custom Finding schema now supports sending HTTP requests and responses encoded as base 64.
- NEW There is now an Any vs All selector for Asset Groups for the reports Custom Vulnerability Summary, Custom Vuln Details and Executive Brief.
- UPDATE The Tenable.io and Tenable.sc connectors have been updated to ingest data more quickly.
- UPDATE The SonarQube and SonarCloud connectors are now branch aware.
- UPDATE The SonarQube and SonarCloud connectors now show more vulnerability information such as code examples and links.
- UPDATE The Qualys WAS connector has been updated to ingest data more quickly.
- UPDATE The Qualys WAS connector has been updated to ingest CVSSv3 scores where available.
- UPDATE The Executive and Technical reports now mark passed and failed compliance findings as green and red respectively.
- UPDATE Vulnerability criteria for ticketing automation rules now include vulnerability description, vulnerability solution, vulnerability discovered date, Nucleus risk score, CVE, CVSS score and RF (Recorded Future) score.
- UPDATE Querying asset information from the API now also returns container information if relevant/available.
- UPDATE The Microsoft Defender for Endpoint connector has been updated to use CVSS scores to set the severity rather than Microsoft’s custom severity.
- BUG FIX In rare circumstances certain hosts were not importing correctly from Tenable.io.
- BUG FIX In rare circumstances when creating tickets the Jira connector would time out.
- DEPRECATED Vulnerability ingestion by scan for both the Tenable.io and Tenable.sc connectors have been deprecated.