This release increases support for searching and filtering for assets in projects. The changes aim to increase functionality and support capabilities required for an upcoming UI release, however also add capability from an API centric standpoint as well.
New features
The _search endpoint filtering capabilities have been increased to support the new fields: name , static_asset, last_scanned_at, and registry
The referenced_ip filter has been extended to support contains
A new POST/filters endpoint has been added, which returns filters in an identical way as the GET endpoint
This endpoint adds the ability to add filters the same way as for the _search endpoint. This enables the ability to show accurate filter options and counts when assets are filtered
The GET and POST/filters endpoints have been extended to support the new fields: name, static_asset, technology_name, last_scanned_at and registry
A new filter option called quick_search has been added to the _search endpoint, see example below. This fields allows for wildcard searches for assets across the fields name, ip, and technology
{"quick_search": {"search": <VALUE>}}
Other updates
Validation has been added for cursor input for the /rules endpoints
