Currently, we can only run collection on the full data set. It would be helpful to allow for us to specify a specific attribute to filter the collection. This would allow for a few things:

- If IDM detects a change on a user via a connector, it could toggle IG to collect that specific account to get the updates into the governance catalog
- In transfer and other use cases where changes are expected, we could go get updates from all systems for that specific user's accounts
- We could integrate with a SIEM to use audit records from systems to toggle IG to update a specific record when an audit record is forwarded to the SIEM
- In the event of a termination, we could collect that user's information from various systems
- For fulfillment activities, we could toggle an immediate collection of that singular account after the fulfillment activity has completely to verify it immediately

This would be different from collecting via a change log, because this would be a method that could be toggled by either internal IG processes (fulfillment completion) or external processes (SIEM, IDM, etc). Currently, we would have to do a full collection, which, depending on the size of the data set, is a heavy process. If we could have a way to call "targeted collection" and provide one or more parameters to filter the results of the collection (such as adding a "WHERE" clause on a SQL statement), it would shrink the overall result set down to just that targeted account or permission.

by: Robert I. | over a year ago | Integrations