Verified Solutions Directory

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.

Showing 9 of 544 published solutions
Software Product

BlackBerry UEM

BlackBerry UEM from BlackBerry focuses on enterprise device management and access policy. It is unified endpoint management technology used for administering devices, business applications and endpoint policies. Capabilities - Device enrollment and management: Brings supported mobile or endpoint devices under enterprise management policy. - Application administration: Provides the documented controls for administering business applications on managed devices. - Device policy enforcement: Applies enterprise settings and policy to the supported device estate. - Mobile operating-system coverage: Includes the mobile platforms explicitly named in BlackBerry's support documentation. Use and operational context BlackBerry UEM is relevant to enterprise mobility and endpoint administration teams when the requirement centers on administering devices, business applications and endpoint policies. 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: Device management deployment; available platform and hosting options depend on the selected UEM offering. Before adoption, review device enrollment, application management, policy enforcement and support for the organization's device fleet. 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? BlackBerry UEM focuses on administering devices, business applications and endpoint policies. - 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.

Deployment: Device management deployment; available platform and hosting options depend on the selected UEM offering
Pricing: Pricing not publicly documented
Software Product

Blackpoint CompassOne

Blackpoint CompassOne from Blackpoint Cyber focuses on security visibility and response operations. It is extended detection and response technology used for connecting security signals across supported domains. Capabilities - Third-party security integrations: Uses the documented connections to bring external security products into the analysis workflow. - Endpoint telemetry: Adds endpoint context to the security domains covered by the product. - Cloud security telemetry: Adds cloud environment context where the platform's documented integrations include it. Use and operational context Blackpoint CompassOne 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? Blackpoint CompassOne 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.

Pricing: Pricing not publicly documented
Managed Service

Blackpoint MDR

Blackpoint MDR is a managed security service offered by Blackpoint Cyber. Its documented scope centers on managed threat detection and response. Capabilities - Managed threat monitoring: Adds a service team to the monitoring and assessment of supported security signals. - Human-led investigation: Provides analyst involvement in reviewing activity and deciding how a threat should be handled. - Response and containment support: Assists with the response steps included in the service agreement and technical deployment. - Security tool integration: Uses supported security tools or telemetry as part of the managed detection workflow. Use and operational context Blackpoint MDR is relevant to organizations seeking external security operations support when the requirement centers on adding expert monitoring and response to supported telemetry. 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: Managed service with provider-led monitoring and response within the agreed service scope. Before adoption, review supported data sources, response authority, escalation responsibilities and the actions included in the service agreement. 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? Blackpoint MDR focuses on adding expert monitoring and response to supported telemetry. - 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.

Deployment: Managed service with provider-led monitoring and response within the agreed service scope
Pricing: Pricing not publicly documented
Software Product

BloxOne Threat Defense

BloxOne Threat Defense from Infoblox focuses on DNS threat detection and protective DNS controls. It is DNS-layer protection technology used for using name-resolution traffic as a security control point. Capabilities - DNS-layer threat defense: Uses DNS visibility and policy as the protection point for the deployment described by Infoblox. - 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. - 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 BloxOne Threat Defense 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 Deployment: Cloud service / SaaS. 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? BloxOne Threat Defense 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.

Deployment: Cloud service / SaaS
Pricing: Pricing not publicly documented
Managed Service

Blumira Managed Detection and Response

Blumira Managed Detection and Response is a managed security service offered by Blumira. Its documented scope centers on managed security monitoring and response. Capabilities - Managed threat monitoring: Adds a service team to the monitoring and assessment of supported security signals. - Human-led investigation: Provides analyst involvement in reviewing activity and deciding how a threat should be handled. - Threat hunting services: Adds a proactive search for suspicious activity to the managed service scope described by the vendor. - Response and containment support: Assists with the response steps included in the service agreement and technical deployment. - Security tool integration: Uses supported security tools or telemetry as part of the managed detection workflow. - Incident communication: Provides a channel for communicating findings and the actions required from the customer. Use and operational context Blumira's managed service extends the monitoring workflow described for Blumira SIEM. Review how the service team assesses an alert using the collected workspace context and how agreed response actions are communicated and recorded for the customer. Deployment and evaluation Deployment: Managed service with provider-led monitoring and response within the agreed service scope. Before adoption, review supported data sources, response authority, escalation responsibilities and the actions included in the service agreement. 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? Blumira Managed Detection and Response focuses on adding expert monitoring and response to supported telemetry. - 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.

Deployment: Managed service with provider-led monitoring and response within the agreed service scope
Pricing: Pricing not publicly documented
Software Product

Blumira SIEM

Blumira SIEM from Blumira focuses on security log analytics and threat detection. It is security analytics technology used for collecting and analyzing security-relevant events. Capabilities - Event correlation: Connects related observations so analysts can investigate a potential incident in context. - Detection rules and analytics: Supports defining or maintaining the logic used to identify suspicious activity. - Threat hunting: Lets analysts investigate hypotheses across the security data available in the platform. - Incident investigation: Organizes evidence and investigative activity around incidents or cases. - Response automation: Connects detection and investigation with the automated actions documented for the offering. - Third-party integrations: Connects security data sources or response tools supported by the platform. - Security reporting: Produces views or reports for communicating detected issues and operational activity. Use and operational context Blumira 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 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? Blumira 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.

Pricing: Pricing not publicly documented
Software Product

Bot Manager

Bot Manager from Radware focuses on automated traffic classification and bot mitigation. 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. - Account abuse protection: Addresses the automated account attacks included in the vendor's protection scope. - Scraping abuse controls: Applies the documented controls for automated extraction or scraping activity. - Application integration: Provides the supported mechanisms for bringing bot controls into application traffic flows. Use and operational context Bot Manager 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? Bot Manager 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.

Pricing: Pricing not publicly documented
Software Product

Bugcrowd Attack Surface Management

Bugcrowd Attack Surface Management from Bugcrowd focuses on external asset discovery and exposure assessment. 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. - Asset attribution: Helps establish how discovered assets relate to the organization or its business units. - Remediation prioritization: Supports ordering follow-up work on the exposures assessed by the product. Use and operational context Bugcrowd Attack Surface Management is relevant to teams reviewing externally observable exposure when the requirement centers on discovering and assessing internet-facing 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 Deployment: Cloud service / SaaS. 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? Bugcrowd Attack Surface Management 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.

Deployment: Cloud service / SaaS
Pricing: Pricing not publicly documented
professional_service

Bugcrowd Bug Bounty

Bugcrowd Bug Bounty is a professional security engagement offered by Bugcrowd. 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. - 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 Bugcrowd Bug Bounty 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: 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? Bugcrowd 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.

Deployment: Professional service delivered within an agreed engagement scope
Pricing: Pricing not publicly documented
Page 8 of 61