Solution area 01
Your SAP system knows the password.
It does not know who typed it.
Logon to SAP and S/4HANA is checked against a credential that anyone can hold, borrow or buy. bioLock checks it against the human standing at the keyboard, and records who that was.
Attackers rarely break into SAP. They log in.
A working username and password is the cheapest way into an enterprise system, which is why credentials are phished, shared between colleagues, written on a sticky note under a keyboard, and kept long after someone has left. Once that credential is used, SAP cannot tell the difference between the human it belongs to and the human using it.
Shared passwords
A colleague covers for someone on leave. Nothing in the log will ever show it.
Ghost workers
A former employee, contractor, auditor, intern or temporary worker still knows a valid password, and the account still works.
Generic and admin logons
DDIC, firefighter and similar accounts conceal the human entirely. Whatever is done under them belongs to nobody.
Account takeover
A phished credential gives an outsider exactly the access the employee had, from anywhere.
Where standard SAP security stops
SAP authentication is designed to answer one question, and it answers it well.
SAP answers this
Is this a valid account with the right authorizations?
bioLock answers this
Was the human using this account the human it belongs to?
Single sign-on makes access smoother. Multi-factor authentication at the network edge makes the login harder to fake. Neither of them stands next to the keyboard once the session is open.
A layer inside SAP, not a product beside it
How bioLock closes it
bioLock adds a verification step to the logon itself, inside SAP.
Every authorized user is enrolled
Whatever their role, so the system holds a biometric identity for each of them and not only a credential.
Logon requires that identity
The account is only the first factor. The human is the second.
Users who are not enrolled get nothing
Unless bioLock has specifically invited a user to a function, the answer is no. This is the practical form of zero trust: no actor is trusted until they are verified.
Every attempt is recorded
Including the ones that fail, in a tamper-proof log that names the identified human next to the SAP user ID.
Enrolled identities
A biometric identity per authorized user, held next to the SAP account.
Logon to production
The password is accepted. The identity is still outstanding.
Not enrolled, no entry
A valid password is no longer enough on its own.
The credential was correct. The human was not the one it belongs to.
Tamper-proof audit record
Including the attempts that were refused.
What you can protect
Logon is the baseline. The same verification can be required again at any point inside the session.
- SAP and S/4HANA logon, on desktops, laptops and over VPN
- Generic and administrative accounts such as DDIC and firefighter IDs
- Powerful system functions such as SU01 and SE16
- The transport manager, and movement of code or data into production
- Any transaction, screen, field or single button that carries consequence
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
A manufacturing client of KPMG, Mexico
Rapid growth, warehouses and offices spread over a large area, and a workforce not tied to any single location. KPMG was asked to upgrade security for the client's SAP ECC6 installation and recommended biometric identity management as the first step, on the grounds that perimeter access has to be taken care of before anything else.
“The client has graduated from the obsolete world of passwords to a far more controlled environment of biometric identity management. The client has a far better understanding of when and how each user had access to their SAP system. The project has been a complete success.”
A user who knows their way around SU01, SE16 or a DDIC logon can reach far beyond their daily work. An employee on the way out can export an entire customer list. A generic logon hides the human completely, unless a second factor identifies them.
What it proves
After bioLock, three things are true that were not true before.
01
Access to SAP is tied to a human, not to a credential in circulation.
02
Workplace rotation stays completely flexible. People work from any machine or location, because their identity travels with them rather than with the device.
03
The audit trail is indisputable, including the attempts that were refused, which is what turns a suspicion into a fact.
Questions people ask
“We already have single sign-on.”
Single sign-on identifies the account and makes it easier to reach. bioLock verifies the human using it. The two work together: SSO for convenience, bioLock for accountability.
“We already have multi-factor authentication.”
MFA protects the login. It does not protect the critical function executed twenty minutes later in an open session. bioLock can require verification at any point you choose, not only at the door.
“Will this slow everybody down?”
Verification takes about a second, and you decide where it is required. Most customers protect the logon plus a short list of sensitive functions, rather than every screen.
“What about people who cannot use a fingerprint reader?”
Several verification methods are supported, including palm vein, face recognition, smart cards and biometric NFC bands for environments where gloves are worn.
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.