4.7.2

4.7.1

Fixed an issue that prevented applying policysets to labels, when the label's name contained a colon character
console.api_url configuration is now used in Quick Install, if set. (This optional config is only needed for deployments where Sensors access the Console via a different hostname than browsers)

The default TLS version has been bumped to 1.2. See the https guide for customization options.

An Integrations page with the ability to forward alerts to Splunk and Elasticsearch
New widget for easily filtering Incidents and Resources with a point-and-click interface
Administrators may now delete users and roles
Many enhancements to the Policy editor including the ability to duplicate Policy Sets

Policy Editor supports more advanced configuration options including alert batching and alert labels
When assigning a policy set to a sensor or group of sensors, you may now assign it to all available labels on your sensor
Users may select from multiple Capsule8 Content versions when creating a new Policy Set
Resources can be filtered and grouped
Package installations (but not Docker images) now add a file named capsule8-console.yaml.example to the /etc/capsule8 directory. This file contains console configuration keys, examples, and explanatory text
Users who have configured LDAP may now additionally sign in with their native Capsule8 accounts
Active Directory backed LDAP logins are now supported.
Oracle Linux 6 and 7 packages are now available from Packagecloud
More comprehensive help text when capsule8-console --help is run
Global Policy Lists have moved from the Policy Editor view to the Policy Set view

Connected/disconnected state of resources is accurately reflected
Resolved an issue causing "Unable to connect to the server" error messages for some users
Fixed text copy when resolving alerts

When creating a Custom Policy with a newFileExec policy type, the "Quarantine" response action is not available. Workaround: After saving and reopening the Custom Policy, Quarantine becomes available
The Custom Policy editor does not allow creation of policies using the UI alone. Workaround: When creating a Custom Policy, paste a yaml policy before clicking "Switch to UI Editor BETA"