4/27/2023 0 Comments Based on controlplane appVeza combines this information with metadata from other sources, like Identity Providers (Okta, AzureAD) in the Authorization Graph.īy importing their authorization metadata with OAA, organizations can leverage all the power of the Veza Platform including reporting, alerting and entitlement review workflows. This information is compiled into a JSON template and pushed to Veza using a REST API. With OAA, customers can develop their own integrations with Veza to provide the metadata on who and what makes up their custom application, along with the authorization information on what users or groups have what roles and permissions. OAA enables organizations to integrate the authorization metadata from their own unique applications directly into the Veza platform to give the same visibility into these data sources that Veza provides out-of-the-box for AWS, Azure, GCP, Snowflake and others. To enable you to truly fold all sources of sensitive data into a single control plane for authorization, there’s Veza’s Open Authorization API (OAA). No productized connector or integration could ever be available for these data sources, yet any comprehensive effort to protect an organization’s sensitive data and prevent excess privilege must include them. For example:Ī hotel chain builds a custom reservation management system, handling payment details and customer PII for more than half a million rooms.Ī technology company builds a custom portal to enable support engineers to access customer deployments.Ī financial technology company uses a software platform to give developers access to multiple databases containing sensitive and regulated information.Ī financial technology company builds a custom dashboard tool to show confidential metrics. These applications can contain protected internal data, or enable access to customer data. ![]() In fact, for many organizations, the source of their most sensitive data is their own purpose-built applications, developed over the course of years and totally unique. However, not all data lives in platforms covered by Veza’s standard integrations. To be truly effective as an authorization platform, Veza needs to be able to capture a complete picture of the sensitive data your organization holds. The connectivity problem: many sources of sensitive data are unique Visualize identity-to-data relationships for all human and machine identities in your organization.Ĭonstantly monitor for authorization misconfigurations and violations, and automate the first steps of remediation.Ĭonduct fast and effective entitlement reviews of the real permissions of users to sensitive data. ![]() As the identity-first security platform for data, Veza is focused on empowering you to answer one vital question: who can, and should, take what action on what data? To do this, Veza ingests authorization data from your IdP (Okta, Azure AD) your cloud providers (AWS, GCP, Azure), and your data assets themselves (Cloud storage buckets, Snowflake, SQL databases, SaaS apps) and normalizes this complex metadata into “effective permissions”: who can create, read, update, delete your sensitive data.īy connecting your data sources to Veza’s authorization platform, you can:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |