Identity and access management
Single Sign-On (SSO), Multi-Factor Authentication (MFA), directory synchronization, and identity lifecycle governance governing user access across enterprise resources.
Key Technical Considerations Before Procuring
Identity is the primary modern enterprise security perimeter. Buyers should require phishing-resistant FIDO2 biometric authentication (FastPass / WebAuthn), automated SCIM lifecycle provisioning, contextual adaptive access evaluation based on device and network risk signals, and universal federation across on-premises Active Directory and cloud SaaS suites.
Documented Solutions in this Category
Showing 43 published solutions with verified evidence
Okta Workforce Identity Cloud
Cloud-native IAM platform providing Single Sign-On (SSO), Adaptive Multi-Factor Authentication (MFA), Lifecycle Management, and Identity Governance (IGA).
Microsoft Entra ID
Microsoft Entra ID from Microsoft focuses on identity management and access control. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Conditional-access policy: Brings user and device conditions into access decisions for the connected Microsoft identity environment. - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Conditional access: Applies access rules using conditions such as the user, device or session context. - Access certification: Helps review whether existing access rights remain appropriate for each identity. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Microsoft Entra ID is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Microsoft Entra ID focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Okta Customer Identity Cloud (Auth0)
Developer-centric Customer Identity and Access Management (CIAM) platform powering secure consumer sign-in, social login, and API authorization.
CyberArk Privilege Cloud
SaaS-based Privileged Access Management solution that securely stores, rotates, and isolates privileged credentials and monitors administrative sessions.
Identity Security Cloud
Identity Security Cloud from SailPoint focuses on identity governance and access lifecycle management. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - SailPoint identity governance: Organizes the supported identity governance functions in SailPoint's cloud offering. - Access certification workflows: Supports reviewing whether assigned access remains appropriate. - Identity lifecycle management: Addresses supported access changes as identities join, move or leave the organization. Use and operational context Identity Security Cloud is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Identity Security Cloud focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
1Password Business
1Password Business from 1Password focuses on enterprise password management and secure credential sharing. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Shared organizational vaults: Uses the product's vault-based model to give teams controlled access to shared business credentials. - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Secure credential sharing: Lets authorized users collaborate on credentials through the product's access controls. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. - Credential risk assessment: Highlights credential exposures or hygiene issues documented by the vendor. Use and operational context 1Password Business is relevant to organizations governing employee credential use when the requirement centers on organizing access to shared or individual credentials. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? 1Password Business focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
1Password Extended Access Management
1Password Extended Access Management from 1Password focuses on device-aware access and application access governance. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Device health and access context: Connects the documented device-health signals with decisions about access to business applications. - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Access certification: Helps review whether existing access rights remain appropriate for each identity. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Device posture assessment: Brings device condition into identity or access decisions. Use and operational context 1Password Extended Access Management is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? 1Password Extended Access Management focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Account Protector
Account Protector from Akamai focuses on account abuse detection and login risk assessment. It is account risk and abuse protection technology used for assessing suspicious login or account activity. Capabilities - Account risk analysis: Assesses the signals associated with a user's account or login activity. - Account takeover protection: Addresses activity that can indicate a legitimate account is being misused. - Credential abuse detection: Focuses on the misuse of credentials in authentication or account access workflows. - Behavioral user signals: Uses observed activity patterns as part of account risk assessment. - Application risk integration: Provides the documented mechanism for bringing account risk signals into an application workflow. Use and operational context Account Protector is relevant to teams protecting customer account workflows when the requirement centers on assessing suspicious login or account activity. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review signal collection, risk thresholds, response integration and the effect of decisions on legitimate account holders. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Account Protector focuses on assessing suspicious login or account activity. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Identity Security Insights
Identity Security Insights from BeyondTrust focuses on identity exposure analysis and risk investigation. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Identity threat detection: Focuses on signs of identity misuse that can remain relevant even when an endpoint is not compromised. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Identity Security Insights is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Identity Security Insights focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Bitwarden Password Manager
Bitwarden Password Manager from Bitwarden focuses on business password storage and secure credential sharing. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Secure credential sharing: Lets authorized users collaborate on credentials through the product's access controls. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. - Credential risk assessment: Highlights credential exposures or hygiene issues documented by the vendor. Use and operational context Bitwarden Password Manager provides a vault-based workflow for employee credentials and approved sharing. Assess how users organize items, how administrators govern organizational access and how credentials are transferred or withdrawn when an employee's responsibilities change. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Bitwarden Password Manager focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
BlackBerry UEM
BlackBerry UEM from BlackBerry focuses on enterprise device management and access policy. It is unified endpoint management technology used for administering devices, business applications and endpoint policies. Capabilities - Device enrollment and management: Brings supported mobile or endpoint devices under enterprise management policy. - Application administration: Provides the documented controls for administering business applications on managed devices. - Device policy enforcement: Applies enterprise settings and policy to the supported device estate. - Mobile operating-system coverage: Includes the mobile platforms explicitly named in BlackBerry's support documentation. Use and operational context BlackBerry UEM is relevant to enterprise mobility and endpoint administration teams when the requirement centers on administering devices, business applications and endpoint policies. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Device management deployment; available platform and hosting options depend on the selected UEM offering. Before adoption, review device enrollment, application management, policy enforcement and support for the organization's device fleet. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? BlackBerry UEM focuses on administering devices, business applications and endpoint policies. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Cisco Duo
Cisco Duo from Cisco focuses on multifactor authentication and device-aware access. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Multifactor authentication service: Adds the supported additional authentication methods to application access workflows. - Device trust assessment: Brings the documented device context into Duo access decisions. - Phishing-resistant authentication options: Includes the phishing-resistant authentication options documented for the selected Duo deployment. - Device posture assessment: Brings device condition into identity or access decisions. Use and operational context Cisco Duo is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Cisco Duo focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Dashlane Password Manager
Dashlane Password Manager from Dashlane focuses on business password management and credential protection. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Secure credential sharing: Lets authorized users collaborate on credentials through the product's access controls. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. - Credential risk assessment: Highlights credential exposures or hygiene issues documented by the vendor. Use and operational context Dashlane's business password manager supports the administration of employee credential use. Review the user experience for storing and sharing credentials, administrative policy and the way account or access changes are handled when employees move between responsibilities. Deployment and evaluation Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Dashlane Password Manager focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Entrust Identity as a Service
Entrust Identity as a Service from Entrust focuses on cloud authentication and access security. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Adaptive authentication: Uses contextual signals to change the authentication requirements for a login attempt. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Entrust Identity as a Service is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Entrust Identity as a Service focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
HUMAN Account Defender
HUMAN Account Defender from HUMAN Security focuses on account abuse detection and risk assessment. It is account risk and abuse protection technology used for assessing suspicious login or account activity. Capabilities - Account risk analysis: Assesses the signals associated with a user's account or login activity. - Behavioral user signals: Uses observed activity patterns as part of account risk assessment. - Application risk integration: Provides the documented mechanism for bringing account risk signals into an application workflow. Use and operational context HUMAN Account Defender is relevant to teams protecting customer account workflows when the requirement centers on assessing suspicious login or account activity. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review signal collection, risk thresholds, response integration and the effect of decisions on legitimate account holders. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? HUMAN Account Defender focuses on assessing suspicious login or account activity. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Huntress Managed ITDR
Huntress Managed ITDR is a managed security service offered by Huntress. Its documented scope centers on managed identity threat detection and response. Capabilities - Cloud identity threat monitoring: Monitors the cloud identity services explicitly supported by Huntress for identity-based threats. - Identity threat detection: Focuses on signs of identity misuse that can remain relevant even when an endpoint is not compromised. Use and operational context Huntress Managed ITDR is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Managed service with provider-led monitoring and response within the agreed service scope. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Huntress Managed ITDR focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative service deliverables, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
IBM Verify
IBM Verify from IBM focuses on identity authentication and access management. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Conditional access: Applies access rules using conditions such as the user, device or session context. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. Use and operational context IBM Verify is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Self-managed / on-premises option documented by the vendor. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? IBM Verify focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
JumpCloud Directory Platform
JumpCloud Directory Platform from JumpCloud focuses on cloud directory management and device identity controls. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Cloud directory administration: Connects the documented identity and device administration functions through a cloud directory model. - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Conditional access: Applies access rules using conditions such as the user, device or session context. - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context JumpCloud Directory Platform is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? JumpCloud Directory Platform focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Keeper Enterprise
Keeper Enterprise from Keeper Security focuses on business password management and credential sharing. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Secure credential sharing: Lets authorized users collaborate on credentials through the product's access controls. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. - Credential risk assessment: Highlights credential exposures or hygiene issues documented by the vendor. Use and operational context Keeper Enterprise provides an organizational password and credential-management workflow. Review the enterprise's vault and sharing structure, administrator permissions and identity lifecycle requirements, including how access is handled when a team member's role changes. Deployment and evaluation Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Keeper Enterprise focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
ADManager Plus
ADManager Plus from ManageEngine focuses on directory administration and identity reporting. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context ADManager Plus addresses directory administration through controlled account and group-management workflows. A useful pilot should include a joiner, a role change and a leaver, with particular attention to delegation, approval and reporting for those changes. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? ADManager Plus focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
N-able Passportal
N-able Passportal from N-able focuses on service-provider credential and password management. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. Use and operational context N-able Passportal is relevant to organizations governing employee credential use when the requirement centers on organizing access to shared or individual credentials. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? N-able Passportal focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
NordPass
NordPass from Nord Security focuses on business password storage and credential sharing. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Secure credential sharing: Lets authorized users collaborate on credentials through the product's access controls. - Credential risk assessment: Highlights credential exposures or hygiene issues documented by the vendor. Use and operational context NordPass is relevant to organizations governing employee credential use when the requirement centers on organizing access to shared or individual credentials. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? NordPass focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Auth0
Auth0 from Okta focuses on customer authentication and application identity management. It is customer identity and access technology used for adding customer authentication to supported applications. Capabilities - Application authentication workflows: Adds customer-facing sign-in and identity flows to supported applications. - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Adaptive authentication: Uses contextual signals to change the authentication requirements for a login attempt. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Customer identity workflows: Supports authentication and identity requirements for customers using external applications. Use and operational context Auth0 is relevant to application teams developing customer-facing sign-in when the requirement centers on adding customer authentication to supported applications. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review authentication methods, application integration, tenant configuration and how account recovery and login failures are handled. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Auth0 focuses on adding customer authentication to supported applications. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Okta Adaptive MFA
Okta Adaptive MFA from Okta focuses on risk-aware multifactor authentication. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Adaptive authentication: Uses contextual signals to change the authentication requirements for a login attempt. - Identity threat detection: Focuses on signs of identity misuse that can remain relevant even when an endpoint is not compromised. Use and operational context Okta Adaptive MFA is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Okta Adaptive MFA focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Okta Identity Governance
Okta Identity Governance from Okta focuses on access requests and identity lifecycle governance. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Access certification: Helps review whether existing access rights remain appropriate for each identity. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Okta Identity Governance is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Okta Identity Governance focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Okta Single Sign-On
Okta Single Sign-On from Okta focuses on centralized application sign-in and access control. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Adaptive authentication: Uses contextual signals to change the authentication requirements for a login attempt. - Identity threat detection: Focuses on signs of identity misuse that can remain relevant even when an endpoint is not compromised. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. - Customer identity workflows: Supports authentication and identity requirements for customers using external applications. Use and operational context Okta Single Sign-On is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Okta Single Sign-On focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Active Roles
Active Roles from One Identity focuses on directory administration and delegated identity management. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Active Roles concentrates on delegated administration of Microsoft directory environments. Review how administrators handle routine identity changes, how permissions are constrained, and whether the directory workflow can be governed without giving every operator unrestricted administrative access. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Active Roles focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Identity Manager
Identity Manager from One Identity focuses on identity lifecycle governance and access certification. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Access governance reviews: Supports reviewing and governing user access to the connected systems. - Role and permission administration: Organizes the role or permission model included in One Identity's management workflow. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Identity Manager is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Identity Manager focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
MetaAccess
MetaAccess from OPSWAT focuses on device posture assessment and access controls. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Device posture assessment: Checks the documented device condition signals used by OPSWAT's access-assessment workflow. - Endpoint compliance checks: Assesses the endpoint compliance factors documented for the supported integrations. - Access policy integration: Connects the device assessment result with the supported access-policy workflow. Use and operational context MetaAccess is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Self-managed / on-premises option documented by the vendor. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? MetaAccess focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
PingAccess
PingAccess from Ping Identity focuses on application access control and policy enforcement. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. - Device posture assessment: Brings device condition into identity or access decisions. Use and operational context PingAccess is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? PingAccess focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
PingFederate
PingFederate from Ping Identity focuses on federated authentication and single sign-on. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Adaptive authentication: Uses contextual signals to change the authentication requirements for a login attempt. - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context PingFederate is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? PingFederate focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
PingID
PingID from Ping Identity focuses on multifactor authentication and login protection. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Multifactor authentication methods: Supplies the additional authentication methods documented for PingID. - Application authentication integration: Connects supported authentication requests with the PingID verification workflow. - Authentication policy administration: Provides the documented controls for administering the authentication experience. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. Use and operational context PingID is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? PingID focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
PingOne
PingOne from Ping Identity focuses on cloud identity management and access control. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context PingOne is a cloud identity platform entry whose functions depend on the selected services. Map the required authentication and access workflows to the proposed package, including application onboarding and the administrative responsibilities for policies and user changes. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? PingOne focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
RSA Governance and Lifecycle
RSA Governance and Lifecycle from RSA focuses on access governance and identity lifecycle control. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Identity access certification: Supports periodic review of identity access within the governance workflow. - Identity lifecycle workflows: Coordinates the identity administration processes covered by the deployment. - Role-based access governance: Brings roles or entitlements into the documented access-governance model. Use and operational context RSA Governance and Lifecycle is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Self-managed / on-premises option documented by the vendor. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? RSA Governance and Lifecycle focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
RSA ID Plus
RSA ID Plus from RSA focuses on identity authentication and access security. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context RSA ID Plus is evaluated as an identity authentication and access service package. Review the methods and access workflows included in the selected offering, then test enrollment, user verification and administrative recovery for the accounts being protected. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? RSA ID Plus focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
RSA SecurID
RSA SecurID from RSA focuses on multifactor authentication and credential protection. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context RSA SecurID addresses authentication using the methods or authenticators included in the proposed deployment. Evaluate token or authenticator enrollment, user verification and recovery procedures, with clear ownership of the administration required throughout the credential lifecycle. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? RSA SecurID focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
IdentityIQ
IdentityIQ from SailPoint focuses on enterprise access governance and certification. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Access certification: Helps review whether existing access rights remain appropriate for each identity. Use and operational context IdentityIQ is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? IdentityIQ focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Saviynt Identity Cloud
Saviynt Identity Cloud from Saviynt focuses on identity governance and access risk management. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Converged identity governance: Brings the documented identity governance capabilities into a shared cloud platform. Use and operational context Saviynt Identity Cloud is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Saviynt Identity Cloud focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Singularity Identity
Singularity Identity from SentinelOne focuses on identity attack detection and identity protection. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Conditional access: Applies access rules using conditions such as the user, device or session context. - Identity threat detection: Focuses on signs of identity misuse that can remain relevant even when an endpoint is not compromised. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Singularity Identity is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Singularity Identity focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
SafeNet Trusted Access
SafeNet Trusted Access from Thales focuses on authentication and application access control. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Customer identity workflows: Supports authentication and identity requirements for customers using external applications. Use and operational context SafeNet Trusted Access is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? SafeNet Trusted Access focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
AuthPoint
AuthPoint from WatchGuard focuses on multifactor authentication and access protection. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context AuthPoint is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? AuthPoint focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
YubiKey 5 Series
YubiKey 5 Series is a hardware security product from Yubico, focused on hardware-backed authentication and login protection. Capabilities - FIDO2 and WebAuthn authentication: Supports the authentication protocols documented for the selected YubiKey device. - Smart-card authentication functions: Includes the smart-card capabilities documented for the selected key model. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. Use and operational context YubiKey 5 Series is relevant to teams deploying physical authenticators for account access when the requirement centers on providing the authentication protocols supported by the selected security key. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Physical hardware device; integration requirements depend on the selected model. Before adoption, review connector format, supported authentication protocols, account enrollment and recovery for a lost key. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? YubiKey 5 Series focuses on providing the authentication protocols supported by the selected security key. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
YubiKey Bio Series
YubiKey Bio Series is a hardware security product from Yubico, focused on biometric hardware authentication. Capabilities - Biometric security-key authentication: Adds the biometric user verification method documented for the selected Bio-series key. - FIDO2 and WebAuthn authentication: Provides the authentication protocols documented for the selected Bio-series key and edition. - Biometric enrollment workflow: Uses the documented enrollment and local user-verification workflow for the biometric authenticator. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. Use and operational context YubiKey Bio Series is relevant to teams evaluating hardware authentication with local biometric verification when the requirement centers on combining a security key with supported biometric user verification. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Physical hardware device; integration requirements depend on the selected model. Before adoption, review key edition, connector compatibility, supported login protocols and enrollment and recovery procedures. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? YubiKey Bio Series focuses on combining a security key with supported biometric user verification. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.