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...
Luna HSM
Luna HSM is a hardware security product from Thales, focused on hardware-backed cryptographic key protection. Capabilities - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Public key infrastructure services: Supports certificate issuance and trust infrastructure within the vendor's product scope. - Code signing workflows: Supports signing software or artifacts using the product's documented key access and policy model. - Signing policy controls: Applies controls to how signing operations or protected keys can be used. - Hardware-backed key storage: Uses the documented hardware protection boundary for sensitive cryptographic material. Use and operational context Luna HSM is relevant to teams operating cryptographic trust services when the requirement centers on managing protected keys, certificates or signing operations. 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: Physical hardware device; integration requirements depend on the selected model. Before adoption, review key ownership, certificate discovery, integration requirements and recovery procedures for critical trust infrastructure. 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? Luna HSM focuses on managing protected keys, certificates or signing operations. - 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.
Malwarebytes ThreatDown
Malwarebytes ThreatDown from Malwarebytes focuses on business endpoint protection and threat response. 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. - 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 Malwarebytes ThreatDown 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? Malwarebytes ThreatDown 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.
Managed Detection and Response
Managed Detection and Response is a managed security service offered by Orange Cyberdefense. 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. - Incident communication: Provides a channel for communicating findings and the actions required from the customer. Use and operational context This provider's MDR entry should be assessed against a defined monitoring and response scope. Review the systems supplying security data, the service team's investigation role and the customer's escalation contacts, including authorization for each proposed response action. 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? 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.
Managed Security Services
Managed Security Services is a managed security service offered by NTT DATA. Its documented scope centers on security monitoring and managed protection operations. Capabilities - Managed security monitoring: Adds an operational service team to the security monitoring workflow. - Security operations support: Provides assistance with the protection operations included in the service agreement. - Threat detection and investigation: Helps review suspicious activity and establish what action is required. Use and operational context Managed Security Services is relevant to organizations assigning defined security tasks to an external provider when the requirement centers on supporting ongoing protection and security operations. 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 the systems in scope, operating responsibilities, communication arrangements and agreed service outcomes. 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? Managed Security Services focuses on supporting ongoing protection and security operations. - 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.
Mandiant Incident Response
Mandiant Incident Response is a professional security engagement offered by Google Cloud. The service focuses on incident investigation and recovery support. Capabilities - Incident investigation: Establishes what happened by examining relevant evidence and the scope of the incident. - Containment planning: Helps define steps intended to reduce an incident's immediate spread or effect. - Digital evidence analysis: Examines digital artifacts to support understanding the incident and its timeline. - Recovery assistance: Assists with the recovery tasks included in the engagement and agreed response plan. - Incident readiness services: Supports preparing for incidents before an emergency response engagement is required. Use and operational context Mandiant Incident Response is relevant to organizations responding to a breach or improving incident readiness when the requirement centers on investigating and managing cybersecurity incidents. 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 engagement scope, evidence handling, response authority and the responsibilities of internal and external responders. 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? Mandiant Incident Response focuses on investigating and managing cybersecurity incidents. - 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.
Mandiant Incident Response Services
Emergency incident response, digital forensics, crisis management, and compromised environment remediation.
Mandiant Managed Defense
Premier managed detection and response service led by Mandiant frontline threat hunters and elite analysts.
Mend Container
Mend Container from Mend.io focuses on container vulnerability scanning. It is cloud security technology used for assessing cloud exposure or protecting running workloads. Capabilities - Container security: Addresses security issues in container images or running containerized applications within the documented scope. - Kubernetes security: Brings Kubernetes assets or configuration into the cloud security assessment workflow. - Vulnerability prioritization: Helps order remediation work using the risk context available in the platform. Use and operational context Mend Container 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? Mend Container 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.
Mend SAST
Mend SAST from Mend.io focuses on source code vulnerability detection. 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. - Developer workflow integration: Places security findings into the development processes documented by the vendor. Use and operational context Mend SAST 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? Mend SAST 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.