Releases: deep-security/smartcheck-helm
1.1.2
1.1.1
1.1.0
Features
New in this major release of Deep Security Smart Check:
- Detect vulnerabilities in applications installed outside of the package manager
- Detect secrets and keys using pre-configured rulesets
- Scan for suspicious or unwanted files using custom queries
Changelog
- Enhance consistency, stability and usability of admin console
- Identify vulnerabilities by CVE ID instead of vendor-specific advisories
- Improve error handling for invalid repos
- Fix race condition that caused registry sync to fail
- Miscellaneous fixes and improvements
1.0.9
Changelog
- Add icons for navigation menu items
- Show image details instead of scan history when image is clicked in the image list
- Upgrade material-ui to v3.1.1
- Add better handling for AWS registry errors
- Preserve filter values when registries are edited
- UI fixups
1.0.8-aws-container-marketplace
AWS Marketplace for Containers
This release of Deep Security Smart Check is intended only for AWS Marketplace for Containers.
1.0.8
Highlighted commits in this release
- Ensure setup wizard automatically starts a scan when the appropriate option is selected
- Fix permissions issue that prevents saving of registry after edits
- Remove the
Danger Zone
for registries - Update dashboard after editing registry
1.0.7
API change notice
Today we removed views from Deep Security Smart Check. As we mentioned in the release notes for v1.0.6, we're doing this because views were adding a fair amount of complexity for a value that customers weren't really seeing.
You can still see results and status across multiple registries in the Overview page, and view status details have been replaced with registry status details. You can selectively include registry content using filters at the registry level, and you can perform bulk scans of registries. The daily view scan has been replaced with a daily registry scan.
The API endpoints for views still exist, but for this release they will return a 410 Gone
response with a Sunset
header and a Link rel="sunset"
header with a link to the original release notes and deprecation plan.
In an upcoming release of Deep Security Smart Check, we will be removing the view API endpoints completely.
We'll always try to keep APIs around as long as possible, but when they don't make sense any more, we'll use the same process to sunset and remove them in an orderly fashion so that you know what's going on.
If you have any questions or comments on this process, please get in touch! We're always happy to hear from our customers.
Highlighted commits in this release
- Return
410 Gone
response from view endpoints
1.0.6
API change notice
We're simplifying the data model for Deep Security Smart Check. In the initial release, we thought it would be useful to have "views" that could bring together status across multiple registries, with interesting and sophisticated filtering. As it turns out, this is just confusing. Customers didn't find it helpful, and the additional complexity of supporting views in the product was slowing us down.
In an upcoming release, we will be removing views entirely from the product API and user interface.
You will still be able to see results and status across multiple registries in the Overview page, and view status details will be replaced with registry status details. You will be able to selectively include registry content using filters at the registry level. You will be able to perform bulk scans of registries, and the daily view scan will be replaced with a daily registry scan.
Today, we're updating the view API endpoints to report a sunset date of September 15th, 2018, indicating that they could be removed at any time after that date. We have also updated the API documentation to show that these APIs are now deprecated.
In the future, we'll continue to use this process of publishing a release note, updating the API specification, and including sunset details in the API response before we remove any API methods. It's a good idea to have your client code check for the Sunset
response header in all API calls and to look for the Link rel="sunset"
response header for a link to a human-readable note like this one.
We'll provide another update as we make progress on the transition to let you know when the replacement APIs are available.
If you have any questions or comments on this process, please get in touch! We're always happy to hear from our customers.
Highlighted commits in this release
- Report sunset date for views API endpoints
1.0.5
Highlighted commits in this release
- Fix crash in licensing module for online license updates
- Implement layer caching for malware scans
- Support VMWare Harbor registry API
- Add image ID to the item list on the Scan History page
- Display vendor CVE information in a new tab