Case studies

Central banking

Single Sign-On

Single Sign-On opens every system without another password. That is the convenience, and it is also the risk. Biometric verification put the human back into the moment that matters.

Customer
African central bank
employees in one shared office
100+
A signed-in session had stopped being the same thing as a signed-in human.

The customer

This African central bank was established in the early 1970s and plays a vital role in maintaining the country’s monetary and financial stability. Its core mandate is to promote price stability, support a sound and resilient financial system, and contribute to the overall stability of the national economy. Key responsibilities include managing the country’s foreign exchange position, safeguarding its foreign currency reserves, overseeing monetary policy, and supporting the effective functioning of the financial sector.

The situation

SAP increasingly promotes Single Sign-On, and the appeal is obvious: authenticate once, and every connected system opens without another password. The risk arrives with the same convenience. Single Sign-On can introduce significant security exposure if it is not combined with proper user authentication at the point it matters.

At this customer, more than 100 employees share an office environment. With standard Single Sign-On, anyone could walk up to an unattended, logged-in computer, click through to the corporate finance system, and potentially reach SAP without entering any further credentials.

Nothing about that looks like an attack. There is no stolen password, no failed logon, nothing for a security report to flag. The session was opened legitimately by the right person. It simply stopped being theirs the moment they walked away from the desk.

The challenge

  • Keep the convenience of Single Sign-On without inheriting its blind spot
  • Prevent access to SAP from a workstation that is already signed in and unattended
  • Establish who is at the keyboard at the moment a sensitive function is used
  • Protect sensitive SAP applications and financial data in a shared office
  • Establish step-up controls on the functions that carry consequence
  • Stop account take-overs on a PC somebody has walked away from
  • Produce a record that names the verified human rather than the open session

What was implemented

Once the customer recognized the vulnerability, they implemented bioLock to add a layer of biometric authentication on top of the existing Single Sign-On.

  • Biometric verification required at selected SAP applications and financial transactions
  • Verification placed at the point of the action rather than only at the point of entry
  • Tamper-proof logging of each protected transaction, including refused attempts
  • Implemented by authorized realtime partner Linx/Africa, which has deployed bioLock across Southern Africa since 2010

The outcome

  • Single Sign-On was kept, and so was its convenience: nobody types more passwords than before
  • An unattended, signed-in workstation no longer opens SAP financial data to whoever sits down at it
  • Sensitive SAP applications and financial data are reached only after the human is verified
  • Accountability restored to individual users in an office of more than a hundred people