Application security
Static (SAST), Dynamic (DAST), and Software Composition Analysis (SCA) tooling identifying vulnerabilities in proprietary code and third-party open-source dependencies.
Key Technical Considerations Before Procuring
Verify integration into developer CI/CD pull-request workflows and low false-positive rates to ensure engineering adoption.
Documented Solutions in this Category
Showing 36 published solutions with verified evidence
Snyk Developer Security Platform
Developer security suite comprising Snyk Open Source (SCA), Snyk Code (SAST), Snyk Container, and Snyk IaC.
Black Duck SCA
Black Duck SCA from Black Duck focuses on open-source vulnerability and license 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. - 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. - License risk analysis: Helps teams review licensing obligations associated with third-party components. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Black Duck SCA focuses on the third-party components included in software. Evaluate dependency identification, vulnerability and licensing findings together, then establish which findings block a release and which require a documented remediation or exception decision. Deployment and evaluation Deployment: Cloud service / SaaS. 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? Black Duck 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.
Coverity
Coverity from Black Duck focuses on static source code defect and vulnerability analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Source-code defect analysis: Addresses code-quality defects as well as the security weaknesses identified by static analysis. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Coverity 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? Coverity 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.
Polaris
Polaris from Black Duck focuses on cloud application security testing orchestration. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context Polaris is Black Duck's platform entry for application security testing. Review which analysis services are enabled, how findings from those services are presented and how development teams integrate the testing workflow into a representative application delivery process. Deployment and evaluation Deployment: Cloud service / SaaS. 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? Polaris 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.
Checkmarx One
Checkmarx One from Checkmarx focuses on application security testing and vulnerability prioritization. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context Checkmarx One is a platform-level application security entry. Review the testing services and modules enabled in the proposed package, how their findings are combined and how development teams receive actionable results in their existing delivery workflow. 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? Checkmarx One 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.
Checkmarx SAST
Checkmarx SAST from Checkmarx focuses on source code security testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - 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. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Checkmarx SAST focuses on static analysis of application code. A trial should use representative repositories and supported languages, with developers reviewing the code location, security explanation and remediation work associated with an identified weakness. 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? Checkmarx SAST 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.
Checkmarx SCA
Checkmarx SCA from Checkmarx focuses on dependency security and software composition 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. - 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. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Checkmarx 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? Checkmarx 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.
Contrast Assess
Contrast Assess from Contrast Security focuses on interactive application security testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. - Interactive application testing: Uses information from application execution to assess security behavior and vulnerabilities. Use and operational context Contrast Assess 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? Contrast Assess 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.
Contrast Protect
Contrast Protect from Contrast Security focuses on application runtime attack protection. It is application security technology used for finding or addressing weaknesses in software. Capabilities - In-application runtime protection: Applies the documented protection controls within the running application's execution context. - Application attack detection: Identifies the application attacks covered by the runtime protection model. - Runtime instrumentation: Uses the application's documented instrumentation approach to obtain runtime security context. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Runtime application protection: Protects the running application using the runtime controls documented for the product. Use and operational context Contrast Protect 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? Contrast Protect 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.
Contrast SCA
Contrast SCA from Contrast Security focuses on dependency vulnerability 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. - 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. - License risk analysis: Helps teams review licensing obligations associated with third-party components. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Contrast 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? Contrast 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.
Endor Labs
Endor Labs from Endor Labs focuses on software dependency risk analysis and application security. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Endor Labs 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? Endor Labs 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 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.
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.
Acunetix
Acunetix from Invicti focuses on web application vulnerability scanning. 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. Use and operational context Acunetix 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. 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? Acunetix 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.
Invicti
Invicti from Invicti focuses on dynamic application security testing and vulnerability validation. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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. - License risk analysis: Helps teams review licensing obligations associated with third-party components. Use and operational context Invicti 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? Invicti 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.
JFrog Advanced Security
JFrog Advanced Security from JFrog focuses on software supply chain analysis and contextual security testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Contextual artifact analysis: Adds the contextual assessment functions documented alongside JFrog's artifact scanning workflow. - 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. Use and operational context JFrog 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? JFrog 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.
JFrog Xray
JFrog Xray from JFrog focuses on artifact vulnerability and license risk scanning. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Artifact-focused component scanning: Assesses supported software artifacts rather than treating application security only as source-code analysis. - 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. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. Use and operational context JFrog Xray 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? JFrog Xray 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.
Mend SAST
Mend SAST from Mend.io focuses on source code vulnerability detection. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Developer workflow integration: Places security findings into the development processes documented by the vendor. Use and operational context Mend SAST 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 SAST 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.
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.
Oligo Cloud Application Detection and Response
Oligo Cloud Application Detection and Response from Oligo Security focuses on application runtime threat detection and exploit investigation. 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. - 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. Use and operational context Oligo Cloud Application Detection and Response 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? Oligo Cloud Application Detection and Response 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.
Burp Suite DAST
Burp Suite DAST from PortSwigger focuses on automated dynamic application security testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Scheduled application scanning: Organizes automated testing of running applications using the deployment and scan model documented by PortSwigger. - 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. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Burp Suite DAST 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: 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? Burp Suite DAST 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.
Web Application Scanning
Web Application Scanning from Qualys focuses on web application vulnerability discovery. 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. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. Use and operational context Web Application Scanning 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. 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? Web Application Scanning 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.
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.
Spectra Assure
Spectra Assure from ReversingLabs focuses on software package risk analysis and supply chain protection. It is software supply chain security technology used for assessing the trust and risk of software artifacts. Capabilities - Software package inspection: Examines the software artifacts within the product's documented analysis scope. - Malicious component detection: Looks for malicious content in the supported software supply chain assets. - Release risk assessment: Helps teams review the security state of software before or alongside release decisions. Use and operational context Spectra Assure is relevant to teams reviewing dependencies, build outputs or releases when the requirement centers on assessing the trust and risk of software artifacts. 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 artifact coverage, policy thresholds, evidence behind findings and the point at which results affect release decisions. 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? Spectra Assure focuses on assessing the trust and risk of software artifacts. - 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.
Semgrep Code
Semgrep Code from Semgrep focuses on source code vulnerability detection. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Rule-based source analysis: Uses the documented code-analysis rules to identify relevant security patterns in source code. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - 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. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Semgrep Code 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. 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? Semgrep Code 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.
Semgrep Supply Chain
Semgrep Supply Chain from Semgrep focuses on dependency vulnerability analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Reachable dependency assessment: Adds the documented reachability context to open-source dependency findings. - 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. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. Use and operational context Semgrep Supply Chain 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. 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? Semgrep Supply Chain 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.
Snyk Code
Snyk Code from Snyk focuses on source code security analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Developer-oriented static analysis: Places source-code vulnerability assessment within the documented developer workflow. - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - 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. Use and operational context Snyk Code 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? Snyk Code 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.
Snyk Open Source
Snyk Open Source from Snyk focuses on dependency vulnerability detection. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Dependency remediation advice: Helps developers evaluate the vendor's documented remediation options for vulnerable dependencies. - 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. Use and operational context Snyk Open Source 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: 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? Snyk Open Source 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.
SonarQube Cloud
SonarQube Cloud from Sonar focuses on cloud-managed code quality and vulnerability analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Cloud-managed code analysis: Provides the documented hosted analysis workflow for connected development projects. - 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. - Infrastructure configuration analysis: Checks infrastructure definitions alongside application code where this capability is included. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context SonarQube Cloud 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? SonarQube Cloud 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.
SonarQube Server
SonarQube Server from Sonar focuses on source code quality and security analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Self-managed code analysis: Provides the documented server-managed environment for administering code analysis. - 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. - Infrastructure configuration analysis: Checks infrastructure definitions alongside application code where this capability is included. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context SonarQube Server 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? SonarQube Server 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.
StackHawk
StackHawk from StackHawk focuses on application and API security testing in development workflows. It is application security technology used for finding or addressing weaknesses in software. Capabilities - 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 StackHawk 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? StackHawk 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.
Veracode Dynamic Analysis
Veracode Dynamic Analysis from Veracode focuses on runtime 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. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Veracode Dynamic Analysis evaluates a running application. Review how the scan reaches the intended application functions, including authentication and test restrictions, and how application owners verify and remediate a finding discovered through the tested request paths. 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? Veracode Dynamic Analysis 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.
Veracode Software Composition Analysis
Veracode Software Composition Analysis from Veracode focuses on open-source dependency vulnerability 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. - 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. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Veracode Software Composition Analysis 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? Veracode Software Composition Analysis 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.
Veracode Static Analysis
Veracode Static Analysis from Veracode focuses on source code vulnerability identification. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - 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. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Veracode Static Analysis evaluates the code or artifacts supported by its analysis workflow. Review representative application inputs, how a finding is linked to the relevant code location and the process developers use to assess and correct that weakness. 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? Veracode Static Analysis 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.
Wiz Code
Wiz Code from Wiz focuses on code-to-cloud security analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Code-to-cloud context: Links documented development findings with their context in the cloud environment. - 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 Wiz Code 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. 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? Wiz Code 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.