Veza Integrations
Veza Integrations terms and definitions in the Veza platform.
Custom Properties
When configuring an integration, use this tab to specify additional attributes on entities to collect, by providing the name and type of attribute Veza will gather. For example, if an organization uses custom security attributes for Azure AD or Okta (such as deskNumber), these custom properties can be enabled when adding the integration, and used to filter results for search and access reviews.
Related documentation: Custom Properties
Data Source
Data Sources are the individual resources (SaaS apps, data lakes, databases, etc.) from which Veza extracts authorization metadata.
Related documentation: Data Source
Integration
A connector built directly into Veza, for ingesting data from external systems. Each inbound integration represents an inbound connection to a cloud provider, identity provider, or external application. Some integrations support activity monitoring, audit logs, and lifecycle Management (when granted additional permissions). Each integration may have multiple child discoverers and data sources representing services and resources. Veza Actions are outbound integrations for triggering actions in external systems.
Related documentation: Integration
Limit Integration Services
Option to globally prevent discovery of all resources for a provider service (for example, AWS EC2).
Related documentation: Limit Integration Services
Mapping Configuration
Option when configuring an Identity Provider integration, allowing users to define cross-service connections between Identity Provider accounts and local accounts in other integrated systems (if Veza cannot automatically detect the connection).
Related documentation: Mapping Configuration
Monitoring
Veza Activity Monitoring features provide insight into resource and privilege utilization for your users. These include Overprovisioned Access Scores and special reports leveraging cloud provider audit logs.
Related documentation: Monitoring
OAA Integration (Community)
An Open Authorization API integration built by Veza, a customer, or the open-source community that is available in our community GitHub repository.
Related documentation: OAA Integration (Community)
OAA Integration (Customer)
An Open Authorization API integration built by a customer for one of their proprietary systems that is not published to the public repository.
Related documentation: OAA Integration (Customer)
Open Authorization API
An Open Source framework for adding off-the-shelf or in-house-developed proprietary applications and identity providers to the Veza graph.
Related documentation: Open Authorization API
Resource Inclusion and Exclusion Lists
Option when configuring an integration, setting limits on the individual resources Veza will attempt to extract and parse (for example, AWS S3 Bucket).
Related documentation: Resource Inclusion and Exclusion Lists
Veza Action
An integration built directly into Veza for sending data to external systems and enabling downstream processes around Veza alerts and access reviewer actions. You can configure generic webhooks, create Jira issues, or ServiceNow tickets with Veza Actions, or enable Slack and email notifications.
Related documentation: Veza Action
Veza Cloud Connector
A Veza-provided VM image or docker container to enable connections to systems without APIs, or without publicly reachable APIs.
Related documentation: Veza Cloud Connector
Worker
Workers are the components that find and catalog the authorization metadata and Data Source components of the integration.
Related documentation: Worker
Last updated
Was this helpful?