Data Access Governance uses the following components in Identity Governance:
Identity Governance Tomcat Application: This is the primary Identity Governance application that provides the management interface along with collection and review of defined identity and application data.
Database: Identity Governance makes use of its own set of databases for management and storage of collected data.
Collector Templates: Collector templates provide the interface for collection of data specific to application endpoints. Data Access Governance provides a custom file system access collector template for use with a File Reporter data store.
Data Access Governance also requires an understanding of the following Identity Governance constructs:
Identity Governance Catalog: The catalog is the set of identities and permissions collected and curated via Identity Governance.
Identity Sources: These are the sources where identities originate such as Active Directory.
Collectors: Collectors are configured instances of collector templates defined within an Identity Governance Application or identity source. Collectors are responsible for the retrieval of the actual data in identity and application endpoints.
Applications: Applications provide context for one or more collectors and generally reference a specific type of endpoint, such as a database or web service.
Permissions: a permission in Identity Governance is like an entitlement as defined in Identity Manager and defines a resource right held by one or more identities. Each permission may have metadata attributes associated with it. Data Access Governance provides a set of custom Permission Attributes for use with the file system access collector template.