Solutions
Five places inside SAP where knowing who is acting changes the outcome.
Case Studies
Ten deployments, across ten different ways the wrong human gets in.
See all case studiesStop fraudulent SAP transactions
Stop unauthorized people from executing critical SAP transactions—even when they're using a valid account.
bioLock verifies the actual human behind high-risk SAP actions with biometric authentication, at the moment the transaction occurs.
The problem
A login verifies a credential. It doesn't verify the human.
Credential-based access
bioLock, function-level
Why now
But one thing remains difficult to fake:
The verified human performing the action.
The demonstration
Interactive SAP simulation.
Test drive the full online simulation (opens in a new tab)See another scenario
01
Someone attempts to change vendor banking information.
02
The checkpoint is defined in advance: exactly which SAP transaction, button, table or field needs protection.
03
When someone attempts that action, bioLock steps in before SAP does.
04
The user confirms who they are biometrically — fingerprint, palm vein, Windows Hello or similar — not just with a password.
05
Verified users proceed. Everyone else is blocked automatically.
06
Every attempt is written to bioLock's own tamper-proof log, ready to share directly with auditors.
07
Any action bioLock authorizes or denies can be sent to supervisors and security teams immediately, so they can act while an attempt is still in progress.
Business risks
Fraud. Insider threat. Privileged access. Compliance. Each one comes back to the same question: who actually performed this action?
How bioLock works
Most security products authenticate at
bioLock can take identity verification down to
The transaction level.
Login authentication
“Who are you?”
Function-level authentication
“Are you really the human performing this action?”
Solution areas
The mechanism is the same everywhere. What changes is which action is worth stopping, and what it costs when the wrong human takes it.
Verify the human at the point of entry. Logon to SAP and S/4HANA is checked against biometric identity, not just a credential someone happens to hold.
Insider threats and Segregation-of-Duties violations are the costliest risks in enterprise finance. GRC rules separate the accounts, but a borrowed password or an unlocked screen can still put one person on both sides of a transaction. bioLock verifies the specific human behind every action, so Segregation of Duties cannot be circumvented that way.
Cashiers at the point of sale and call centre staff editing customer records are a daily exposure point. bioLock confirms identity at the exact moment it matters.
A shared kiosk on the loading dock stays signed in under one generic SAP ID, so nobody loses the day logging in and out. Each action is confirmed with a fingerprint and recorded against the human who took it, and anyone without an enrolled credential — a visiting driver at an unattended screen — can do nothing at all.
Attach a verified human identity to the documents and changes that carry consequence, so an approval can be traced to a human rather than to an account. It also cuts the digital signature itself from 15+ seconds of typing to about one second, including biometric bands for gloved environments.
Proof
Developed since 2001 – SAP Certified since 2002 – 25 years protecting real-world SAP environments.
SAP News Center · January 2023
The global chemicals and energy company uses bioLock biometric verification to secure payment approvals in SAP, so a shared password can no longer confirm a payment.
Read the article on SAP News (opens in a new tab)“…only the intended SAP user, beyond any reasonable doubt, can confirm payment.”
SAP News Center · March 2025
Seven factories and 150 depots at South Africa’s state-owned rail and port operator run shop-floor SAP through kiosks built by partner Linx-AS, with Fujitsu PalmSecure palm-vein verification and bioLock. Nobody signs in and out all day, and every transaction still belongs to a named human.
Read the article on SAP News (opens in a new tab) Watch the installation (opens in a new tab)“Palm-vein technology is ideal for industrial environments as sub-dermal biometrics do not wear out over time.”
In production
0
employees at Transnet Engineering, where shop-floor SAP runs behind palm-vein kiosks
0+
cashiers protected at a national retail chain
0+
users covered in a manufacturing workflow rollout
0%
annual SAP fraud reduction, measured by a major government organization after deploying bioLock
Trusted by Global Fortune 500 companies, central banks, governments, and leading public and private sector organizations worldwide.
Case studies
Logistics
55,500employees
Palm-vein verification on shared maintenance kiosks across seven factories and 150 depots — so a shared password stopped being a way into SAP Plant Maintenance.
Read the case studyRetail
800cashiers
Biometric re-authentication on every single sale, across 300+ registers in 200+ locations, tying each transaction to the human who rang it.
Read the case studyPharmaceutical
100%of high-value approvals
Remote approval of large payments requires biometric identification before the transaction posts — an audit trail administrator credentials cannot bypass.
Read the case studyManufacturing
1,000users
Mandatory two-factor biometric access to SAP across geographically dispersed sites, ending password sharing and producing an indisputable log-on trail.
Read the case studyBanking
Multicurrency wire transfers
An international bank placed biometric checks directly on wire transfers and other high-value transactions, with tamper-proof logging for regulatory compliance.
Read the case studyManufacturing
4factories, 17 export markets
Mandatory dual approval on vendor payments, enforced biometrically, across a procurement operation spanning four plants and seventeen export markets.
Read the case studyPublic sector
Zeroovertime fraud after rollout
Junior administrators had been approving overtime as their supervisors on shared SAP passwords. Biometric approval ended it — and named who had been doing it.
Read the case studyConglomerate
5,568employees
Paper-based leave requests replaced by a biometrically controlled self-service process at shared kiosks, for a workforce with limited SAP proficiency.
Read the case studyGovernment
PHIinside SAP HR
After an unauthorized look at employee health records, access to protected health information was restricted to verified users, with re-authentication on sensitive tasks.
Read the case studySocial services
Millionsof beneficiaries
Biometric and smart-card controls on benefit disbursement for an agency running pensions, workers' compensation and social assistance programmes.
Read the case studyTechnology
Security that lives where the SAP transaction happens.
bioLock is embedded within the SAP environment, allowing identity verification to occur at the point where a sensitive SAP function is executed—not merely when the user logs in.
Integrated into SAP's ABAP code, in our own SAP namespace/realtime
The user doesn't have to leave the SAP environment to prove identity.
Authentication can be tied to the specific business action, rather than treating every SAP session the same.
The important question becomes: Who actually performed this action? Not simply: who logged in?
bioLock becomes part of the SAP security architecture rather than another disconnected security layer.
Standard SAP security
“We verified that this account can access SAP.”
bioLock
“We verified that the human performing this SAP action is the authorized user.”
WhoDid whatIn SAPWhenAfter biometric verification
The standard SAP log file shows only the logged-in credentials: the SAP User ID. bioLock also records the uniquely identified human, by biometric ID, in its own tamper-proof log that can be shared directly with auditors.
| Date | SAP User ID | Biometric ID user · full name | Protection status | Controlled SAP activity | ||||
|---|---|---|---|---|---|---|---|---|
| Date | User Name | bioLK User | First name | Last name | N | Text | Func | Text |
| 10.02.2024 | SMITH | SMITH | Thomas | Smith | 1 | was accepted | 471 | Execute the Payment Run – F110 |
| 10.02.2024 | SMITH | Snowden | Edward | Snowden | 3 | not authorized | 375 | Exporting Sensitive NSA DATA |
| 11.02.2024 | AJ3765 | AJ3765 | Amanda | JONES | 3 | not authorized | 470 | Automatic Payment Transaction |
| 12.02.2024 | MATHIAS | none | Hacker | Hacker | 2 | was rejected | 471 | Execute the Payment Run – F110 |
| 12.02.2024 | ADMIN | MILLER | Joe | Miller | 3 | not authorized | 412 | Create a Vendor – FK01 |
What a standard SAP log showsWhat bioLock adds: the human
| Approach | What is verified? | Where? |
|---|---|---|
| Password | Credential | Login |
| MFA | Credential + second factor | Login |
| SSO | User identity | Application access |
| PAM | Privileged account | Access/session |
| SAP authorization | User's permissions | SAP |
| bioLock | The human performing the action | SAP function/transaction / Enter Button |
Authentication tells you who entered SAP. bioLock helps establish who performed the critical action.
SAP knows the transaction.
bioLock knows the human.
Together, they establish trusted execution.
What does bioLock replace?
Already have MFA, GRC, SSO or PAM?
| Existing security | What it does | bioLock adds |
|---|---|---|
| SSO | Identifies account | Verifies human |
| MFA | Protects login | Protects critical function |
| SAP GRC | Manages internal controls | Prevents circumvention of internal controls |
| PAM | Controls privileged access | Adds biometric identity |
| SIEM | Records events | Establishes verified identity |
Resources
15 min
For security/IT leadership.
Book a briefing30 min
A customized 30-minute assessment of your security pain points.
Request an assessmentPOC
For organizations evaluating deployment.
Request a Proof of Concept
