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...
ThreatLocker Application Control
ThreatLocker Application Control from ThreatLocker focuses on application allowlisting and execution control. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Application execution approvals: Applies the documented approval or allowlisting decisions to application execution. - Application control: Restricts which applications can execute according to an administrator's policies. Use and operational context Application Control addresses which applications are permitted to execute. Review the approval and maintenance process for business software, including how an administrator handles a newly introduced application or a legitimate change that would otherwise be restricted. Deployment and evaluation Before adoption, review agent compatibility, policy tuning, alert investigation and the response actions available in the selected edition. 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? ThreatLocker Application Control focuses on endpoint protection and incident investigation. - 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.
ThreatLocker Elevation Control
ThreatLocker Elevation Control from ThreatLocker focuses on endpoint privilege elevation approval and control. It is privileged access management technology used for controlling elevated credentials and privileged sessions. Capabilities - Least-privilege enforcement: Restricts routine access so users and applications do not retain unnecessary elevated permissions. - Application privilege controls: Applies privilege decisions to application execution rather than granting unrestricted administrative rights. - Approval workflows: Routes access requests through the authorization process configured by the organization. Use and operational context ThreatLocker Elevation Control is relevant to administrators governing access to sensitive systems when the requirement centers on controlling elevated credentials and privileged sessions. 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 credential onboarding, access approvals, session controls and the operational impact of least-privilege policies. 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? ThreatLocker Elevation Control focuses on controlling elevated credentials and privileged sessions. - 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.
ThreatLocker Ringfencing
ThreatLocker Ringfencing from ThreatLocker focuses on application interaction and resource access restrictions. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Application resource restrictions: Applies the documented restrictions to how an application interacts with other software or resources. Use and operational context Ringfencing addresses the permitted interaction of applications with other applications or resources. Review the specific communication and resource-access boundaries required for a business application, then test its normal operation under the proposed restriction policy. Deployment and evaluation Before adoption, review agent compatibility, policy tuning, alert investigation and the response actions available in the selected edition. 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? ThreatLocker Ringfencing focuses on endpoint protection and incident investigation. - 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.
Tines
Tines from Tines focuses on security workflow automation and integration. It is security workflow automation technology used for coordinating repeatable security actions across tools. Capabilities - Workflow orchestration: Coordinates actions and information across the systems involved in a security process. - Human approval steps: Allows selected decisions to remain with an authorized person within the automation process. Use and operational context Tines is relevant to security operations teams standardizing investigation or response tasks when the requirement centers on coordinating repeatable security actions across tools. 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 connector permissions, failure handling, approval checkpoints and a test workflow using the organization's own tools. 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? Tines focuses on coordinating repeatable security actions across tools. - 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.
Torq Hyperautomation
Torq Hyperautomation from Torq focuses on security process automation and workflow orchestration. It is security workflow automation technology used for coordinating repeatable security actions across tools. Capabilities - Workflow orchestration: Coordinates actions and information across the systems involved in a security process. - Tool integrations: Connects the external applications supported by the product's integration model. - Incident case management: Tracks investigation context, decisions and response tasks around a security case. - Alert enrichment: Adds relevant context to alerts before an analyst or automated workflow makes a decision. Use and operational context Torq Hyperautomation is relevant to security operations teams standardizing investigation or response tasks when the requirement centers on coordinating repeatable security actions across tools. 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 connector permissions, failure handling, approval checkpoints and a test workflow using the organization's own tools. 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? Torq Hyperautomation focuses on coordinating repeatable security actions across tools. - 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.
TotalCloud
TotalCloud from Qualys focuses on cloud posture assessment and workload risk visibility. 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. - Container security: Addresses security issues in container images or running containerized applications within the documented scope. - Cloud compliance checks: Compares observed cloud settings with the control checks supported by the product. - Vulnerability prioritization: Helps order remediation work using the risk context available in the platform. Use and operational context TotalCloud 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 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? TotalCloud 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.
Traceable API Security
Traceable API Security from Traceable focuses on API discovery and threat detection. It is API security technology used for understanding and protecting application interfaces. Capabilities - API inventory and discovery: Identifies APIs so teams can establish which interfaces are included in their security review. - API posture assessment: Highlights API configuration or exposure issues for further assessment. - Sensitive data visibility: Helps identify where protected information appears in the APIs covered by the platform. - Runtime API attack protection: Protects or inspects live API traffic according to the product's enforcement model. - OWASP API risk coverage: Supports evaluating the API risk classes described in the vendor's documentation. Use and operational context Traceable API Security is relevant to security teams responsible for externally or internally exposed APIs when the requirement centers on understanding and protecting application interfaces. 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 API discovery coverage, traffic collection, authentication context and the enforcement model for live applications. 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? Traceable API Security focuses on understanding and protecting application interfaces. - 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.
Trend Vision One
Trend Vision One from Trend Micro focuses on security telemetry analysis and extended detection. It is extended detection and response technology used for connecting security signals across supported domains. Capabilities - Cross-domain detection: Connects observations from supported security domains rather than treating every alert as an isolated event. - Automated response: Connects detected activity with the response actions documented for the platform. - Cloud security telemetry: Adds cloud environment context where the platform's documented integrations include it. Use and operational context Trend Vision One is relevant to security operations teams investigating activity that spans multiple systems when the requirement centers on connecting security signals across supported domains. 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 telemetry coverage, correlation quality, response permissions and integration with existing protection products. 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? Trend Vision One focuses on connecting security signals across supported domains. - 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.
Trivy
Trivy is an open-source security scanner for developers and security engineers checking container images, code repositories, filesystem content and supported infrastructure targets. It helps surface known vulnerabilities and other security findings before artifacts move further through a delivery process. Capabilities - Vulnerability scanning: checks supported operating-system packages and application dependencies against security data. Results depend on the target, package metadata and available vulnerability records. - Repository scanning: accepts local or remote repositories. Vulnerability and secret scanning are enabled by default for repository targets; additional scanners can be selected explicitly. - Misconfiguration scanning: checks supported infrastructure definitions, including Terraform HCL, JSON and supported plan representations. This gives teams a way to review configuration risks alongside code changes. - Secret scanning: looks for supported patterns of exposed credentials in scanned content. Findings require review before deciding whether a credential needs revocation or rotation. - License scanning: provides license findings for supported components when the relevant scanner is enabled. Legal interpretation and policy decisions remain with the organization. - SBOM scanning: accepts supported CycloneDX and SPDX representations, including SPDX JSON, so a software inventory can become an input to vulnerability or license checks. Operating workflow Choose a scan target and scanner set, run the check locally or in a build pipeline, then route findings to the team responsible for the affected package or configuration. Establish filtering and exception rules deliberately so accepted risks do not hide new problems. Trivy downloads and maintains security databases; database access and update behavior matter when operating in restricted environments. Buyer and implementation questions - How is it deployed? Trivy can run as a command-line scanner locally or in CI workflows. Check the installation and database configuration for the intended environment. - What should a pilot test? Use representative images and repositories, confirm dependency coverage and output handling, and measure scan time and the triage effort created by findings. - Is it a substitute for runtime protection? Its role in this entry is scanning supported artifacts and configurations. Design runtime monitoring and incident response separately. - What should be configured before broader adoption? Decide which scanners run for each target, how findings affect build decisions, how exceptions are approved and how security data stays current.