Language

Knowledge-Based Authentication (KBA)

What is Knowledge-Based Authentication (KBA)?

Knowledge-based authentication (KBA) is a method of checking a person’s identity by asking questions that the person is expected to answer correctly. It has traditionally been used during account login, account recovery, customer support calls, and other situations where an organization wants additional evidence that it is dealing with the account holder.
A question might ask for a fact the user supplied earlier, such as the name of their first school, or for information drawn from external records, such as a previous address. This second approach is often more precisely called knowledge-based verification (KBV).

What are the types of KBA?

KBA is commonly divided into two types:
  • Static KBA: uses questions and answers set in advance. A user may choose a security question when creating an account and answer it later to recover access. The same question can be asked repeatedly unless the organization changes it.
  • Dynamic KBA or KVB: generates questions from external records at the time of the check. A person might be asked to identify a previous address or recognize a past transaction from several options. These questions do not depend on answers previously registered with the service.

Why has KBA become less reliable?

KBA assumes that personal facts are difficult for anyone other than the legitimate user to obtain. In practice, potential answers may be available through public records, social media, data breaches, social engineering, or information shared with relatives and acquaintances.
Static security questions are particularly vulnerable when users select common answers or reuse the same questions across services. Dynamic questions avoid some of these problems, but the underlying records may be outdated, incomplete, or accessible to an attacker. Legitimate users may also fail because they cannot remember an old address or do not recognize a transaction.
For these reasons, KBA should not be relied on as the sole control for sensitive actions such as account recovery, changing payment details, or accessing protected information. Current NIST guidance does not consider KBA an acceptable secret for digital authentication and does not permit KBA or KBV as a method of identity verification in systems following its requirements.

What can organizations use instead of KBA?

The appropriate alternative depends on what the organization needs to establish. Passkeys and other cryptographic authenticators can provide stronger evidence that a returning user controls a registered account credential. Confirmation through an existing authenticated channel may provide additional protection for sensitive account changes.
When an organization needs to confirm that the person requesting access is the verified account holder, renewed identity verification may be appropriate. This can involve checking a government-issued identity document, comparing the applicant’s face with the document portrait, and using liveness detection to help confirm that a real person is present.

How can Regula help when KBA is insufficient?

Regula provides document and biometric verification technologies for situations that require stronger identity evidence than answers to personal questions.
Regula Document Reader SDK can examine an identity document for authenticity and extract information from its visual zone, machine-readable zone, barcode, and NFC/RFID chip where available. Regula Face SDK can perform a 1:1 comparison between the applicant’s facial image and a portrait extracted from the document or another trusted source. Liveness detection helps confirm that a real person is present during the biometric capture.
Organizations can use these checks during customer onboarding, higher-risk account recovery, reverification, or before approving sensitive account changes.

FAQ

Is KBA the same as a password?

No. Both rely on something a person knows, but a password is intended to be a secret created or assigned specifically for authentication. KBA questions often rely on personal facts that may be discoverable through public sources, data breaches, or social engineering. Knowing someone’s previous address generally provides less assurance than controlling a properly protected authenticator.

What is the difference between static and dynamic KBA?

Static KBA uses questions and answers established in advance, such as a security question selected during account setup. Dynamic KBA creates questions from external records during the verification session. Dynamic questions can be less predictable, but their answers may still be available to an attacker or difficult for the legitimate user to recall.

Can KBA verify someone’s identity during onboarding?

Answers to personal questions can be compared with records, but they do not show that an identity document is genuine or that the person answering is its holder. An organization that needs stronger identity proof may require document verification and biometric checks. The required method depends on the service, risk, and applicable rules.

Why is KBA risky for account recovery?

Account recovery can give a person control of an existing account and its stored data. If an attacker can obtain or guess the answers, the recovery process may bypass stronger login protection. Organizations should assess account recovery as a sensitive action and use checks suited to its risk.

On our website, we use cookies to collect technical information. In particular, we process the IP address of your location to personalize the content of the site

Cookie Policy rules