Set up segregation of duties [AX 2012]
Updated: February 1, 2013
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Security or policies may require that specific tasks be performed by different users. For example, you might not want the same person both to acknowledge the receipt of goods and to process payment to the vendor. This concept is named segregation of duties.
Segregation of duties helps you reduce the risk of fraud, and it also helps you detect errors or irregularities. You can also use segregation of duties to enforce internal control policies.
In Microsoft Dynamics AX, when two duties in the same role conflict, or when a user is assigned to two roles that contain conflicting duties, the conflict is logged. The security administrator must approve or reject each assignment that causes a conflict.
For duties that are typically separated, separate sample roles and default duties are included with Microsoft Dynamics AX. By default, no rules are set up for segregation of duties.
Compliance with the rules for segregation of duties is not verified when you create rules. Therefore, you can create a rule that causes existing user role assignments to conflict. You can also create a rule that causes an existing role definition to have a conflict. You must validate compliance manually after you create new rules. For more information about how to identify and resolve conflicts, see Identify and resolve conflicts in segregation of duties.
Use the following procedure to set up a rule for segregation of duties.
Click System administration > Setup > Security > Segregation of duties > Segregation of duties rules.
Enter a name for the rule.
Select the first duty that is controlled by the rule.
Select the second duty that is controlled by the rule.
Select the severity of the risk that occurs when the same user or role performs both duties.
Enter a description of the security risk.
Enter a description of the actions that you take to mitigate the security risk. For example, you can mitigate the risk by conducting more detailed reviews of the process, by conducting a monthly managerial review, or by sharing resources with other departments.
Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).