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...
Wiz Code
Wiz Code from Wiz focuses on code-to-cloud security analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Code-to-cloud context: Links documented development findings with their context in the cloud environment. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Dynamic application security testing: Tests a running application to find exposed security weaknesses. - 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. - Infrastructure configuration analysis: Checks infrastructure definitions alongside application code where this capability is included. Use and operational context Wiz Code 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 Deployment: Cloud service / SaaS. 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? Wiz Code 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.
Wiz Defend
Wiz Defend from Wiz focuses on cloud threat detection and response. It is cloud security technology used for assessing cloud exposure or protecting running workloads. Capabilities - Cloud runtime investigation: Focuses the documented cloud detection workflow on suspicious workload activity. - Kubernetes security: Brings Kubernetes assets or configuration into the cloud security assessment workflow. - Attack path analysis: Connects multiple exposures to help explain how an attacker could reach a valuable target. - Runtime threat detection: Uses activity from running workloads to identify or respond to active threats. - Agentless assessment: Assesses the connected cloud environment using the agentless approach described by the vendor. - Vulnerability prioritization: Helps order remediation work using the risk context available in the platform. - Cloud detection and response: Supports investigation and response for suspicious activity in cloud environments. Use and operational context Wiz Defend is relevant to cloud and security teams working across accounts and workloads when the requirement centers on assessing cloud exposure or protecting running workloads. 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 cloud permissions required for onboarding, the assets assessed, runtime coverage and how findings reach remediation owners. 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? Wiz Defend focuses on assessing cloud exposure or protecting running workloads. - 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.
Wiz Runtime Sensor
Lightweight eBPF-powered runtime sensor providing real-time container threat detection and process-level incident response.
YubiHSM 2
YubiHSM 2 is a hardware security product from Yubico, focused on hardware-backed cryptographic key protection. Capabilities - Hardware-protected cryptographic operations: Provides the documented hardware boundary for supported key storage and cryptographic operations. - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Public key infrastructure services: Supports certificate issuance and trust infrastructure within the vendor's product scope. - Signing policy controls: Applies controls to how signing operations or protected keys can be used. - Hardware-backed key storage: Uses the documented hardware protection boundary for sensitive cryptographic material. Use and operational context YubiHSM 2 is relevant to teams integrating hardware-protected cryptography into applications when the requirement centers on protecting keys and supported cryptographic operations. 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 supported algorithms, integration interfaces, key lifecycle administration and backup 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? YubiHSM 2 focuses on protecting keys and supported cryptographic operations. - 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.
Zscaler Digital Experience
Zscaler Digital Experience from Zscaler focuses on user experience monitoring and connectivity diagnostics. It is digital experience monitoring technology used for investigating user connectivity and application experience. Capabilities - Application experience diagnostics: Uses the documented experience signals to investigate access or connectivity issues. - Zero trust network access: Grants access to the applications or resources defined by policy rather than relying solely on network location. - Data loss prevention controls: Adds sensitive-data policy enforcement to the access or traffic protection workflow. - Private application access: Connects authorized users to private applications according to access policy. - Internet traffic inspection: Inspects the traffic paths supported by the selected deployment and policy configuration. - Remote workforce access: Addresses secure connectivity for users working beyond a traditional office network. - WAN connectivity integration: Combines access security with the networking functions documented for the platform. - User experience monitoring: Helps investigate connectivity and application experience rather than only security alerts. Use and operational context Zscaler Digital Experience is relevant to IT teams troubleshooting access to business applications when the requirement centers on investigating user connectivity and application experience. 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 measurement coverage, troubleshooting context, privacy settings and how an observed experience issue is assigned for correction. 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? Zscaler Digital Experience focuses on investigating user connectivity and application experience. - 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.
Zscaler Internet Access
Zscaler Internet Access from Zscaler focuses on secure internet access and cloud-delivered inspection. It is secure access and networking technology used for applying access policy to users, applications or traffic. Capabilities - Internet-bound access security: Applies the documented Zscaler inspection and policy controls to internet access. - Zero trust network access: Grants access to the applications or resources defined by policy rather than relying solely on network location. - Secure web gateway: Applies security policy to users' internet-bound traffic. - Cloud access security broker: Provides policy and visibility for the cloud application interactions covered by the product. - Data loss prevention controls: Adds sensitive-data policy enforcement to the access or traffic protection workflow. - Private application access: Connects authorized users to private applications according to access policy. - Internet traffic inspection: Inspects the traffic paths supported by the selected deployment and policy configuration. - Remote workforce access: Addresses secure connectivity for users working beyond a traditional office network. Use and operational context Zscaler Internet Access is relevant to teams supporting distributed users and application access when the requirement centers on applying access policy to users, applications or traffic. 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 identity integration, application reachability, traffic routing and the user experience during a staged rollout. 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? Zscaler Internet Access focuses on applying access policy to users, applications or traffic. - 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.
Zscaler Private Access
Zscaler Private Access from Zscaler focuses on zero trust access to private applications. It is secure access and networking technology used for applying access policy to users, applications or traffic. Capabilities - Application-specific private access: Connects users to private applications using the documented zero trust access model. - Zero trust network access: Grants access to the applications or resources defined by policy rather than relying solely on network location. - Private application access: Connects authorized users to private applications according to access policy. - Remote workforce access: Addresses secure connectivity for users working beyond a traditional office network. Use and operational context Zscaler Private Access is relevant to teams supporting distributed users and application access when the requirement centers on applying access policy to users, applications or traffic. 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 identity integration, application reachability, traffic routing and the user experience during a staged rollout. 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? Zscaler Private Access focuses on applying access policy to users, applications or traffic. - 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.