Frequently Asked Questions
Caller Verify is a Single Page Application (SPA) connects to the Okta authorization server and makes Okta API calls to Okta. Caller Verify leverages a user's existing authenticators already enrolled in Okta to verify users.
The Caller Verify application can also integrate with many ITSM applications (e.g. ServiceNow, Zendesk). This allows users to use Caller Verify within their ITSM application.
Caller Verify can be found on the Okta Integration Network here.
Yes! Caller Verify can integrate with various ITSM applications including ServiceNow and Zendesk.
Check out this video on Caller Verify and ServiceNow. The TechJutsu team can help you integrate Caller Verify with your ServiceNow.
Check out this video on Caller Verify and Zendesk. Caller Verify is available on the Zendesk Marketplace here.
Okta Caller Verify is more secure than traditional security questions because it eliminates common vulnerabilities associated with knowledge-based authentication (KBA). Here's why:
Security Questions Are Easy to Guess or Breach
-
Publicly Available Information: Many security question answers (e.g., mother’s maiden name, first pet, or high school) can be found online, especially via social media or data breaches.
-
Social Engineering Attacks: Attackers can manipulate users into revealing security answers through phishing or phone scams.
-
Credential Stuffing & Data Leaks: If security answers are leaked in a breach, attackers can reuse them to bypass authentication.
Caller Verify is more secure because it relies on real-time, device-based authentication rather than static, guessable answers.
Dynamic & Real-Time Authentication
-
Caller Verify uses Okta Verify push notifications or one-time passcodes (OTP) sent via SMS or email.
-
These methods require real-time interaction from the legitimate account owner.
-
Even if an attacker knows some personal details, they cannot approve a push notification on the victim’s device.
This ensures the user is actively present and authenticating, rather than relying on pre-set, potentially compromised answers.
Protection Against Replay & Phishing Attacks
-
Traditional security questions can be reused indefinitely once exposed.
-
Caller Verify generates a new challenge every time, making replay attacks impossible.
-
Push notifications and OTPs add an additional security layer that prevents phishing attacks.
Even if attackers have some personal data, they still need access to the user’s phone or email.
Reduces Agent Fraud & Insider Threats
-
Security questions can be misused by malicious agents or compromised call centers that store or leak answers.
-
Caller Verify removes agent access to security answers, making insider fraud much harder.
-
The verification process is logged, ensuring accountability and compliance.
Even support agents don’t see the verification data, reducing risk.
Compliance & Zero Trust Security
-
Many regulations (e.g., GDPR, HIPAA, PCI-DSS) discourage or prohibit using static security questions for identity verification.
-
Caller Verify aligns with Zero Trust security principles by verifying the user based on their real-time authentication, not stored knowledge.
Caller Verify meets modern security and compliance standards, making it a safer alternative.
-
Yes! Yubikeys can be used as a FIDO2 or WebAuthN authenticator in Okta.
For FIDO2 or WebAuthN authenticator verfication, Caller Verify generates a verification link that must be delivered to the user. The verification link can either be manually provided to the caller or it can be delivered via SMS link, email link, or Slack message.
Check out this video on Caller Verify and YubiKey.
There are some scenarios where it might not be possible to Verify a particular Caller. Some examples of these scenarios are:
-
The caller has lost (or forgotten) their phone with all their Enrolled MFA methods.
-
Employee onboarding, the caller may be a new employee that hasn’t yet registered in MFA.
-
Cleanroom or Shopfloor employees. These employees may or may not have MFA registered but may be in an environment where they are not allowed to bring their mobile devices.
To address these scenarios Caller Verify can support Delegated Authentication. This feature allows you to delegate authentication to a trusted 3rd party, for example a Callers manager or supervisor. The details about the manager or supervisor can be automatically pulled from any Okta Universal Directory attribute.
-
Caller verification software is essential for compliance with various regulations such as OSFI, HIPAA, PCI DSS, and GDPR.
OSFI: The Office of the Superintendent of Financial Institutions (OSFI) is a Canadian independent federal government agency that regulates and supervises more than 400 federally regulated financial institutions (FRFIs) to determine whether they are in sound financial condition and meeting their requirements, including the implementation of MFA . In Guideline B-13 Technology and Cyber Risk Management Section 3.2.7 OSFI requires that federally regulated financial institutions implement MFA across external-facing channels, and ensure that accounts are securely authenticated, managed, and audited to detect unauthorized access requests. Caller verification software can help entities comply with this requirement by verifying the identity of callers using MFA, before granting access to systems and data and by logging verification attempts.
HIPAA: The Health Insurance Portability and Accountability Act (HIPAA) requires covered entities to implement reasonable and appropriate administrative, technical, and physical safeguards to protect the confidentiality, integrity, and availability of electronic protected health information (ePHI). One of the technical safeguards required by HIPAA is access control, which includes implementing unique user identification, emergency access procedures, and automatic logoff. Caller verification software can help covered entities comply with the access control requirement by verifying the identity of callers before granting access to ePHI. HIPAA Security Rule, 45 CFR § 164.308(a)(1)(ii)(D).
Caller Verify can be implemented in less than a day. Contact TechJutsu today to book your Caller Verify demo.
Yes! Caller Verify can integrate with many ITSM applications including Jira Service Management.
Check out this video on Caller Verify and Jira. The TechJutsu team can help you integrate Caller Verify with your Jira Service Management.