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...
G DATA Managed Endpoint Security
G DATA Managed Endpoint Security from G DATA focuses on managed business endpoint security. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Managed endpoint administration: Adds the provider-led administration role described in G DATA's managed endpoint offering. - Endpoint security configuration support: Includes the configuration tasks specified in the managed-service documentation. - Exploit prevention: Adds protection against techniques that abuse software weaknesses during an attack. - Malware prevention: Provides controls intended to detect or block malicious files and execution. Use and operational context G DATA Managed Endpoint Security 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? G DATA Managed Endpoint Security 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.
GitHub Advanced Security
GitHub Advanced Security from GitHub focuses on repository security analysis and vulnerability management. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Repository security workflows: Places the documented security checks within the repository and development workflows supported by GitHub. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Dependency vulnerability analysis: Brings third-party software components into the vulnerability review process. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context GitHub Advanced Security 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? GitHub Advanced Security 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.
GitHub Code Security
GitHub Code Security from GitHub focuses on code vulnerability and dependency security analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - CodeQL code analysis: Uses the documented CodeQL approach to identify security issues in supported repository code. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Dependency vulnerability analysis: Brings third-party software components into the vulnerability review process. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context GitHub Code Security 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? GitHub Code Security 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.
GitHub Secret Protection
GitHub Secret Protection from GitHub focuses on repository secret detection and push protection. It is application secrets management technology used for controlling how software obtains and uses credentials. Capabilities - Secret push protection: Adds checks intended to stop supported secrets from being introduced through repository pushes. - Application secret storage: Provides a controlled storage and access workflow for application credentials and other secrets. - Secret rotation: Supports changing secrets according to the credential lifecycle controls described by the vendor. - Developer and pipeline integration: Connects secrets access with the development or delivery tools supported by the product. Use and operational context GitHub Secret Protection is relevant to development and infrastructure teams handling nonhuman access when the requirement centers on controlling how software obtains and uses credentials. 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 secret retrieval, access policy, rotation behavior and the consequences of a service or network interruption. 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? GitHub Secret Protection focuses on controlling how software obtains and uses credentials. - 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.
GitLab Ultimate
GitLab Ultimate from GitLab focuses on development security testing and compliance workflows. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Security and compliance pipeline checks: Combines the documented application-security checks with GitLab's delivery and governance workflow. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Dynamic application security testing: Tests a running application to find exposed security weaknesses. - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Dependency vulnerability analysis: Brings third-party software components into the vulnerability review process. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Infrastructure configuration analysis: Checks infrastructure definitions alongside application code where this capability is included. Use and operational context GitLab Ultimate 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 Deployment: Cloud service / SaaS; Self-managed / on-premises option documented by the vendor. 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? GitLab Ultimate 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.
Glasswall Embedded Engine
Glasswall Embedded Engine from Glasswall focuses on software development kit for integrating file content disarm and reconstruction. It is file reconstruction software development kit used for integrating content disarm and reconstruction into another application. Capabilities - Embedded file reconstruction SDK: Provides a software development kit for integrating the documented file-reconstruction controls into another application. - 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 Glasswall Embedded Engine is relevant to developers adding file protection to an intake or processing workflow when the requirement centers on integrating content disarm and reconstruction into another application. 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 file types, SDK interfaces, policy behavior and preservation of legitimate document content. 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? Glasswall Embedded Engine focuses on integrating content disarm and reconstruction into another application. - 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.
Glasswall Genesis
Glasswall Genesis from Glasswall focuses on file content disarm and reconstruction engine with policy controls. It is file reconstruction engine used for processing supported files under granular content security policies. Capabilities - Policy-controlled file reconstruction: Implements file reconstruction using the granular content policies described by Glasswall. - 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 Glasswall Genesis is relevant to teams operating controlled document processing when the requirement centers on processing supported files under granular content security policies. 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 content, policy settings, processing performance and the fidelity of reconstructed files. 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? Glasswall Genesis focuses on processing supported files under granular content security policies. - 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.
Glasswall Halo
Glasswall Halo from Glasswall focuses on server-based file content disarm and reconstruction. It is server-based file reconstruction technology used for processing files through a centrally deployed content disarm and reconstruction service. Capabilities - Server-based file reconstruction: Provides the documented server deployment for processing files through content disarm and reconstruction. - 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 Glasswall Halo is relevant to teams securing shared file intake and processing when the requirement centers on processing files through a centrally deployed content disarm and reconstruction service. 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 deployment topology, file formats, integration interfaces and validation using representative business documents. 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? Glasswall Halo focuses on processing files through a centrally deployed content disarm and reconstruction service. - 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.
Glasswall Meteor
Glasswall Meteor from Glasswall focuses on desktop file content disarm and reconstruction. It is desktop file reconstruction technology used for applying content disarm and reconstruction to files in a desktop workflow. Capabilities - Desktop file reconstruction: Applies the documented desktop workflow to files handled on local or connected storage. - 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 Glasswall Meteor is relevant to teams handling local or connected files that require content protection when the requirement centers on applying content disarm and reconstruction to files in a desktop workflow. 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 desktop deployment, file location coverage, processing policy and the usability of reconstructed documents. 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? Glasswall Meteor focuses on applying content disarm and reconstruction to files in a desktop workflow. - 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.