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...
HarfangLab EDR
HarfangLab EDR from HarfangLab focuses on endpoint threat detection and investigation. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Endpoint detection and response: Connects endpoint alerts with investigation and response workflows rather than stopping at malware identification. - Malware prevention: Provides controls intended to detect or block malicious files and execution. Use and operational context HarfangLab EDR focuses on the investigation of activity recorded at endpoints. Review an actual alert and its related execution context, including the information analysts can retrieve and the response permissions granted to the operators who manage the incident. 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? HarfangLab EDR 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.
HarfangLab Endpoint Protection Platform
HarfangLab Endpoint Protection Platform from HarfangLab focuses on endpoint malware prevention and file threat analysis. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Behavioral threat detection: Analyzes suspicious execution patterns to help distinguish malicious activity from ordinary endpoint behavior. - Endpoint detection and response: Connects endpoint alerts with investigation and response workflows rather than stopping at malware identification. - Malware prevention: Provides controls intended to detect or block malicious files and execution. Use and operational context HarfangLab Endpoint Protection Platform is relevant to security teams administering employee devices or servers when the requirement centers on endpoint protection and incident investigation. 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 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? HarfangLab Endpoint Protection Platform 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.
Harmony Email and Collaboration
Harmony Email and Collaboration from Check Point focuses on email and collaboration threat protection. It is email and messaging security technology used for protecting or governing business messaging. Capabilities - Phishing detection: Analyzes email threats that try to mislead recipients into sharing information or taking unsafe actions. - Message remediation: Supports handling messages identified as suspicious or malicious. Use and operational context Check Point's email and collaboration entry addresses threats reaching users through supported productivity services. Establish the services included in the selected package and review how protection, account context and message remediation fit the organization's administration workflow. Deployment and evaluation Before adoption, review mail routing or API permissions, incident handling, legitimate-message delivery and the exact services included in the license. 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? Harmony Email and Collaboration focuses on protecting or governing business messaging. - 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.
Harmony Endpoint
Harmony Endpoint from Check Point focuses on endpoint prevention and threat response. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Application control: Restricts which applications can execute according to an administrator's policies. - Threat hunting: Supports searching endpoint activity for suspicious patterns that warrant deeper investigation. - Malware prevention: Provides controls intended to detect or block malicious files and execution. Use and operational context Harmony Endpoint is relevant to security teams administering employee devices or servers when the requirement centers on endpoint protection and incident investigation. 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 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? Harmony Endpoint 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.
Harmony SASE
Harmony SASE from Check Point focuses on secure remote access and cloud-delivered network security. 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. - Data loss prevention controls: Adds sensitive-data policy enforcement to the access or traffic protection workflow. - 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. Use and operational context Harmony SASE 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? Harmony SASE 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.
Heimdal DNS Security
Heimdal DNS Security from Heimdal focuses on DNS-layer threat blocking and traffic protection. It is DNS-layer protection technology used for using name-resolution traffic as a security control point. Capabilities - Protective DNS filtering: Uses DNS request handling as a control point for access to risky destinations. - Malicious domain blocking: Restricts access to domains that meet the configured threat or filtering rules. - Content category filtering: Applies filtering rules to the destination categories supported by the product. - DNS request visibility: Provides information about the DNS activity included in the deployment. - Threat intelligence support: Uses the documented threat information to inform DNS-based protection decisions. Use and operational context Heimdal DNS Security is relevant to organizations governing access to risky destinations when the requirement centers on using name-resolution traffic as a security control point. 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 DNS routing, filtering policy, exceptions and the effect of protective decisions on legitimate 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? Heimdal DNS Security focuses on using name-resolution traffic as a security control point. - 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.
Heimdal Patch and Asset Management
Heimdal Patch and Asset Management from Heimdal focuses on endpoint patching and asset visibility. 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. - Policy-driven automation: Turns repeatable endpoint administration tasks into configured management workflows. - Deployment scheduling: Supports planning when updates or management tasks should run. - Patch compliance reporting: Helps teams identify devices or software that still require update attention. - Software deployment: Distributes supported applications as part of the endpoint management workflow. Use and operational context Heimdal Patch and Asset 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 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? Heimdal Patch and Asset 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.
Heimdal Privileged Access Management
Heimdal Privileged Access Management from Heimdal focuses on endpoint privilege control and access administration. It is privileged access management technology used for controlling elevated credentials and privileged sessions. Capabilities - Privileged credential vaulting: Stores privileged credentials under centrally administered access controls. - Just-in-time access: Limits privileged access to the period or approval conditions defined for a task. - 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 Heimdal Privileged Access Management 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? Heimdal Privileged Access Management 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.
Hillstone CloudArmour
Hillstone CloudArmour from Hillstone Networks focuses on cloud workload protection and security 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. - Cloud workload protection: Focuses on protecting workloads running in the cloud rather than only inspecting account configuration. - Runtime threat detection: Uses activity from running workloads to identify or respond to active threats. Use and operational context Hillstone CloudArmour 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? Hillstone CloudArmour 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.