Separation of Duties (SoD) and Responsibilities

Separation of duties reduces risk by ensuring no single individual controls all critical functions or access within a system.

va. use_z = True

#selection at the end -add back the deselecte

mirror_ob.select= 1 modifier_ob.select=1 bpy.context.scene.obiertc print("c..

Separation of duties (SoD) means that no individual person can complete an entire trusted action or process alone.

The concept of SoD is to reduce chances of fraud within sensitive parts of the organization. The classic example is bifurcated purchasing: the purchasing manager must sign the purchase order (PO) but cannot issue a check; the accountant can issue a check but only with a PO signed by a manager. Larger payments (which exceed predefined limits) might further require approval by a more senior manager, as would unusual payment processing and transmission needs. This type of SoD, enforced by access control (AC) mechanisms in the financial applications platforms and the databases they rely on, are part of defending against whaling attacks, which are phishing attacks that attempt to trick highly placed officials into authorizing large fund wire transfers to previously unknown entities.

Implementing a SoD control system starts with workflow and task design. Ideally this identifies critical steps that require the approval of a second or third person. This requires control flows: information flowing to the approver, and the approval, rejection, or referral of the action on to yet higher authorities. Those control loops should be closely examined to ensure they are correctly designed. Then, the right mix of AC technologies can be used to support their implementation.