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.
Endpoint Privilege Management
Endpoint Privilege Management from BeyondTrust focuses on endpoint least privilege and application control. It is privileged access management technology used for controlling elevated credentials and privileged sessions. Capabilities - Privileged credential vaulting: Stores privileged credentials under centrally administered access controls. - Just-in-time access: Limits privileged access to the period or approval conditions defined for a task. - Least-privilege enforcement: Restricts routine access so users and applications do not retain unnecessary elevated permissions. - Application privilege controls: Applies privilege decisions to application execution rather than granting unrestricted administrative rights. - Remote session brokering: Provides controlled access paths for administrators or external support providers. Use and operational context Endpoint Privilege Management is relevant to administrators governing access to sensitive systems when the requirement centers on controlling elevated credentials and privileged sessions. 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: Windows, macOS, Linux. Supported versions and feature coverage depend on the vendor support matrix.. Check version requirements and feature differences before rollout. Before adoption, review credential onboarding, access approvals, session controls and the operational impact of least-privilege policies. 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? Endpoint Privilege Management focuses on controlling elevated credentials and privileged sessions. - 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.
Endpoint Privilege Manager
Endpoint Privilege Manager from CyberArk focuses on endpoint least privilege and application control. It is privileged access management technology used for controlling elevated credentials and privileged sessions. Capabilities - Just-in-time access: Limits privileged access to the period or approval conditions defined for a task. - Least-privilege enforcement: Restricts routine access so users and applications do not retain unnecessary elevated permissions. Use and operational context Endpoint Privilege Manager is relevant to administrators governing access to sensitive systems when the requirement centers on controlling elevated credentials and privileged sessions. 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: Windows, Linux. Supported versions and feature coverage depend on the vendor support matrix.. Check version requirements and feature differences before rollout. Before adoption, review credential onboarding, access approvals, session controls and the operational impact of least-privilege policies. 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? Endpoint Privilege Manager focuses on controlling elevated credentials and privileged sessions. - 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.
Entrust Identity as a Service
Entrust Identity as a Service from Entrust focuses on cloud authentication and access security. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Adaptive authentication: Uses contextual signals to change the authentication requirements for a login attempt. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context Entrust Identity as a Service is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. 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 identity providers, application connectors, access-policy design and the account lifecycle 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? Entrust Identity as a Service focuses on authentication, access policy or identity lifecycle administration. - 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.
Entrust nShield HSM
Entrust nShield HSM is a hardware security product from Entrust, focused on hardware-backed cryptographic key protection. Capabilities - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Code signing workflows: Supports signing software or artifacts using the product's documented key access and policy model. - Hardware-backed key storage: Uses the documented hardware protection boundary for sensitive cryptographic material. Use and operational context Entrust nShield 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? Entrust nShield 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.
Exabeam Fusion
Exabeam Fusion from Exabeam focuses on security analytics and incident 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. - 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 Exabeam Fusion is evaluated within Exabeam's security analytics portfolio. Review how relevant event and behavior information reaches an investigation, how incidents are organized and which platform capabilities are included in the proposed product package. Deployment and evaluation Deployment: Cloud service / SaaS; 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? Exabeam Fusion 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.
Exabeam New-Scale SIEM
Exabeam New-Scale SIEM from Exabeam focuses on security log analytics and behavior-based 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. - Event correlation: Connects related observations so analysts can investigate a potential incident in context. - Behavior analytics: Examines patterns associated with users or entities to help identify suspicious deviations. - Detection rules and analytics: Supports defining or maintaining the logic used to identify suspicious activity. - 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 Exabeam New-Scale 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 Deployment: Cloud service / SaaS; 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? Exabeam New-Scale 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.
Expel Managed Detection and Response
24/7 MDR that integrates via APIs into existing security tools across Kubernetes, AWS, Azure, GCP, SaaS apps, and endpoints with fast automated containment.
Expel Managed Detection and Response
Expel Managed Detection and Response is a managed security service offered by Expel. Its documented scope centers on managed threat monitoring and investigation. 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 Expel's managed service is assessed around the supported security tools and data it will monitor. Identify the integration permissions, evidence available to the analysts and the process by which a reviewed finding becomes an agreed 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? Expel 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.
F5 BIG-IP Advanced WAF
F5 BIG-IP Advanced WAF from F5 focuses on web application firewall 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. - 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. - DDoS mitigation integration: Can be evaluated within the vendor's documented application availability and attack mitigation scope. - Virtual patching: Uses protective rules to reduce exposure while application remediation is being arranged. Use and operational context F5 BIG-IP Advanced WAF is relevant to application owners and security teams protecting web services when the requirement centers on applying security rules to application requests. 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 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? F5 BIG-IP Advanced WAF 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.