Distributing workflow through Guardium groups
Using the receiver group option, define a single Compliance Workflow audit process that sends different results to different Guardium users based on a pre-defined, custom mapping.
About this task
Setup a single audit process and distribute the appropriate results to the appropriate manager. This process saves time as you do not have to create separate audit processes for separate receivers.
IBM® Guardium®’s Compliance Workflow Automation automatically delivers reports, classification results, and security assessment results to Guardium users on a scheduled basis. Result receivers can be defined as Guardium users, Guardium roles, or user groups.
For example, consider a large organization that has fifteen DBA managers. These managers need to review the activities for the DBAs they manage and not view the activities of the other manager’s DBAs. One solution is to setup fifteen separate audit processes; one for each manager. This solution takes time to configure and it is difficult to manage. Each audit process needs to be scheduled separately and any global change needs to be made individually for all fifteen audit processes.
However, you can use the user group distribution method to set up a single audit process and distributes the appropriate results to each manager based on a manager mapping or DBA mapping. This process requires more upfront configuration but reduces to maintenance time. Only one audit process needs to be scheduled and changes need to be only applied in one location.
You need to map users to the data elements within Guardium that forms the basis for report distribution. The example that is used in this document is based on objects, but you can apply these concepts with any data element within Guardium.
For example, three users have responsibility over three different sets of tables based on audit requirements (PCI, HIPPA, and CCI) within a database server, as follows:
User | Table or Object |
---|---|
User01 | db2inst1.cc_numbers |
User01 | db2inst1.ccn |
User02 | db2inst1.ADDRESSES |
User02 | db2inst1.SSN_NUMBERS |
User02 | db2inst1.G_CUSTOMERS |
User02 | db2inst1.G_EMPLOYEES |
User02 | db2inst1.G_FUNDS |
User03 | db2inst1.doctor |
User03 | db2inst1.medicare |
User03 | db2inst1.med_history |
This table must be added as a custom table within Guardium, either manually or through a data upload. The following steps demonstrate how to create a custom table manually.