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...
Sophos Incident Response
Sophos Incident Response is a professional security engagement offered by Sophos. The service focuses on incident investigation and containment 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. - Root-cause assessment: Helps identify the factors associated with the incident so remediation can address the underlying exposure. Use and operational context Sophos's incident response service addresses investigation and response during a cyber incident. Agree the affected systems, access required by responders and the decision process for containment, with a clear operational handoff for recovery and longer-term remediation work. 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? Sophos 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.
Sophos MDR
Sophos MDR is a managed security service offered by Sophos. 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. - 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 Sophos MDR adds a managed security operations workflow to the telemetry supported by the service. Review how the planned integrations supply incident context, what actions the service team can take and which decisions or tasks remain with the customer's administrators. 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? Sophos 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.
Sophos XDR
Sophos XDR from Sophos focuses on cross-domain threat detection and investigation. It is extended detection and response technology used for connecting security signals across supported domains. Capabilities - Cross-domain detection: Connects observations from supported security domains rather than treating every alert as an isolated event. - Automated response: Connects detected activity with the response actions documented for the platform. - 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 Sophos XDR 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? Sophos XDR 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.
SpamTitan
SpamTitan from TitanHQ focuses on email spam filtering and phishing 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. - Business email compromise detection: Focuses on impersonation and social engineering patterns that may not involve a malicious attachment. - Attachment threat analysis: Examines or evaluates attachments using the mechanisms documented by the vendor. - Message remediation: Supports handling messages identified as suspicious or malicious. - Outbound data controls: Adds policy controls for the movement of sensitive information through supported email workflows. - Email retention and search: Preserves and searches message data for the retention or investigation use cases described by the vendor. - Behavioral email analysis: Uses communication behavior or contextual signals in email threat analysis. Use and operational context SpamTitan is relevant to teams administering email protection and message investigation when the requirement centers on protecting or governing business messaging. 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 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? SpamTitan 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.
Spectra Analyze
Spectra Analyze from ReversingLabs focuses on file threat analysis and malware investigation. It is malware analysis technology used for examining suspicious files or observed execution behavior. Capabilities - Static file analysis: Examines file characteristics without relying only on execution behavior. - Threat indicator extraction: Produces indicators that can inform investigation or be used in supported security workflows. - Analysis reporting: Organizes analysis results so analysts can review the observed behavior and threat assessment. - Analysis automation: Connects analysis with the automation or integration mechanisms supplied by the vendor. Use and operational context Spectra Analyze is relevant to analysts triaging samples and investigating threats when the requirement centers on examining suspicious files or observed execution behavior. 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 samples, analysis visibility, submission privacy and how findings are reviewed before operational decisions. 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? Spectra Analyze focuses on examining suspicious files or observed execution behavior. - 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.
Spectra Assure
Spectra Assure from ReversingLabs focuses on software package risk analysis and supply chain protection. It is software supply chain security technology used for assessing the trust and risk of software artifacts. Capabilities - Software package inspection: Examines the software artifacts within the product's documented analysis scope. - Malicious component detection: Looks for malicious content in the supported software supply chain assets. - Release risk assessment: Helps teams review the security state of software before or alongside release decisions. Use and operational context Spectra Assure is relevant to teams reviewing dependencies, build outputs or releases when the requirement centers on assessing the trust and risk of software artifacts. 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 artifact coverage, policy thresholds, evidence behind findings and the point at which results affect release decisions. 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? Spectra Assure focuses on assessing the trust and risk of software artifacts. - 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.
Splunk Enterprise Security
Splunk Enterprise Security from Splunk focuses on security analytics and incident investigation. It is security analytics technology used for collecting and analyzing security-relevant events. Capabilities - 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. Use and operational context Splunk Enterprise Security 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? Splunk Enterprise Security 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.
Splunk SOAR
Splunk SOAR from Splunk focuses on security workflow orchestration and automation. It is security workflow automation technology used for coordinating repeatable security actions across tools. Capabilities - Splunk response playbooks: Builds repeatable security response workflows using the documented playbook and integration model. - Workflow orchestration: Coordinates actions and information across the systems involved in a security process. - Playbook automation: Packages repeatable investigation or response steps into reusable workflows. - Tool integrations: Connects the external applications supported by the product's integration model. - Incident case management: Tracks investigation context, decisions and response tasks around a security case. Use and operational context Splunk 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? Splunk 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.
Sprinto
Sprinto from Sprinto focuses on security compliance monitoring and evidence workflows. It is security governance and compliance technology used for coordinating controls, evidence and risk decisions. Capabilities - Control monitoring: Tracks the controls or compliance signals included in the product's documented scope. - Risk assessment workflows: Structures how risks are recorded, evaluated and assigned for follow-up. - Audit preparation: Helps coordinate the information and activities required to prepare for an audit. - Third-party assessments: Adds supplier or external-party risk review to the documented governance workflow. - Policy and task coordination: Tracks governance policies and the actions assigned to their owners. - Trust communication: Provides a documented way to share security or compliance information with interested parties. Use and operational context Sprinto is relevant to teams preparing audits or managing security governance when the requirement centers on coordinating controls, evidence and risk decisions. 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 frameworks, evidence ownership, assessment workflows and how the system fits existing governance responsibilities. 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? Sprinto focuses on coordinating controls, evidence and risk decisions. - 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.