Solutions

Solution area 02

Segregation of Duties separates the accounts.
It cannot separate the humans.

One person can create the purchase order, approve it and release the payment, as long as they can reach a second account. bioLock verifies the human at each step, so the rule you wrote is the rule that actually holds.

SAP GRC sets the rule. The fingerprint establishes who kept it.

The control was never wrong. It was applied to the wrong human.

Internal controls in SAP are enforced against accounts, and accounts are reached with knowledge: a password. Anything protected by knowledge alone can be passed around.

Unauthorized financial activity and Segregation of Duties violations by insiders are among the most dangerous threats an organization faces, and enterprise systems are often the low-hanging fruit.

A password lent during leave

One human quietly holds both sides of a control, and the log shows two accounts doing exactly what the rule intended.

A screen left unlocked

Whoever sits down next inherits an approval right that was never theirs.

Work under a supervisor's profile

A junior administrator does the work and the system records the supervisor.

Where standard SAP security stops

SAP GRC manages internal controls. It defines conflicting duties, analyzes risk, and keeps the accounts that must stay apart from being held by one user.

SAP answers this

Are these conflicting duties held by separate accounts?

bioLock answers this

Is there a separate human behind each of those accounts?

The moment a credential moves between two people, the separation exists on paper and not in the room.

Your SAP system Payments, vendors, journals
SAP GRC controls Which duties must stay apart
bioLock Who is on each side of the control

A layer inside SAP, not a product beside it

How bioLock closes it

bioLock adds identity to the control, at the moment the control is exercised.

01

The sensitive step asks for the human

Creating the vendor, approving the invoice, releasing the payment: whichever steps must stay apart, each one can require verification.

02

Allow lists decide who may be verified

A function can be restricted to a named group, so even a user whose SAP profile would permit the action is refused unless bioLock has invited them.

03

Dual confirmation enforces four eyes

Where a transaction must be approved by two humans, bioLock can require two separate verifications, from two different people, before it proceeds.

04

Thresholds trigger the check

A field value can carry the rule, so a transaction above an agreed amount requires re-authentication while routine work is untouched.

05

Everything is recorded

Including refused attempts, with the identified human named next to the SAP user ID in a tamper-proof log that can be handed to an auditor.

bioLock · SAP GRC

The control, as designed

GRC keeps the two duties on separate accounts.

Create vendorA. JONESPermitted
Release paymentT. SMITHPermitted

Only invited humans pass

The profile permits it. The allow list decides.

Thomas SmithOn the listAccepted
Joe MillerNot on the listRefused

Four eyes, two humans

One verification is not enough on this step.

First approverVerifiedAccepted
Second approverAwaitingRequired

Above the threshold

Routine work is untouched. This one is not routine.

4,200.00 EURBelow thresholdNo check
480,000.00 EURAbove thresholdVerify

Handed to the auditor

The human beside the account, refusals included.

Thomas SmithReleased paymentAllowed
Joe MillerAttempted releaseRefused

What you can protect

Start with the steps where a borrowed credential would be worth the most, and extend from there.

  • Vendor creation and vendor bank detail changes
  • Invoice approval and payment release, including host-to-host payment streams
  • Wire transfers, loan write-offs and other high-value financial movements
  • Any transaction above a threshold value you define
  • Journal entries and accounting corrections
  • The approval steps in any custom workflow
  • Administrative profiles that could otherwise override a control

Verification methods

  • Palm vein
  • Fingerprint
  • Face recognition
  • Smart card
  • Biometric NFC band
  • PIN
  • Password
  • IP address
  • Nationality

Any combination can be required, and which one is used is recorded with the event.

In practice

Consol Glass, South Africa

A glass packaging manufacturer with four factories, a complex vendor and procurement landscape, and payment streams running host to host directly into vendors' banks. Mandatory dual biometric approval was built into the payment process itself, with no access at all for users who are not enrolled.

Read the full case study

A major international bank

Biometric security was required natively inside SAP as part of the bank's own checks and balances, after extensive proof-of-concept and penetration testing. Large wire transfers and loan write-offs require biometric credentials, and threshold values inside transactions trigger re-authentication automatically.

Read the full case study

A public school district

Overtime could only be approved by supervisors, but their assistants held their passwords for everything else, which is how overtime came to be approved under a principal's profile. Attaching the biometrics to the task rather than the sign-in ended it, and named the people responsible.

Read the full case study

Sasol, South Africa

A global chemicals and energy company running eight SAP systems across 27 countries. SAP GRC defines which bank payments need which approvals; bioLock establishes who gave them, and the same protection covers changes to the GRC responsibility rules themselves.

“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.”

Lungile Mginqi, Group CIO, Sasol

Read the full case study

What it proves

The rule you designed becomes the rule that executes.

01

The Segregation of Duties rule you designed is the rule that executes, because it now applies to a verified human rather than to a credential.

02

Delegation becomes visible. Work carried out under someone else's profile is recorded against the human who actually did it.

03

The audit log answers the auditor's real question, which is not which account did this but who did this.

Questions people ask

“We already have SAP GRC.”

Good, and keep it. GRC manages your internal controls. bioLock stops them being circumvented, by making sure the human on each side of a control is the human who is supposed to be there.

“Our controls have never been breached.”

The standard SAP log records the account, so a breach carried out with a borrowed password looks exactly like normal work. bioLock is what makes the difference visible in the first place.

“Do we have to protect every transaction?”

No. Most customers start with a short list: the payment release, the vendor master, the transactions above a threshold. The list grows from there.

“Who can change the rules themselves?”

The rules can be protected the same way. At Sasol, changing a GRC responsibility rule requires two authorized users to provide biometric credentials, so four eyes covers the rules as well as the money.

See it in your own SAP system.

A 15-minute briefing, a 60-minute technical presentation for your team, or a proof-of-concept installation running against your own data and functions.

bioLock runs inside SAP ERP and the S/4HANA platform. It does not replace your security stack. It closes the gap between access and action.