RSA My Page | ID Verification and Secure Enrollment

Credentials can be stolen. Identities can be faked. An attacker who convinces your help desk they’re a legitimate employee—or who slips through onboarding under a false identity—can operate inside your environment for months before detection. ID verification closes that gap by confirming not just that someone has the right credentials, but that they are the person entitled to have them.

RSA My Page embeds ID verification directly into the credential enrollment and recovery workflows your users already use. Offered through RSA^® ID Plus, the market’s most secure identity and access management (IAM) security platform, it gives security and IT teams a no-code, policy-driven way to enforce identity proofing at the moments that matter most—without adding friction for legitimate users.

ID verification is most critical at high-risk points in the identity lifecycle—when a new user is being onboarded, or when an existing user needs to recover access. These are the moments attackers target.

• Credential enrollment: New users verify their identity digitally—using biometrics, a government-issued ID, or other verification methods—before birthright credentials are issued. Remote workers can complete the process without appearing in person.
• Credential recovery: When a user needs to reset or recover credentials, RSA My Page requires proof of identity before access is restored. This stops the social engineering technique used in attacks like the ALPHV ransomware campaigns, where attackers called help desks claiming to have forgotten passwords.

RSA My Page integrates ID Dataweb’s verification workflows through RSA’s OpenID Connect (OIDC) connector. Administrators configure and deploy ID verification workflows without custom coding. The process begins with an initial authentication step, followed by the ID Dataweb verification workflow. Each interaction is logged for audit and compliance reporting.

Available verification templates through ID Dataweb:

• MobileMatch: Verifies identity through phone possession, ownership, and credit bureau data.
• BioGovID: Employs a live selfie and government ID match for high-assurance verification.
• DynamicKBA: Confirms identity using dynamic knowledge-based questions.

ID verification is also available through RSA Help Desk Live Verify, extending the same identity proofing to contractors, partners, temporary employees and users without a registered authenticator through government-issued identification. These users have historically represented a gap in verification coverage.

The RSA Help Desk Live Verify workflow confirms both the user’s and the agent’s identities without either side sharing a PIN, password, or personal detail. Administrators configure which user populations are routed to authenticator-based verification versus ID Verification through the same RSA ID Plus policy framework.

RSA ID verification is designed for organizations where identity assurance requirements are not optional:

• Financial institutions where fraudulent insider access and help desk social engineering directly translate to financial loss.
• Government agencies with strict identity requirements at access boundaries that extend to contractors and partners.
• High-assurance organizations where onboarding an imposter—or allowing an attacker to recover someone else’s credentials—represents an unacceptable risk.

RSA’s ID verification capability is powered by ID Dataweb, a leading provider of real-time identity verification, fraud prevention, and risk management. The integration embeds ID Dataweb’s verification workflows into RSA My Page and RSA Help Desk Live Verify with no custom coding required, available to all RSA ID Plus E2 and E3 subscribers.

Contact your RSA Account Manager or visit rsa.com to learn more about ID verification and secure enrollment with RSA ID Plus.