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...
Grip SaaS Security Control Plane
Grip SaaS Security Control Plane from Grip Security focuses on saaS discovery and identity risk assessment. It is SaaS security technology used for assessing application usage, configuration or identity risk. Capabilities - SaaS application discovery: Finds SaaS usage so teams can understand their application footprint. - SaaS identity risk analysis: Reviews identity and access issues associated with supported SaaS services. - Third-party application visibility: Shows connected applications or integrations that can introduce additional access paths. - Application governance workflows: Helps teams take action on application access or usage decisions. Use and operational context Grip SaaS Security Control Plane is relevant to teams overseeing business SaaS applications when the requirement centers on assessing application usage, configuration or identity risk. 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 services, connector permissions, findings ownership and the response process for risky access or configurations. 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? Grip SaaS Security Control Plane focuses on assessing application usage, configuration or identity risk. - 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.
Guardian
Guardian from Nozomi Networks focuses on operational network asset 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. - Industrial network analysis: Uses the documented network visibility to understand activity within operational environments. Use and operational context Nozomi Guardian addresses operational network visibility and threat detection. Review where its monitoring components will be positioned, which assets and protocols can be assessed and how its observations are reviewed by the operational and security teams. 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? Guardian 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.
Guardicore Segmentation
Guardicore Segmentation from Akamai focuses on workload microsegmentation and policy enforcement. It is network security technology used for controlling communications and inspecting traffic. Capabilities - Workload communication segmentation: Uses the documented workload communication view to define and assess segmentation policies. - Network segmentation: Separates access between network or workload groups to constrain unnecessary communication. - Lateral movement controls: Supports evaluating or restricting pathways used to move between systems after initial compromise. Use and operational context Guardicore Segmentation is relevant to network teams protecting branches, data centers or workloads when the requirement centers on controlling communications and inspecting 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 traffic throughput, network topology, policy administration and the effect of inspection on business 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? Guardicore Segmentation focuses on controlling communications and inspecting 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.
HCL BigFix
HCL BigFix from HCLSoftware focuses on endpoint lifecycle management and patch remediation. It is endpoint administration and patching technology used for keeping supported software and devices maintained. Capabilities - Fixlet-based endpoint actions: Uses the documented Fixlet model to organize endpoint assessment and remediation actions. - 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. - 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 HCL BigFix 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. 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? HCL BigFix 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.
HUMAN Account Defender
HUMAN Account Defender from HUMAN Security focuses on account abuse detection and risk assessment. It is account risk and abuse protection technology used for assessing suspicious login or account activity. Capabilities - Account risk analysis: Assesses the signals associated with a user's account or login activity. - Behavioral user signals: Uses observed activity patterns as part of account risk assessment. - Application risk integration: Provides the documented mechanism for bringing account risk signals into an application workflow. Use and operational context HUMAN Account Defender is relevant to teams protecting customer account workflows when the requirement centers on assessing suspicious login or account activity. 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 signal collection, risk thresholds, response integration and the effect of decisions on legitimate account holders. 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? HUMAN Account Defender focuses on assessing suspicious login or account activity. - 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.
HUMAN Bot Defender
HUMAN Bot Defender from HUMAN Security focuses on bot detection and automated abuse protection. It is automated traffic protection technology used for distinguishing and controlling abusive automated requests. Capabilities - Automated traffic detection: Identifies automated requests within the traffic processed by the service. - Behavioral traffic analysis: Uses request behavior as part of the automated-traffic assessment. - Application integration: Provides the supported mechanisms for bringing bot controls into application traffic flows. Use and operational context HUMAN Bot Defender is relevant to application teams dealing with bots and automated abuse when the requirement centers on distinguishing and controlling abusive automated requests. 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 integration paths, treatment of legitimate automation, challenge behavior and the effect on real users. 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? HUMAN Bot Defender focuses on distinguishing and controlling abusive automated requests. - 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.
HackerOne Assets
HackerOne Assets from HackerOne focuses on external asset inventory and attack surface visibility. It is external attack surface technology used for discovering and assessing internet-facing assets. Capabilities - External asset discovery: Finds internet-facing assets that are relevant to the organization's exposure. - Attack surface inventory: Provides a record of the externally visible assets included in the assessment scope. - Exposure assessment: Identifies potential weaknesses that warrant investigation or remediation. - Remediation prioritization: Supports ordering follow-up work on the exposures assessed by the product. Use and operational context HackerOne Assets addresses visibility into the external assets included in a security review. Assess how the asset inventory establishes ownership and testing scope, and how discovered exposure informs the authorized testing or remediation process. Deployment and evaluation Before adoption, review asset ownership, discovery scope, validation of findings and handoff to remediation teams. 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? HackerOne Assets focuses on discovering and assessing internet-facing 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.
HackerOne Bug Bounty
HackerOne Bug Bounty is a professional security engagement offered by HackerOne. The service focuses on coordinated researcher vulnerability discovery. Capabilities - 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. - Retesting workflows: Supports reviewing whether a correction has addressed an identified weakness. - Researcher-led testing: Uses the coordinated researcher model described by the service provider. - Adversary simulation: Exercises authorized attack scenarios to assess defensive visibility and response. Use and operational context HackerOne's bug bounty offering coordinates researcher participation under a defined program policy. Review target scope, reporting expectations and triage responsibilities, including how a submitted vulnerability is validated and passed to the team responsible for correction. Deployment and evaluation Deployment: Professional service delivered within an agreed engagement scope. 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? HackerOne Bug Bounty focuses on assessing weaknesses and validating attack possibilities. - What should a proof of concept establish? Test the listed capabilities against representative service deliverables, 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.
HackerOne Pentest
HackerOne Pentest is a professional security engagement offered by HackerOne. The service focuses on authorized application security testing. Capabilities - 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. - Retesting workflows: Supports reviewing whether a correction has addressed an identified weakness. - Researcher-led testing: Uses the coordinated researcher model described by the service provider. - Adversary simulation: Exercises authorized attack scenarios to assess defensive visibility and response. Use and operational context HackerOne Pentest addresses a scoped, authorized testing engagement. Evaluate how targets and test restrictions are agreed, how findings are communicated during the engagement and how the required reporting and remediation verification are delivered. Deployment and evaluation Deployment: Professional service delivered within an agreed engagement scope. 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? HackerOne Pentest focuses on assessing weaknesses and validating attack possibilities. - What should a proof of concept establish? Test the listed capabilities against representative service deliverables, 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.