Protect sign-in with multi-factor authentication and role-based access
Also listed as: Multi-factor authentication & role-based access
What is it?
Xelence checks who each user is when they sign in, including a second proof of identity (multi-factor authentication), and limits what they can see and do based on their role.
Why does it matter?
Less risk of unauthorized access, with permissions that match each person's job.
Start thinking about
- Which identity provider, such as Entra ID or Okta, should staff and constituents use to sign in?
- Which of your policies, such as password, session or network rules, should Xelence enforce?
- How often do you review user roles and access, and who signs off on the review?
- How quickly can you remove access when staff change roles or leave?
- What does your policy say about using generative AI with personal or sensitive information?
- How will you fit the security changes in each release into your change and testing process?
Terms used on this card
- Multi-factor authentication (MFA)
- Signing in with a second proof of identity, such as a code on your phone, as well as a password.