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...
InsightVM
InsightVM from Rapid7 focuses on vulnerability assessment and remediation prioritization. It is vulnerability and exposure management technology used for identifying and prioritizing security weaknesses. Capabilities - Vulnerability scanning: Finds potential weaknesses that can be reviewed and prioritized for remediation. - Risk-based prioritization: Uses the available risk context to help order remediation work. Use and operational context InsightVM is relevant to teams planning vulnerability remediation across assets when the requirement centers on identifying and prioritizing security weaknesses. 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 scan scope, credentialed assessment options, prioritization inputs and how remediation owners verify closure. 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? InsightVM focuses on identifying and prioritizing security weaknesses. - 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.
Intezer
Intezer from Intezer focuses on malware analysis and security alert investigation. It is malware analysis technology used for examining suspicious files or observed execution behavior. Capabilities - Threat indicator extraction: Produces indicators that can inform investigation or be used in supported security workflows. - Analysis reporting: Organizes analysis results so analysts can review the observed behavior and threat assessment. - Analysis automation: Connects analysis with the automation or integration mechanisms supplied by the vendor. Use and operational context Intezer is relevant to analysts triaging samples and investigating threats when the requirement centers on examining suspicious files or observed execution behavior. 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 samples, analysis visibility, submission privacy and how findings are reviewed before operational decisions. 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? Intezer focuses on examining suspicious files or observed execution behavior. - 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.
Invicti
Invicti from Invicti focuses on dynamic application security testing and vulnerability validation. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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. - License risk analysis: Helps teams review licensing obligations associated with third-party components. Use and operational context Invicti 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? Invicti 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.
Island Enterprise Browser
Island Enterprise Browser from Island focuses on enterprise browser access controls and data protection. It is enterprise browser technology used for administering browser-based work and application access. Capabilities - Enterprise browsing policies: Applies the documented browser controls to supported work sessions and applications. - Browser data protection: Addresses the data-handling controls included in the browser offering. - Identity-aware application access: Connects browser access with the identities or policies covered by the product. - Unmanaged device access: Addresses access from personal or unmanaged devices within the supported deployment model. - Browser activity visibility: Provides records or visibility into the browsing activity covered by the product. Use and operational context Island Enterprise Browser is relevant to organizations governing business browsing and application sessions when the requirement centers on administering browser-based work and application access. 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 browser deployment, application compatibility, access policies and the effect of data controls on legitimate workflows. 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? Island Enterprise Browser focuses on administering browser-based work and application access. - 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.
Ivanti Neurons for Patch Management
Ivanti Neurons for Patch Management from Ivanti focuses on software patch deployment and remediation. It is endpoint administration and patching technology used for keeping supported software and devices maintained. Capabilities - Automated patch deployment: Helps distribute software updates across the endpoints included in the management scope. - Third-party application patching: Brings supported nonoperating-system applications into the software update process. - Endpoint inventory: Provides information about the managed devices and software that influence patching decisions. - Policy-driven automation: Turns repeatable endpoint administration tasks into configured management workflows. - Patch compliance reporting: Helps teams identify devices or software that still require update attention. Use and operational context Ivanti Neurons for Patch Management is relevant to IT teams managing software updates across a device fleet when the requirement centers on keeping supported software and devices maintained. 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. Operating systems listed in the available documentation: Windows, macOS, Linux. Supported versions and feature coverage depend on the vendor support matrix.. Check version requirements and feature differences before rollout. Before adoption, review application coverage, deployment scheduling, restart behavior and a pilot group that represents production devices. 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? Ivanti Neurons for Patch Management focuses on keeping supported software and devices maintained. - 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.
Ivanti Neurons for Risk-Based Vulnerability Management
Ivanti Neurons for Risk-Based Vulnerability Management from Ivanti focuses on vulnerability risk scoring and prioritization. It is vulnerability and exposure management technology used for identifying and prioritizing security weaknesses. Capabilities - Vulnerability scanning: Finds potential weaknesses that can be reviewed and prioritized for remediation. - Risk-based prioritization: Uses the available risk context to help order remediation work. - Remediation tracking: Helps teams move from identified exposures to assigned correction work. - Exposure reporting: Provides views for communicating the assessed exposure and progress of remediation work. Use and operational context Ivanti Neurons for Risk-Based Vulnerability Management is relevant to teams planning vulnerability remediation across assets when the requirement centers on identifying and prioritizing security weaknesses. 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 scan scope, credentialed assessment options, prioritization inputs and how remediation owners verify closure. 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? Ivanti Neurons for Risk-Based Vulnerability Management focuses on identifying and prioritizing security weaknesses. - 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.
Ivanti Neurons for Zero Trust Access
Ivanti Neurons for Zero Trust Access from Ivanti focuses on identity-aware remote application access. It is secure access and networking technology used for applying access policy to users, applications or traffic. Capabilities - Zero trust network access: Grants access to the applications or resources defined by policy rather than relying solely on network location. - Device posture checks: Uses the condition of the connecting device as an input to access decisions. - Private application access: Connects authorized users to private applications according to access policy. Use and operational context Ivanti Neurons for Zero Trust 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? Ivanti Neurons for Zero Trust 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.
JFrog Advanced Security
JFrog Advanced Security from JFrog focuses on software supply chain analysis and contextual security testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Contextual artifact analysis: Adds the contextual assessment functions documented alongside JFrog's artifact scanning workflow. - 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 JFrog Advanced Security 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? JFrog Advanced Security 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.
JFrog Xray
JFrog Xray from JFrog focuses on artifact vulnerability and license risk scanning. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Artifact-focused component scanning: Assesses supported software artifacts rather than treating application security only as source-code analysis. - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - 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 JFrog Xray 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? JFrog Xray 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.