FullSODCheck
Full segregation of duty check that reports all existing violations
FullSODCheck performs a full segregation-of-duty (SoD) check across all users in the Identity
Store. The PolicyAgent evaluates every user’s current privilege set against the configured SoD
rules and records all violations it finds. The check is a reporting operation: it does not remove
or revoke any privilege assignments.
Run this workflow periodically or before compliance audits to get a complete picture of all active SoD violations in the Identity Store.
The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.
At a Glance
Name |
|
Category |
Identity Store |
Technology |
Tcl-based scheduled workflow |
LDAP object class |
|
Workflow type |
- |
Connected system / controller type |
- |
Configuration wizard |
|
Active in the factory data |
not set |
Factory data version |
7.0 |
Factory data path |
|
Prerequisites
-
SoD rules must be configured in the Identity Store.
-
The
FullSODCheck InandFullSODCheck Outchannels must be configured in the C++-based Server.
Workflow and Activities
| Step | Activity | Description | Agent | Runs after |
|---|---|---|---|---|
1 |
|
Full SOD check activity |
|
start activity |
Jobs and Agents
| Activity | Job | Agent | Operation | Input channel | Output channel |
|---|---|---|---|---|---|
|
|
|
Full Import |
|
|
Configuration Parameters
| Parameter | Default value |
|---|---|
|
full |
|
0 |
|
AssignOnly |
|
process |
|
2 |
A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order
defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent
with one input and one output channel. Agents exchange their data through files or directly through
the meta controller, so a typical workflow consists of an export activity that writes the data of the
connected system and an import activity that maps and loads that data into the Identity Store.
You start these workflows manually from the Identity Manager or attach them to a schedule.
The workflow has a single activity, FullSODCheck, which runs the PolicyAgent job of the
same name. The job reads user entries from the FullSODCheck In input channel and evaluates
each user’s privilege set against the SoD rules. Violations are written to the FullSODCheck
Out output channel. The mode is AssignOnly and the request is process.
Operation
-
You start the workflow manually from the Identity Manager or attach it to a schedule.
-
The C++-based Server starts the
FullSODCheckactivity and launches thePolicyAgentjob. -
The agent reads user entries from the Identity Store through the
FullSODCheck Ininput channel. -
For each user the configured SoD rules are evaluated against the user’s current privilege set.
-
All detected violations are written to the
FullSODCheck Outoutput channel for reporting and review. -
Privilege assignments are not modified; the workflow only records and reports violations.