Documented Products & Services
Search and filter enterprise cybersecurity solutions by category, deployment architecture, supported operating systems, and verified pricing models. Default sorting is alphabetical.
Official leaderboards evaluated by technical benchmarks & scope...
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 Customer Identity Cloud (Auth0)
Developer-centric Customer Identity and Access Management (CIAM) platform powering secure consumer sign-in, social login, and API authorization.
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.
Okta Workforce Identity Cloud
Cloud-native IAM platform providing Single Sign-On (SSO), Adaptive Multi-Factor Authentication (MFA), Lifecycle Management, and Identity Governance (IGA).
Oligo Cloud Application Detection and Response
Oligo Cloud Application Detection and Response from Oligo Security focuses on application runtime threat detection and exploit investigation. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Dependency vulnerability analysis: Brings third-party software components into the vulnerability review process. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. Use and operational context Oligo Cloud Application Detection and Response is relevant to development and application security teams when the requirement centers on finding or addressing weaknesses in software. 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 languages or targets, scan placement, finding quality and how developers validate proposed fixes. 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? Oligo Cloud Application Detection and Response focuses on finding or addressing weaknesses in software. - 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.
OneTrust Privacy Automation
OneTrust Privacy Automation from OneTrust focuses on privacy operations and compliance workflow management. It is security governance and compliance technology used for coordinating controls, evidence and risk decisions. Capabilities - Risk assessment workflows: Structures how risks are recorded, evaluated and assigned for follow-up. - Framework mapping: Maps controls or evidence to the frameworks supported by the product, without itself constituting certification. - Third-party assessments: Adds supplier or external-party risk review to the documented governance workflow. - Policy and task coordination: Tracks governance policies and the actions assigned to their owners. - Trust communication: Provides a documented way to share security or compliance information with interested parties. Use and operational context OneTrust Privacy Automation is relevant to teams preparing audits or managing security governance when the requirement centers on coordinating controls, evidence and risk decisions. 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 frameworks, evidence ownership, assessment workflows and how the system fits existing governance responsibilities. 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? OneTrust Privacy Automation focuses on coordinating controls, evidence and risk decisions. - 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.
OneTrust Third-Party Management
OneTrust Third-Party Management from OneTrust focuses on third-party risk assessment and governance. It is security governance and compliance technology used for coordinating controls, evidence and risk decisions. Capabilities - Compliance evidence collection: Organizes the documentation used to demonstrate how controls are being managed. - Control monitoring: Tracks the controls or compliance signals included in the product's documented scope. - Risk assessment workflows: Structures how risks are recorded, evaluated and assigned for follow-up. - Framework mapping: Maps controls or evidence to the frameworks supported by the product, without itself constituting certification. - Third-party assessments: Adds supplier or external-party risk review to the documented governance workflow. - Policy and task coordination: Tracks governance policies and the actions assigned to their owners. - Trust communication: Provides a documented way to share security or compliance information with interested parties. Use and operational context OneTrust Third-Party Management is relevant to teams preparing audits or managing security governance when the requirement centers on coordinating controls, evidence and risk decisions. 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 frameworks, evidence ownership, assessment workflows and how the system fits existing governance responsibilities. 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? OneTrust Third-Party Management focuses on coordinating controls, evidence and risk decisions. - 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.
OpenText Carbonite Endpoint Backup
OpenText Carbonite Endpoint Backup from OpenText focuses on endpoint data backup and recovery. It is backup and recovery technology used for protecting recoverable data and organizing restoration. Capabilities - Backup and restore workflows: Creates recoverable copies of the data or workloads within the product's documented protection scope. - Endpoint backup: Addresses data protection for supported employee devices rather than only servers or cloud workloads. Use and operational context OpenText Carbonite Endpoint Backup is relevant to IT teams accountable for data resilience when the requirement centers on protecting recoverable data and organizing restoration. 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 protected workloads, retention settings, recovery location and a practical restore test using representative business data. 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? OpenText Carbonite Endpoint Backup focuses on protecting recoverable data and organizing restoration. - 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.