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...
Kroll Managed Detection and Response
Kroll Managed Detection and Response is a managed security service offered by Kroll. Its documented scope centers on managed threat 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. - Response and containment support: Assists with the response steps included in the service agreement and technical deployment. - Incident communication: Provides a channel for communicating findings and the actions required from the customer. Use and operational context Kroll's MDR service adds external monitoring and investigation to the customer's security operations. Review the environments included in the service, the evidence communicated with a finding and the responsibilities for carrying out an approved containment or remediation 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? Kroll 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.
Kroll Penetration Testing
Kroll Penetration Testing is a professional security engagement offered by Kroll. The service focuses on application and infrastructure 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. - Adversary simulation: Exercises authorized attack scenarios to assess defensive visibility and response. Use and operational context Kroll Penetration Testing 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? Kroll Penetration Testing 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.
LevelBlue Digital Forensics and Incident Response
LevelBlue Digital Forensics and Incident Response is a professional security engagement offered by LevelBlue. The service focuses on breach investigation and incident response. Capabilities - Incident investigation: Establishes what happened by examining relevant evidence and the scope of the incident. - Digital evidence analysis: Examines digital artifacts to support understanding the incident and its timeline. - Incident readiness services: Supports preparing for incidents before an emergency response engagement is required. Use and operational context LevelBlue Digital Forensics and 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? LevelBlue Digital Forensics and 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.
LevelBlue Managed Detection and Response
LevelBlue Managed Detection and Response is a managed security service offered by LevelBlue. 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. - 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. - Incident communication: Provides a channel for communicating findings and the actions required from the customer. Use and operational context LevelBlue Managed Detection and Response 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? LevelBlue 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.
Log360
Log360 from ManageEngine focuses on security log analysis and incident monitoring. It is security analytics technology used for collecting and analyzing security-relevant events. Capabilities - Security log collection: Brings supported logs and events into a common security analysis workflow. - Behavior analytics: Examines patterns associated with users or entities to help identify suspicious deviations. - 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. Use and operational context Log360 is ManageEngine's security analytics entry. Assess the event sources and detection workflows needed for the organization's environment, including how logs are searched, incidents are reviewed and security administration fits existing identity or infrastructure operations. Deployment and evaluation Deployment: Self-managed / on-premises option documented by the vendor. 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? Log360 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.
Logpoint SIEM
Logpoint SIEM from Logpoint focuses on security event correlation and investigation. It is security analytics technology used for collecting and analyzing security-relevant events. Capabilities - Security log collection: Brings supported logs and events into a common security analysis workflow. - 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. Use and operational context Logpoint 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? Logpoint 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.
Logpoint SOAR
Logpoint SOAR from Logpoint focuses on security orchestration and response automation. 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. Use and operational context Logpoint SOAR 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? Logpoint SOAR 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.
Lookout Mobile Endpoint Security
Lookout Mobile Endpoint Security from Lookout focuses on mobile device threat detection and risk assessment. It is mobile threat protection technology used for assessing threats affecting employee or customer mobile devices. Capabilities - Mobile threat detection: Assesses threats affecting the mobile devices covered by the product. - Application risk assessment: Examines the mobile application risks included in the documented assessment scope. - Phishing protection: Addresses mobile phishing threats within the protection scope described by the vendor. Use and operational context Lookout Mobile Endpoint Security is relevant to teams protecting mobile access to business systems when the requirement centers on assessing threats affecting employee or customer mobile devices. 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: Android, iOS. Supported versions and feature coverage depend on the vendor support matrix.. Check version requirements and feature differences before rollout. Before adoption, review device support, privacy settings, enterprise mobility integration and the handling of detected risk. 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? Lookout Mobile Endpoint Security focuses on assessing threats affecting employee or customer mobile devices. - 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.
Lookout Mobile Threat Defense
Lookout Mobile Threat Defense from Lookout focuses on mobile threat protection and device risk detection. It is mobile threat protection technology used for assessing threats affecting employee or customer mobile devices. Capabilities - Mobile threat detection: Assesses threats affecting the mobile devices covered by the product. - Application risk assessment: Examines the mobile application risks included in the documented assessment scope. - Device posture visibility: Brings supported device risk signals into the mobile security workflow. Use and operational context Lookout Mobile Threat Defense is relevant to teams protecting mobile access to business systems when the requirement centers on assessing threats affecting employee or customer mobile devices. 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: Android, iOS. Supported versions and feature coverage depend on the vendor support matrix.. Check version requirements and feature differences before rollout. Before adoption, review device support, privacy settings, enterprise mobility integration and the handling of detected risk. 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? Lookout Mobile Threat Defense focuses on assessing threats affecting employee or customer mobile devices. - 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.