Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 4 of 5

Remediation vs mitigation

10 min

Listen to this lesson

0:00 / 6:02

Every reported risk needs a decision. There are two kinds of answer. Remediation removes the risk: change the role, change the assignment, or split the task. Mitigation accepts that the access stays, and puts a compensating control in place that would detect or prevent misuse. Remediation is the default; mitigation is the exception that needs a reason.

  1. Is the conflict inside a single role?Yes → remediate by redesigning the role · No → next question
  2. Does the user really need both functions for their job?No → remediate by removing an assignment · Yes → next question
  3. Can the work be split between two people?Yes → remediate by reassigning tasks · No → mitigate
  4. Is there an effective control that would catch misuse?Yes → assign the mitigating control with an owner · No → design one, or escalate to the risk owner
Remediate first; mitigate only when the business genuinely needs the combination.
The Sign-Off Table · thesignofftable.com/academy/sap-sec-204

Remediation options

  • Role redesign: remove the conflicting catalog or transaction from a role, or split a role into two task-based roles.
  • Assignment change: remove the role that is no longer needed, typical after a job change or temporary cover.
  • Organizational restriction: sometimes the conflict disappears when the functions apply to different units, for example supplier maintenance for 1810 only and payments for 1710 only; check that your rule set analyzes organizational values before relying on this.
  • Process change: move a task to a different team, such as central master data maintenance.

Mitigating controls

A mitigating control is a documented control that compensates for the accepted risk. In SAP Access Control, controls live in a mitigating control catalog and are assigned to users or roles for specific risks, usually with a validity period; analysis can then show the risk as mitigated. A good control is specific, performed by someone independent of the user, done at a fixed frequency, and leaves evidence.

A mitigating control lives in a catalog and is assigned for a specific risk to a user or role, with an independent performer and a validity period.
The Sign-Off Table · thesignofftable.com/academy/sap-sec-204
Control elementContoso example for a supplier master plus payment conflict
Risk coveredP001, maintain fictitious supplier and process payment, for one AP lead at Contoso Parts Distribution (1810)
ControlMonthly review of all supplier creations and bank detail changes for 1810 against supporting documents
Performed byThe 1810 controller, who has no AP or master data access
Frequency and evidenceMonthly; signed review report with any follow-ups, stored with the control
ValidityOne year, then re-approved by the risk owner

A mitigating control that would survive an audit test.

Mitigation is most often justified in small teams. Contoso Parts Distribution has two people in finance; strict segregation would need a third. Dan, as risk owner, accepts the conflict for the AP lead there, with the monthly review by the controller. In Detroit, with a team of twelve, the same conflict is remediated instead.

Remove the accessLow need, lower risk: clean up the assignment in the next review.
Mitigate, light touchReal need, lower risk: a periodic review control is enough.
Remediate nowHigh risk with no real need: remove the access before go-live.
Mitigate with a strong controlHigh risk the business cannot avoid: an independent, frequent, evidenced control approved by the risk owner.
Risk level and business need together decide the treatment.
The Sign-Off Table · thesignofftable.com/academy/sap-sec-204

Document the decision

Whichever treatment is chosen, the decision itself is evidence. For each open risk, Nadia records the risk, the user or role, the treatment chosen, who decided and when, and, for mitigation, which control was assigned until which date. When auditors later ask why Contoso Parts Distribution's AP lead still holds a conflict, the answer is a record, not a recollection.

Each reported risk ends in a recorded treatment; a mitigation expires or fails if the control is not performed, and the risk is open again.
The Sign-Off Table · thesignofftable.com/academy/sap-sec-204

What would you do?

Contoso's Toledo plant (1810) has one warehouse supervisor who both posts goods issues and runs physical inventory adjustments, flagged as a high risk. There is no second supervisor on the night shift. Luis asks whether this blocks cutover. What is the best treatment?

Key points
  • Remediation removes the risk; mitigation accepts it with a compensating control.
  • Remediate first: role redesign, assignment change, organizational split or process change.
  • A mitigating control needs an independent performer, a frequency, evidence and a validity period.
  • Mitigation is common in small teams; the risk owner approves it.
  • An assigned control that is not performed hides the risk instead of managing it.

Check your understanding · not graded

Lesson check

  1. 1. What is the difference between remediation and mitigation?

  2. 2. Who should perform a mitigating control for an AP lead's conflict?

  3. 3. Why can an unperformed mitigating control be worse than no control?

  4. 4. When is mitigation most often justified?