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...
Imperva API Security
Imperva API Security from Imperva focuses on API discovery and risk assessment. 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. - 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. - Shadow API visibility: Finds undocumented API endpoints that can otherwise escape routine security review. Use and operational context Imperva API Security is relevant to security teams responsible for externally or internally exposed APIs when the requirement centers on understanding and protecting application interfaces. 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: Self-managed / on-premises option documented by the vendor. 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? Imperva 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.
Imperva DDoS Protection
Imperva DDoS Protection from Imperva focuses on network and application attack mitigation. It is DDoS mitigation technology or service used for protecting availability during malicious traffic floods. Capabilities - DDoS attack detection: Identifies traffic associated with distributed denial-of-service activity. - Traffic scrubbing: Uses the documented filtering infrastructure to separate attack traffic from traffic that should be served. - Network-layer protection: Addresses the network-layer attack scope stated by the vendor. - Attack visibility and reporting: Provides information for assessing observed attack traffic and mitigation activity. - Mitigation orchestration: Supports applying the mitigation approach documented for the deployment. Use and operational context Imperva DDoS Protection is relevant to organizations safeguarding network or application availability when the requirement centers on protecting availability during malicious traffic floods. 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 traffic routing, attack coverage, mitigation activation and communication arrangements during an attack. 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? Imperva DDoS Protection focuses on protecting availability during malicious traffic floods. - 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.
Imperva Data Security
Imperva Data Security from Imperva focuses on database monitoring and data risk protection. It is data security technology used for understanding sensitive information and controlling its exposure. Capabilities - Sensitive data discovery: Finds protected information so teams can establish where it is stored or used. - Data classification: Organizes data using the classification methods described by the product. - Data security posture assessment: Assesses sensitive-data exposure and the protection state of the connected environment. - Data protection policy management: Gives teams a way to administer data protection rules across the product's supported scope. Use and operational context Imperva Data Security is relevant to teams responsible for protecting business data when the requirement centers on understanding sensitive information and controlling its exposure. 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 connected repositories, classification accuracy, access findings and the handling of approved data movement. 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? Imperva Data Security focuses on understanding sensitive information and controlling its exposure. - 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.
Imperva Web Application Firewall
Imperva Web Application Firewall from Imperva focuses on web application request filtering and 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 Imperva's WAF entry addresses protection of web request paths. Assess the application's traffic pattern and deployment architecture, then evaluate rule configuration, false-positive investigation and the policy outcome for requests that resemble known application attacks. 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? Imperva Web Application Firewall 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.
Incident Response
Incident Response is a professional security engagement offered by NCC Group. The service focuses on incident investigation and containment assistance. 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. - 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 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? 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.
Incident Response
Incident Response is a professional security engagement offered by Orange Cyberdefense. The service focuses on breach 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 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? 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.
InsightAppSec
InsightAppSec from Rapid7 focuses on dynamic web application vulnerability testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Dynamic application security testing: Tests a running application to find exposed security weaknesses. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context InsightAppSec 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? InsightAppSec 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.
InsightConnect
InsightConnect from Rapid7 focuses on security workflow automation and integration. 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. - Alert enrichment: Adds relevant context to alerts before an analyst or automated workflow makes a decision. Use and operational context InsightConnect 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? InsightConnect 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.
InsightIDR
InsightIDR from Rapid7 focuses on security detection and incident investigation. It is security analytics technology used for collecting and analyzing security-relevant events. Capabilities - Security log investigation: Brings supported security data into Rapid7's incident investigation workflow. - User and entity behavior analytics: Adds the documented user or entity context to detection and investigation. - Detection and response workflows: Organizes the supported detection results and follow-up actions around incidents. Use and operational context InsightIDR 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? InsightIDR 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.