Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 21.8

Open Web Application Security Project (OWASP) Dependency-Check
Open Web Application Security Project (OWASP) Dependency-Check Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: Open Web Application Security Project (OWASP) Dependency-Check is a utility that attempts to detect publicly disclosed vulnerabilities contained within project dependencies. The utility includes a Command Line Interface (CLI), a Maven plugin, an Ant task, a Gradle Plugin, an SBT Plugin, and a Jenkins plugin. The core engine contains a series of analyzers that inspect the project dependencies and collects pieces of information about the dependencies (referred to as evidence within the tool). The evidence is then used to identify the Common Platform Enumeration (CPE) for the given dependency. If a CPE is identified, a listing of associated Common Vulnerabilities and Exposures (CVEs) are listed in a report. Dependency-check automatically updates itself using the National Vulnerability Database (NVD) Data Feeds hosted by the National Institute of Standards and Technology (NIST).

This technology does not contain a database.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.2
Decision Date: 02/10/2020
Introduced By: TRM Request
Vendor Name: OWASP
- The information contained on this page is accurate as of the Decision Date (02/10/2020).