Strivus

Strivus 6.1.0 Release Notes

New Features Strivus 6.1.0 introduces feature updates, security updates/fixes, migration guidance from 6.0.1 to 6.1.0; and updated documentation. The features impacted are Usage Metrics, Licensing Model Changes, User Access control, Terraform Client Credential Provider Login, and Configuration Auditing.

Usage Metrics and Licensing Model Changes

Strivus 6.1.0 introduces a new metrics data panel on the UI homepage which displays your previous and current month's average daily usage. In addition to the raw data count, the UI will automatically warn you when your average daily usage is 80% of the quota for your license. In order to use Strivus, you will need to configure a valid Prometheus instance. You can either configure the helm chart to use the URL of an existing Prometheus, or to have Strivus set it up for you.

User Access Control

Strivus 6.1.0 introduces attribute-based user access control for permissions. Whenever a user successfully logs into the application, they will be placed into a pending approval state with no permissions. An existing user with the "users" permissions can use the new User Management page in the UI. Existing Strivus 6.0 (or prior) users will need to log in again and be granted permissions by a user with the User Management permission. To setup the new permissions, an admin will need to have their permissions configured by a Kubernetes administrator in the database. They will need to be granted the "users" and "read" permissions so they can manage permissions for any additional user through the User Management page.

Terraform Client Credential Provider Login

Added support for provider login using a client ID and client secret for admin service account privileges. This client and its issuer will need to be specified in the new adminClientBinding (in the format of |) for security. The provider continues to support basic credential login for the primary identity provider.

Configuration Auditing

Audit recording has been added for significant events such as creation, deletion, and updating of configurations, user permission changes, and installing and uninstalling packs. The audit records the ID and email of the performing user, the ID of the object they are operating on, and an event message indicating what operation the action took.

Updates, Fixes, and Security

• Terraform now allows categorizer resource to specify prefilter and postfiler stages
• Processors are now available in Streams Studios
• Removed certain inputs and processors (file, awk) that may pose a security risk
• Ensure encryption of sensitive data across all API endpoints; secured nil pointers.
• Fixed replays of files no longer in data lake always remaining in queued state
• Added new Access Logs parameter in the helm chart to enable route logging
• Added helm chart signature files for validation
• Beta input support for Crowdstrike Falcon EDR streams

Migration Guide (6.0.1 -> 6.1.0)

1. Upgrade Helm values before rollout:

• Set controller.oidc.adminClientBindings for each automation/service account client.
• Set pipeline.jackknife.url to your intended fixed Jackknife endpoint.
• Verify controller.metrics.prometheusURL points to a reachable Prometheus instance.

2. Validate automation and Terraform authentication:

• If using client credentials mode, ensure provider client_id/client_secret correspond to a configured adminClientBindings entry.
• Re-run Terraform plan/apply and confirm API authentication succeeds.

3. Run post-upgrade smoke checks:

• Confirm users can authenticate and access expected pages based on permission grants.
• Confirm pipeline deploy/update succeeds with current config set.
• Confirm usage metrics and quota banners load from Prometheus-backed metrics.

Roadmap: Coming in 6.1.1 and 6.2, planned features include improvements to Strivus collectors, dedicated streams, a new pipeline summary page, and pipeline error correlation, In addition, key integration initiatives include Azure marketplace integration, MSFT Sentinel output definition, UDM mapping packs planned, AWS environment and resource integrations, SIEM integration(s), continued updates to multi-data model support for data normalization, and multi-cloud compatibility.