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.
Adlumin XDR
Adlumin XDR from N-able focuses on cross-domain threat detection and security 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. - Threat hunting: Supports proactive investigation across the telemetry included in the deployment. - 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 Adlumin 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? Adlumin 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.
AhnLab EDR
AhnLab EDR from AhnLab focuses on endpoint threat detection and investigation. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Behavioral threat detection: Analyzes suspicious execution patterns to help distinguish malicious activity from ordinary endpoint behavior. - 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 AhnLab EDR 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? AhnLab EDR 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.
AhnLab V3
AhnLab V3 from AhnLab focuses on endpoint malware prevention and protection. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Malware prevention: Provides controls intended to detect or block malicious files and execution. - Cloud workload protection: Extends the documented protection scope beyond employee workstations to cloud-hosted workloads. Use and operational context AhnLab V3 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? AhnLab V3 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.
Akamai API Security
Akamai API Security from Akamai focuses on API discovery and behavioral threat detection. It is API security technology used for understanding and protecting application interfaces. Capabilities - API inventory and discovery: Identifies APIs so teams can establish which interfaces are included in their security review. - API behavior analysis: Uses observed API behavior to investigate activity that differs from expected usage. - API posture assessment: Highlights API configuration or exposure issues for further assessment. - Sensitive data visibility: Helps identify where protected information appears in the APIs covered by the platform. - Runtime API attack protection: Protects or inspects live API traffic according to the product's enforcement model. - API authentication risk assessment: Brings authentication and authorization behavior into the API security review. - OWASP API risk coverage: Supports evaluating the API risk classes described in the vendor's documentation. Use and operational context Akamai API Security gives teams a way to establish API visibility and investigate API activity. The evaluation should follow an API from discovery through risk review, including what traffic context is available when authentication or sensitive-data exposure becomes a concern. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review API discovery coverage, traffic collection, authentication context and the enforcement model for live 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? Akamai API Security focuses on understanding and protecting application interfaces. - 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.
Amazon GuardDuty
Amazon GuardDuty from Amazon Web Services focuses on cloud threat detection and suspicious activity monitoring. It is cloud threat detection service used for detecting suspicious activity across supported AWS security signals. Capabilities - AWS account threat findings: Analyzes the AWS security signals documented for this managed threat-detection service. - Cloud security posture management: Finds cloud configuration risks so teams can prioritize corrections across connected environments. - Vulnerability prioritization: Helps order remediation work using the risk context available in the platform. Use and operational context Amazon GuardDuty is relevant to security teams monitoring AWS accounts and workloads when the requirement centers on detecting suspicious activity across supported AWS security signals. 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 enabled protection plans, permissions, finding triage and the downstream response workflow. 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? Amazon GuardDuty focuses on detecting suspicious activity across supported AWS security signals. - 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.
Amazon Inspector
Amazon Inspector from Amazon Web Services focuses on cloud workload vulnerability assessment. It is cloud vulnerability assessment service used for assessing supported AWS workloads and software assets for vulnerabilities. Capabilities - EC2 workload assessment: Assesses the Amazon EC2 workloads included in the configured vulnerability assessment scope. - ECR container image assessment: Brings supported Amazon ECR image assets into the vulnerability assessment workflow. - Lambda vulnerability assessment: Addresses supported AWS Lambda assets under the scanning options documented by AWS. - Vulnerability scanning: Finds potential weaknesses that can be reviewed and prioritized for remediation. - Risk-based prioritization: Uses the available risk context to help order remediation work. - Configuration assessment: Identifies configuration issues as a separate source of security exposure. - Exposure reporting: Provides views for communicating the assessed exposure and progress of remediation work. - Cloud exposure assessment: Brings the connected cloud environments into the documented exposure assessment scope. Use and operational context Amazon Inspector is relevant to teams remediating weaknesses in their AWS estate when the requirement centers on assessing supported AWS workloads and software assets for vulnerabilities. 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 asset coverage, scanning settings, finding prioritization and ownership of workload remediation. 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? Amazon Inspector focuses on assessing supported AWS workloads and software assets for vulnerabilities. - 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.
Amazon Macie
Amazon Macie from Amazon Web Services focuses on cloud data discovery and sensitive data detection. It is sensitive-data discovery service used for assessing sensitive information stored in supported Amazon S3 data. Capabilities - Amazon S3 sensitive-data assessment: Focuses the documented sensitive-data discovery workflow on supported Amazon S3 data. - S3 data protection findings: Connects sensitive-data discovery with findings relevant to how the assessed S3 data is protected. - Sensitive data discovery: Finds protected information so teams can establish where it is stored or used. - Data access visibility: Shows who or what can access the covered data assets. - Data protection policy management: Gives teams a way to administer data protection rules across the product's supported scope. Use and operational context Amazon Macie is relevant to AWS teams overseeing the protection of S3 data when the requirement centers on assessing sensitive information stored in supported Amazon S3 data. 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 bucket scope, discovery-job configuration, data identifiers and who investigates a sensitive-data finding. 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? Amazon Macie focuses on assessing sensitive information stored in supported Amazon S3 data. - 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.
Anomali ThreatStream
Anomali ThreatStream from Anomali focuses on threat intelligence collection and enrichment. It is threat intelligence technology or service used for providing external threat context for analysis and decisions. Capabilities - Threat intelligence collection: Brings threat information into a workflow that supports analysis and security decisions. - Threat indicator enrichment: Adds context to indicators so teams can assess their relevance to an investigation. - Adversary and campaign context: Provides information about activity patterns associated with threat actors or campaigns. - Threat intelligence integrations: Connects intelligence with the supported analysis tools or security workflows. - Intelligence prioritization: Helps teams focus attention on the threat information most relevant to their requirements. Use and operational context Anomali ThreatStream is relevant to analysts investigating adversaries, indicators or emerging exposures when the requirement centers on providing external threat context for analysis and 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 Before adoption, review source relevance, freshness, integration methods and how intelligence changes a specific investigation or protection decision. 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? Anomali ThreatStream focuses on providing external threat context for analysis and 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.
App & API Protector
App & API Protector from Akamai focuses on web application and API attack protection. It is web application protection technology used for applying security rules to application requests. Capabilities - Web request filtering: Applies protection rules to requests reaching the web applications covered by the deployment. - OWASP attack coverage: Targets application attack classes referenced in the product's protection documentation. - Bot traffic controls: Adds controls for automated traffic that can create application abuse or availability problems. - API traffic protection: Brings API traffic into the application protection scope where included in the selected offering. - Behavior-based analysis: Uses behavioral context in addition to straightforward signature matching. - DDoS mitigation integration: Can be evaluated within the vendor's documented application availability and attack mitigation scope. Use and operational context App & API Protector sits in Akamai's application protection portfolio and brings application and API protection into the web-traffic workflow. Validate how rules are applied to the applications in scope and how legitimate requests are distinguished during policy tuning. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review application onboarding, rule tuning, false-positive handling and behavior under representative legitimate traffic. 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? App & API Protector focuses on applying security rules to application 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.