Skip to main content

Release Notes for Styra DAS

This page describes the release notes for Styra DAS delivered in October 2021.

Release Summary

Styra is built on the Open Policy Agent (OPA), a popular and widely deployed open source project developed by the founders of Styra. With primary credibility for the underlying technology, the Styra team and technology are both proven in production across verticals. Styra enables enterprises to define, enforce, validate, and continually monitor security, compliance and operational policies across the cloud-native application stack. Styra has reinvented the authorization solutions to mitigate customer risk, and reinforce commitment to trust and transparency in safeguarding customers’ data. Styra’s Declarative Authorization Service (DAS) is a sophisticated management plane that provides context-based guardrails, built from a graphical policy library to mitigate risk, reduce human error and accelerate development. Styra makes it possible for enterprises to implement policy-as-code controls and to prove their effectiveness to both internal and external security and compliance audiences.

October 19, 2021

This Styra DAS 20211019 release delivers the following new enhancements and list of fixed issues.

New Features and Enhancements

This section describes the new enhancements in Styra DAS 20211019.


  • This release adds HTTPS data source to DAS systems which allows you to link a JSON file as a new data source.

  • The Workspace level introduces All, Added, and Managed tabs under the Settings pane to manage API tokens and simplify the readability. Managed tokens are created by Styra on behalf of the user and are for system-specific use (such as, connecting an OPA to a system) or for a system type to manage its assets.


  • Policy editor can now autocomplete data sources for systems, stacks, libraries, and so on.

Issues Fixed

This section describes the issues fixed in Styra DAS 20211019.


  • Fixed the errors and warnings in OpenAPI v2 specification.


  • Fixed an issue in the Git synchronization logic where files failed to synchronize when the path in the Git configuration for the repository was set to indicate the root (dot (.)) of the repository.


  • The decision log mask for Envoy systems was augmented to remove the authorization header. This ensured the following two paths was automatically purged from the decision logs uploaded to DAS from OPAs linked to Envoy systems.



October 12, 2021

This Styra DAS 20211012 release delivers the following new enhancements.

New Features and Enhancements

This section describes the new enhancements in Styra DAS 20211012.


  • Starting with release, the JSON request body is added to the User Activity log for DAS configuration changes. The feature flag ACTIVITY_GC_HISTORY is also added to the extend log capture period to four weeks and the online API activity API is updated.


  • This release allows you to edit your data source through the Settings button.

  • Policy editor can now autocomplete any system’s JSON data sources.


  • Styra DAS provides new Monitoring Integrations under Workspace >> Settings. Select Add data metrics targets to configure the DAS to periodically send the systems and time-series metrics to remote Datadog and SignalFx targets.


  • Starting with this release, Mesh system types are released: Istio, Kong Mesh, and Kuma.

October 5, 2021

This Styra DAS 20211005 release delivers the following security updates, new enhancements, and list of fixed issues.

Security Updates

  • Updated Docker images for Styra CLI, datasources-agent, styra-local-plane, and Git Relay to incorporate critical security updates to packages openssl/libcrypto and apk-tools.

New Features and Enhancements

This section describes the new enhancement in Styra DAS 20211005.


  • Decisions can now be configured to stream from DAS to a remote S3 bucket. This enables long-term decision archival for audits or compliance purposes.

Issues Fixed

This section describes the issue fixed in Styra DAS 20211005.


  • Fixed an issue in the UI, where decisions made on systems with coarse-resolution clocks show up as Missing latency. These decisions now accurately show that their latency is less than one millisecond.