2023.1.16

Workflows

  • Improved loading speed for the main Workflows landing page, in addition to overall workflows performance enhancements. A progress indicator is now shown when additional certifications are loading in the background.

Insights

  • Inactive (disabled) users are no longer included in the total count of Identities that can circumvent MFA.

  • The Alerts panel is now located under the Remediation section on the main navigation menu.

  • The Rules panel now shows the email address of each rule's creator.

Integrations

  • New Veza-distributed OAA integrations are now available for sourcing users and roles from Oracle Fusion Cloud and Coupa.

Platform

  • As an alternative to temporarily disabling API Keys, unused tokens can now be permanently removed with DELETE /api/preview/keys/{id}.

  • Authorization Graph searches can now specify excluded entity types (only return results without a relationship to the chosen entity).

  • For improved Authorization Graph readability, the Object column is no longer shown when searching relationships for Salesforce Accounts.

  • Google Cloud KMS and BigQuery role bindings have an additional property listing the role permissions (visible when querying user->role binding).

  • Partial results are now returned when a search returns more data than Authorization Graph can render (before, this resulted in an error message). Users are now reminded to apply filters to constrain the search to a manageable size when viewing incomplete results.

  • Violations are re-enabled as an Authorization Graph search option. Fewer built-in assessments are now marked as violations by default.

  • When using Explain Effective Permissions, you can now change the selected principal (the Explain modal may not always open on the expected source or destination).

Bug Fixes

  • Query Builder: Fixed an issue where adding a Grouping Entity Limit could cause the search to return no results.

  • Integrations: Added | to allowed characters in AWS account names (previously this resulted in an error when adding the account to Veza).

Last updated