Documented Products & Services
Search and filter enterprise cybersecurity solutions by category, deployment architecture, supported operating systems, and verified pricing models. Default sorting is alphabetical. Position does not imply editorial ranking or performance superiority.
ConnectWise RMM
ConnectWise RMM from ConnectWise focuses on endpoint monitoring and patch administration. 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. - Remote endpoint management: Supports administering devices without relying on an administrator being physically present. - Patch compliance reporting: Helps teams identify devices or software that still require update attention. Use and operational context ConnectWise RMM 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 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? ConnectWise RMM 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.
ConnectWise SIEM
ConnectWise SIEM from ConnectWise focuses on security event analytics and monitoring. It is security analytics technology used for collecting and analyzing security-relevant events. Capabilities - Security log collection: Brings supported logs and events into a common security analysis workflow. - Event correlation: Connects related observations so analysts can investigate a potential incident in context. - Threat hunting: Lets analysts investigate hypotheses across the security data available in the platform. - Third-party integrations: Connects security data sources or response tools supported by the platform. Use and operational context ConnectWise SIEM is relevant to security operations teams investigating alerts and incidents when the requirement centers on collecting and analyzing security-relevant events. 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 source onboarding, detection content, query performance, data retention and the cost implications of event volume. 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? ConnectWise SIEM focuses on collecting and analyzing security-relevant events. - 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.
Continuous Threat Detection
Continuous Threat Detection from Claroty focuses on industrial network monitoring and threat detection. It is operational technology security technology used for understanding or protecting industrial and connected assets. Capabilities - Operational asset discovery: Builds visibility into the operational or connected assets covered by the deployment. - Industrial threat monitoring: Examines activity in operational environments for signs requiring security investigation. - Operational exposure assessment: Assesses weaknesses or exposure affecting the supported operational assets. - Controlled remote access: Provides the documented access controls for external or remote work on operational systems. - Operational segmentation: Provides protection mechanisms for limiting exposure or traffic pathways within the operational environment. Use and operational context Continuous Threat Detection is relevant to teams securing industrial, healthcare or other operational environments when the requirement centers on understanding or protecting industrial and connected assets. 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 asset and protocol coverage, discovery impact, change-control requirements and the availability needs of operational systems. 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? Continuous Threat Detection focuses on understanding or protecting industrial and connected assets. - 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.
Contrast Assess
Contrast Assess from Contrast Security focuses on interactive application security testing. 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. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. - Interactive application testing: Uses information from application execution to assess security behavior and vulnerabilities. Use and operational context Contrast Assess 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? Contrast Assess 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.
Contrast Protect
Contrast Protect from Contrast Security focuses on application runtime attack protection. It is application security technology used for finding or addressing weaknesses in software. Capabilities - In-application runtime protection: Applies the documented protection controls within the running application's execution context. - Application attack detection: Identifies the application attacks covered by the runtime protection model. - Runtime instrumentation: Uses the application's documented instrumentation approach to obtain runtime security context. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Runtime application protection: Protects the running application using the runtime controls documented for the product. Use and operational context Contrast Protect 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? Contrast Protect 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.
Contrast SCA
Contrast SCA from Contrast Security focuses on dependency vulnerability analysis. 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. - License risk analysis: Helps teams review licensing obligations associated with third-party components. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Contrast SCA 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? Contrast SCA 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.
Core Impact
Core Impact from Fortra focuses on penetration testing and exploit validation. It is authorized security testing technology or service used for assessing weaknesses and validating attack possibilities. Capabilities - Authorized exploit validation: Supports assessing whether selected vulnerabilities can be exploited within an approved testing engagement. - Authorized security testing: Evaluates security weaknesses within an explicitly agreed and authorized test scope. - Exploitability validation: Assesses whether a weakness can be used in the documented testing workflow. - Application security testing: Brings supported application targets into the authorized assessment scope. - Remediation reporting: Documents the assessed issues so the responsible team can plan corrections. - Adversary simulation: Exercises authorized attack scenarios to assess defensive visibility and response. Use and operational context Core Impact is relevant to organizations defining an approved security assessment scope when the requirement centers on assessing weaknesses and validating attack possibilities. 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 test authorization, target coverage, operational safeguards and the quality of findings and remediation verification. 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? Core Impact focuses on assessing weaknesses and validating attack possibilities. - 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.
Corelight Open NDR Platform
Corelight Open NDR Platform from Corelight focuses on network security telemetry and threat detection. It is network detection and response technology used for turning observed traffic into security evidence. Capabilities - Zeek-based network evidence: Uses Zeek-derived network evidence in the analysis scope documented by Corelight. - Suricata detection context: Includes the documented Suricata-related detection context in its network security workflow. - Behavioral network detection: Looks for network activity that differs from expected patterns. - Protocol-aware visibility: Uses protocol-level context from the traffic data covered by the product. - Investigation telemetry: Provides evidence that can help analysts investigate suspicious network activity. - Threat hunting workflows: Supports proactive investigation using the network data retained or analyzed by the platform. Use and operational context Corelight Open NDR Platform is relevant to analysts investigating network activity and potential lateral movement when the requirement centers on turning observed traffic into security evidence. 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 traffic visibility, sensor placement, encrypted-traffic limitations and the evidence available for incident investigation. 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? Corelight Open NDR Platform focuses on turning observed traffic into security evidence. - 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.
Cortex Cloud
Cortex Cloud from Palo Alto Networks focuses on cloud posture management and runtime protection. It is cloud security technology used for assessing cloud exposure or protecting running workloads. Capabilities - Cloud security posture management: Finds cloud configuration risks so teams can prioritize corrections across connected environments. - Cloud workload protection: Focuses on protecting workloads running in the cloud rather than only inspecting account configuration. - Cloud entitlement analysis: Examines cloud permissions to identify overly broad or risky access. - Runtime threat detection: Uses activity from running workloads to identify or respond to active threats. - 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 Cortex Cloud 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? Cortex Cloud 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.