Skip to main content
Knowledge asks the employee to state facts from their directory or HR record, such as the last 4 digits of their Social Security number. It’s low friction, but directory facts are exactly what a social engineer researches before calling the help desk, so Knowledge is the weakest factor. Use it as a fallback alongside stronger factors, never on its own.

Before you start

  • A connected directory, an HR system, or both, with fields that are populated, consistent and not public. Employee ID and the last digits of an ID number are common choices. department is often empty and coworkers know it.
  • If your organization keeps HR data in extension attributes, you can use those too; give them a readable label.

Settings

Open Factors → Knowledge.

Question sets

Questions are grouped into sets. Every question in a set is asked, in order.
  • The first set this person has every answer for is asked. If someone is missing a value for any question in set 1, set 2 is used instead, and so on. Add up to 3 sets.
  • A wrong answer never unlocks the next set. It uses an attempt, and the same set is asked again. Only missing data moves someone to the next set.
  • Knowledge is offered only when at least one set has every answer on file for that person.
For example, set 1 asks the last 4 digits of the Social Security number and the department; set 2, for people with no SSN on file, asks the employee ID and the office location.

Each question

Select a question to open its settings.
Questions that ask about HR need the HR system to answer. If HR is down or disconnected, a set with an HR question is skipped and the next set is used; TruU doesn’t fall back to your directory for that question. Keep a set that needs only directory fields if Knowledge must stay available.
Attempts per run sets how many wrong answers are allowed before the factor fails (default 2). Answers are compared on TruU’s servers. The expected value is never sent to the browser or shown to an agent, and a failed answer never says which question was wrong.
Never put Knowledge alone in a column. Pair it with a one-time code (Email or SMS) at minimum.

Troubleshooting