We’re chuffed to announce the next update to our Amazon Web Services connector, Amazon ECR! With the release of Amazon ECR support, you can synchronize container image repositories from your AWS accounts, as well as ingest vulnerabilities that have been found.
To get started simply add the Amazon ECR Managed Policy AmazonEC2ContainerRegistryReadOnly to any cross-account roles that you’ve setup in the AWS connector. You’ll then be able to use your existing AWS connectors to synchronize repositories by creating Asset Sync Rules, and to ingest vulnerabilities by Importing via Connector or creating Vulnerability Ingest Rules.
When you’ve ingested data in to your project, you’ll immediately notice that all additional asset metadata is set for the asset, which can be further used in the Nucleus Automation Engine. You can also swap between different images within the same repository.
“Great things are not done by impulse, but by a series of small things brought together” – Vincent van Gogh
In this release we’ve made a small change to the way that filtering works on the Asset Management page, and we think you’re going to love it! Now, if you apply filters, click on an asset to view it, and then click back to the Asset Management page, the filters you applied will persist!
NEW The Amazon Web Services connector now has support for synchronizing Amazon ECR repositories and ingesting vulnerabilities.
NEW Asset filters now persist in the asset management page after navigating to individual assets and back.
BUG FIX In a limited set of situations imports from Qualys via group would not run.
BUG FIX In certain situations invalid asset criticality’s could be set.
BUG FIX In Safari some text would not fit the screen.
BUG FIX Some asset group names would impact asset category filters on the Asset Management page.
BUG FIX In certain situations scans could not be imported by query from Tenable.sc.
BUG FIX Adding assets to custom findings now works as expected.
BUG FIX Importing images from PrismaCloud without registries set now omits the registry.
BUG FIX Dates for vulnerabilities now always reflect the local timezone.
BUG FIX In certain circumstances importing scans from AWS services resulted in an unhandled error.Read More
As organizations mature their vulnerability management programs, it has become increasingly common (and necessary) to set and track Service Level Agreements (SLAs) for how and when a vulnerability is treated. This can be particularly helpful in large organizations, where security policies define expected remediation effort and timelines for different classes of vulnerabilities in different situations.
In this release we’re introducing our first foray into SLAs, Vulnerability Due Dates. Vulnerability Due Dates allow you to set when remediation efforts on vulnerabilities must be completed by, and track and report on vulnerabilities that are approaching their due date or have exceeded that date.
Using the Nucleus Automation Engine, you can create vulnerability processing rules which, based on all of the available vulnerability and asset criteria, enable you to automatically set due dates for vulnerabilities. Rules can be configured to set the due date as a set number of days, weeks or months from the time of ingestion, or the vulnerability’s discovered date.
Once set, you can identify and measure vulnerabilities in the Active Vulnerabilities page by due date, including whether a due date is not set, when a vulnerability is due within days, weeks or months, and when vulnerabilities are overdue!
This release we’re excited to announce a new connector with Assetnote! Assetnote is an Attack Surface Management platform that identifies an organisations external facing systems and continuously monitors those systems for exploitable vulnerabilities.
We’ve worked closely with the team at Assetnote to create a connector that integrates with the Assetnote Notification Pipeline so that when assets and vulnerabilities are discovered across your environment, they surface in to your Nucleus project(s) in real time. When combined with the Nucleus Automation engine, you can create powerful and intelligent rules to suit your specific use case.
Read about setting up the Assetnote connector here.
The Active Vulnerabilities page has received a face lift to ensure that you are able to identify and track the vulnerabilities that matter most. We’ve introduced an updated Quick Filter pane at the top of the page that shows you rolled up numbers of vulnerabilities based on different tracked metrics. Using these filters, in one click you can drill down to the vulnerabilities that are most important to you.
We've also added the ability to multi-select vulnerabilities on the Active Vulnerabilities list, as well as a Modify menu to bulk update attributes of vulnerabilities. Currently we only support setting due dates in bulk, but you should be on the lookout for other actions such as setting: severity, status, and exploitability in bulk in the future as well.
Additionally, we’ve also updated the Source column with vulnerability source tool icons to make it easier for you to quickly identify where a vulnerability came from.
We added a Certificate Summary view to the Assets menu to make it easy to view and report on certificates. This view includes all the usual filters for quick drilldowns. Plus, you can export to a downloadable report in one click.
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!
There are a few improvements to the Nucleus Custom File Schema, making it easier to get asset and finding data in to Nucleus:
The API has also been updated to return a container image’s tag, repository URL, digest and distro when querying for assets.
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).
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.
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:
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.