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...
Mend SCA
Mend SCA from Mend.io focuses on open-source dependency risk analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. Use and operational context Mend SCA 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? Mend SCA 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.
Menlo Secure Enterprise Browser
Menlo Secure Enterprise Browser from Menlo Security focuses on browser isolation and enterprise browsing protection. It is enterprise browser security technology used for applying policy to business browsing and application access. Capabilities - Enterprise browsing policies: Applies the documented browser controls to supported work sessions and applications. - Browser data protection: Addresses the data-handling controls included in the browser offering. - Identity-aware application access: Connects browser access with the identities or policies covered by the product. - Browser isolation: Uses the isolation approach documented for protecting browsing activity. - Unmanaged device access: Addresses access from personal or unmanaged devices within the supported deployment model. - Browser activity visibility: Provides records or visibility into the browsing activity covered by the product. Use and operational context Menlo's browser offering addresses the protection and control of enterprise browsing. Review application compatibility and the isolation or data-handling functions included in the proposed service, then assess the experience of users accessing representative business applications. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review application compatibility, browser deployment, data-handling policies and the experience on managed or personal devices. 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? Menlo Secure Enterprise Browser focuses on applying policy to business browsing and application access. - 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.
MetaAccess
MetaAccess from OPSWAT focuses on device posture assessment and access controls. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Device posture assessment: Checks the documented device condition signals used by OPSWAT's access-assessment workflow. - Endpoint compliance checks: Assesses the endpoint compliance factors documented for the supported integrations. - Access policy integration: Connects the device assessment result with the supported access-policy workflow. Use and operational context MetaAccess 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: Self-managed / on-premises option documented by the vendor. 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? MetaAccess 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.
MetaDefender Core
MetaDefender Core from OPSWAT focuses on file threat scanning and content sanitization. It is file inspection and sanitization technology used for evaluating and processing files through the selected threat-inspection engines. Capabilities - Multiengine file scanning: Combines the file inspection engines documented for the selected MetaDefender configuration. - Content disarm and reconstruction: Processes supported files using the vendor's disarm-and-reconstruction method to reduce content-borne risk. - File inspection workflows: Brings file handling into the documented threat inspection workflow. - Application integration: Provides the documented mechanism for integrating file protection into an application or service. Use and operational context MetaDefender Core is relevant to teams securing incoming files or application uploads when the requirement centers on evaluating and processing files through the selected threat-inspection engines. 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 enabled engines, supported content, scanning and transformation policy and how results affect the file intake 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? MetaDefender Core focuses on evaluating and processing files through the selected threat-inspection engines. - 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.
MetaDefender Kiosk
MetaDefender Kiosk is a hardware security product from OPSWAT, focused on portable media inspection and threat prevention. Capabilities - Portable-media intake screening: Applies the documented inspection workflow to files arriving through removable media. - Content disarm and reconstruction: Processes supported files using the vendor's disarm-and-reconstruction method to reduce content-borne risk. - File policy controls: Applies configurable decisions to the files or content types processed by the product. - File inspection workflows: Brings file handling into the documented threat inspection workflow. - Application integration: Provides the documented mechanism for integrating file protection into an application or service. Use and operational context MetaDefender Kiosk is relevant to teams controlling physical file intake when the requirement centers on checking removable-media content before it enters a protected environment. 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 media support, inspection policy, treatment of detected content and records of approved file transfer. 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? MetaDefender Kiosk focuses on checking removable-media content before it enters a protected environment. - 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.
Microsoft Defender for Cloud
Microsoft Defender for Cloud from Microsoft focuses on cloud security posture and workload protection. It is cloud security technology used for assessing cloud exposure or protecting running workloads. Capabilities - Azure and multicloud posture: Brings the connected cloud environments into Microsoft's documented posture and workload assessment model. - Cloud configuration findings: Assesses the cloud security configuration scope enabled for the connected accounts. - Defender workload protection plans: Provides the workload protection functions enabled through the applicable Defender plans. - Azure and connected cloud inventory: Brings supported cloud assets into the visibility and assessment workflow. Use and operational context Microsoft Defender for Cloud is relevant to cloud and security teams working across accounts and workloads when the requirement centers on assessing cloud exposure or protecting running workloads. 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 cloud permissions required for onboarding, the assets assessed, runtime coverage and how findings reach remediation owners. 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? Microsoft Defender for Cloud focuses on assessing cloud exposure or protecting running workloads. - 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.
Microsoft Defender for Endpoint
Microsoft Defender for Endpoint from Microsoft focuses on endpoint protection and threat investigation. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Automated investigation and remediation: Connects documented investigation logic with the configured endpoint response workflow. - Endpoint detection and response: Connects endpoint alerts with investigation and response workflows rather than stopping at malware identification. - Ransomware protection: Addresses ransomware-related execution patterns or recovery controls described in the product documentation. - Malware prevention: Provides controls intended to detect or block malicious files and execution. - Policy management: Lets administrators apply protection settings to groups of managed endpoints. Use and operational context Microsoft Defender for Endpoint 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 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 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? Microsoft Defender for Endpoint 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. Microsoft ecosystem and investigation Defender for Endpoint contributes endpoint signals to the unified Microsoft Defender portal, where analysts can correlate them with other supported identity, email and cloud signals. Advanced hunting provides a query-based investigation workflow, and custom detection rules can turn suitable hunting queries into scheduled detections. APIs and partner integrations support connections to broader security operations processes. These workflows should be evaluated with the actual licenses and data sources planned for deployment. Platform and licensing considerations Supported platforms include Windows, macOS, Linux, Android and iOS, with differences in supported versions and functions. Plan 1, Plan 2 and Defender for Business have different scopes; server protection has distinct licensing considerations. Begin with a controlled onboarding pilot and verify prerequisites, permissions, response actions and the operational process for investigating alerts.
Microsoft Entra ID
Microsoft Entra ID from Microsoft focuses on identity management and access control. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Conditional-access policy: Brings user and device conditions into access decisions for the connected Microsoft identity environment. - 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. - Conditional access: Applies access rules using conditions such as the user, device or session context. - Access certification: Helps review whether existing access rights remain appropriate for each identity. - 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 Microsoft Entra ID 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? Microsoft Entra ID 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.
Microsoft Purview
Microsoft Purview from Microsoft focuses on data security and compliance management. It is data governance, security and compliance technology used for governing data use and managing information protection or compliance workflows. Capabilities - Data security and compliance portfolio: Brings the documented data-governance, security or compliance services into the organization's Microsoft data workflow. - 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. Use and operational context Microsoft Purview is relevant to teams protecting and governing data in the supported Microsoft ecosystem when the requirement centers on governing data use and managing information protection or compliance workflows. 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 services, data locations, classification policies and the licensing requirements of the functions being evaluated. 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? Microsoft Purview focuses on governing data use and managing information protection or compliance workflows. - 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.