Energy and chemicals
Strengthening SAP GRC
SAP GRC decided which payments needed which approvals. A fingerprint at the approval itself decided whether the human releasing the money was the one the rules intended.
- Customer
- Sasol, South Africa
- SAP systems, 27 countries
- 8
“SAP GRC software does a great job of defining bank payment amounts that authorised approvers must confirm. GRC’s capabilities stop when the approver uses somebody else’s password to approve the payment via SAP Digital Signature. Adding bioLock as the second biometric factor gives Sasol the peace of mind to guarantee that only the intended SAP user, beyond any reasonable doubt, can confirm payment.”
The customer
Sasol is a global chemicals and energy company, launched in South Africa more than seventy years ago and listed on both the Johannesburg and New York stock exchanges. It employs over 30,000 people, operates in 27 countries, runs eight SAP systems and spans many separate business units.
Its Enterprise Risk Management framework sets the foundation for those businesses to manage risk in a standardized, systematic way. This is one of the controls inside it.
The situation
Sasol set out to reduce the risk in its bank payment approvals and to enforce mandatory dual approval in the payment process.
The concern was specific rather than theoretical. A user could bypass their GRC role by using a colleague’s password. Once an approval can be given by somebody other than the approver, the controls still appear to have been satisfied, and the door to corruption and collusion is open.
The challenge
- Enforce dual approval on bank payments, so no single human can release funds alone
- Prevent an authorized user from circumventing the intended payment controls with a colleague’s password
- Apply the same protection to the GRC rules themselves, not only to the payments they govern
- Require tamper-proof logging of all restricted activity, including failed and unauthorized attempts
- Reinforce Segregation of Duties
- Record who approved, rather than which account approved
What was implemented
Biometric verification was built directly into the approval step.
- SAP GRC controls trigger a custom bioLock approval to release a bank payment, through transaction BNK_APP
- The user signs in with username and password, then re-confirms that sign-off with a fingerprint: the password and the finger together establish who is really there
- Changing the responsibility rules themselves, in OOCU_RESP, requires two authorized users to provide biometric credentials, so the four-eyes principle covers the rules as well as the money
- The risk team receives an immediate email alert on an anomaly, so it can act while the attempt is still fresh
- Every activity is recorded in a log file against a biometrically identified user
- The bioLock software was implemented by authorized realtime partner Linx/AS Africa
The outcome
- SAP GRC continues to define which payments need which approvals. bioLock establishes who actually gave them
- A colleague’s password no longer releases a payment, because the password is not the last thing the process asks for
- Confirming with a fingerprint is faster than re-entering credentials, so the control adds assurance without adding friction
- Every protected approval carries the verified individual into the record