├── .gitignore
├── 404.html
├── Gemfile
├── _config.yml
├── _data
└── ow_attributions.json
├── assets
└── images
│ ├── KPMG.svg
│ └── risk-based-security.png
├── index.md
├── info.md
├── leaders.md
├── tab_executive-order-14028.md
├── tab_features.md
├── tab_installation.md
├── tab_integrations.md
├── tab_news.md
└── tab_supporters.md
/.gitignore:
--------------------------------------------------------------------------------
1 | __pycache__
2 | env
3 | .vscode
4 | _site/
5 |
--------------------------------------------------------------------------------
/404.html:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: 404 - Not Found
4 | layout: col-generic
5 |
6 | ---
7 |
8 |
9 |
10 |
WHOA THAT PAGE CANNOT BE FOUND
11 |
Try the SEARCH function in the main navigation to find something. If you are looking for chapter information, please see Chapters for the correct chapter. For information about OWASP projects see Projects . For common attacks, vulnerabilities, or information about other community-led contributions see Contributed Content .
12 |
13 |
14 |
If all else fails you can search our historical site .
15 |
16 |
--------------------------------------------------------------------------------
/Gemfile:
--------------------------------------------------------------------------------
1 | source 'https://rubygems.org'
2 | group :jekyll_plugins do
3 | gem "github-pages"
4 | end
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | remote_theme: "owasp/www--site-theme@main"
2 | plugins:
3 | - jekyll-include-cache-0.2.0
4 | code_user: DependencyTrack
5 | code_repo: dependency-track
6 |
--------------------------------------------------------------------------------
/_data/ow_attributions.json:
--------------------------------------------------------------------------------
1 | ["Nedap NV"]
--------------------------------------------------------------------------------
/assets/images/KPMG.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
12 |
14 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/assets/images/risk-based-security.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OWASP/www-project-dependency-track/78dc146444653d456155b8642248c390926200e8/assets/images/risk-based-security.png
--------------------------------------------------------------------------------
/index.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | layout: col-sidebar
4 | title: OWASP Dependency-Track
5 | site_side: true
6 | tags: dependency-track dtrack sca scrm sbom bom component-analysis supply-chain cpe purl license vulnerability impact
7 | level: 4
8 | type: tool
9 | pitch: Intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain.
10 |
11 | ---
12 |
13 | For more details about Dependency-Track see the projects website at [dependencytrack.org](https://dependencytrack.org/)
14 |
15 | Dependency-Track is an intelligent [Component Analysis](https://owasp.org/www-community/Component_Analysis) platform that allows organizations to
16 | identify and reduce risk in the software supply chain. Dependency-Track takes a unique
17 | and highly beneficial approach by leveraging the capabilities of [Software Bill of Materials](https://owasp.org/www-community/Component_Analysis#software-bill-of-materials-sbom) (SBOM). This approach
18 | provides capabilities that traditional Software Composition Analysis (SCA) solutions cannot achieve.
19 |
20 |
21 |
22 | VIDEO
24 |
25 |
26 |
27 |
28 | Dependency-Track monitors component usage across all versions of every application in its portfolio in order to
29 | proactively identify risk across an organization. The platform has an API-first design and is ideal for use in
30 | CI/CD environments.
31 |
32 |
33 | 
34 |
--------------------------------------------------------------------------------
/info.md:
--------------------------------------------------------------------------------
1 | ### Project Information
2 |
3 | *
4 | Flagship Project
5 |
6 | #### Classification
7 |
8 | * Tool
9 |
10 | #### Audience
11 |
12 | * Builder
13 | * Defender
14 |
15 | ### External Resources
16 |
17 | * [Documentation](https://docs.dependencytrack.org/)
18 | * [GitHub](https://github.com/DependencyTrack)
19 | * [Slack](https://dependencytrack.org/slack) - [invite](https://dependencytrack.org/slack/invite)
20 | * [Twitter](https://twitter.com/dependencytrack)
21 | * [Website](https://dependencytrack.org/)
22 | * [YouTube](https://www.youtube.com/channel/UC8xdttysl3gNAQYvk1J9Efg)
23 |
24 | ### Licensing
25 |
26 | [Apache 2 License](https://www.apache.org/licenses/LICENSE-2.0)
27 |
--------------------------------------------------------------------------------
/leaders.md:
--------------------------------------------------------------------------------
1 | ### Leaders
2 | * [Steve Springett](mailto:steve.springett@owasp.org)
3 | * [Niklas Düster](mailto:niklas.duester@owasp.org)
4 |
--------------------------------------------------------------------------------
/tab_executive-order-14028.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: Executive-Order-14028
4 | displaytext: Executive Order 14028
5 | layout: null
6 | order: 6
7 | tab: true
8 | tags: dependency-track dtrack
9 |
10 | ---
11 |
12 | ## U.S. Executive Order 14028
13 |
14 | Since its inception in 2013, OWASP Dependency-Track has been at the forefront of analyzing bill of materials for cybersecurity
15 | risk identification and reduction. Dependency-Track allows organizations and governments to operationalize SBOM in
16 | conformance with [U.S. Executive Order 14028](https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/).
17 |
18 | * Supports the OWASP CycloneDX BOM format specifically defined in the [NTIA Minimum Elements For a Software Bill of Materials(SBOM)](https://www.ntia.gov/files/ntia/publications/sbom_minimum_elements_report.pdf)
19 | * Consumes and analyzes SBOMs for known security, operational, and license risk
20 | * Ideal for use in [procurement](https://docs.dependencytrack.org/usage/procurement/) and [continuous integration and delivery](https://docs.dependencytrack.org/usage/cicd/) environments
21 | * Supports the OWASP CycloneDX VEX format exceeding the [Vulnerability Exploitability Exchange requirements defined by CISA](https://www.cisa.gov/sites/default/files/publications/VEX_Use_Cases_Document_508c.pdf)
22 |
23 | ### For software consumers
24 |
25 | * Tracks all systems and applications that have SBOMs
26 | * Upload SBOMs through the user interface or via automation
27 | * Components defined in SBOMs will be analyzed for known vulnerabilities using multiple sources of vulnerability intelligence, including the [NVD](https://nvd.nist.gov/)
28 | * Displays all identified vulnerabilities and vulnerable components for every SBOM analyzed
29 | * Upload CycloneDX VEX obtained from suppliers to gain insight into the vulnerable components that pose risk, and the ones that don't
30 | * Quickly identify all systems and applications that have a specific component or are affected by a specific vulnerability
31 | * Helps to prioritize mitigation by incorporating support for the [Exploit Prediction Scoring System (EPSS)](https://www.first.org/epss/)
32 | * Evaluate the portfolio of systems and applications against user-configurable security, operational, and license policies
33 |
34 | ### For software producers
35 |
36 | * Create and consume CycloneDX SBOMs in development pipelines
37 | * SBOMs will be analyzed for known security, operational, and license risk
38 | * Evaluates the portfolio of applications against user-configurable security, operational, and license policies
39 | * Inspect security findings and make audit decisions about the relevance and exploitability of each vulnerability
40 | * CycloneDX BOMs can be dynamically generated from current inventory for any application
41 | * CycloneDX VEX is dynamically generated from audit decisions for each application
42 | * An API-first design allows software producers to extract SBOMs for released products, produce VEX whenever updated audit decisions are made, and make data available to internal systems responsible for SBOM and VEX distribution.
43 |
44 | ### Other considerations
45 |
46 | * Both CycloneDX and Dependency-Track are full-stack solutions supporting software, hardware, and services. The CycloneDX standard and use with Dependency-Track is not limited to SBOM use cases.
47 | * Software consumers may optionally audit security findings from vendor SBOMs. If consumers discover discrepancies in vendor supplied VEX, consumers can share their own auto-generated VEX with suppliers, completing a bi-directional exchange of vulnerability and exploitability information.
48 |
--------------------------------------------------------------------------------
/tab_features.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: Features
4 | layout: null
5 | order: 1
6 | tab: true
7 | tags: dependency-track dtrack
8 |
9 | ---
10 |
11 | ## Features
12 |
13 | * Consumes and produces [CycloneDX] Software Bill of Materials (SBOM)
14 | * Consumes and produces CycloneDX Vulnerability Exploitability Exchange (VEX)
15 | * Full-stack component support for:
16 | * Applications
17 | * Libraries
18 | * Frameworks
19 | * Operating systems
20 | * Containers
21 | * Firmware
22 | * Files
23 | * Hardware
24 | * Services
25 | * Tracks component usage across every application in an organizations portfolio
26 | * Quickly identify what is affected, and where
27 | * Identifies multiple forms of risk including
28 | * Components with known vulnerabilities
29 | * Out-of-date components
30 | * Modified components
31 | * License risk
32 | * More coming soon...
33 | * Integrates with multiple sources of vulnerability intelligence including:
34 | * [National Vulnerability Database] (NVD)
35 | * [GitHub Advisories]
36 | * [Sonatype OSS Index]
37 | * [VulnDB] from [Risk Based Security]
38 | * More coming soon.
39 | * Helps to prioritize mitigation by incorporating support for the [Exploit Prediction Scoring System (EPSS)]
40 | * Maintain a private vulnerability database of vulnerability components
41 | * Robust policy engine with support for global and per-project policies
42 | * Security risk and compliance
43 | * License risk and compliance
44 | * Operational risk and compliance
45 | * Ecosystem agnostic with built-in repository support for:
46 | * Cargo (Rust)
47 | * Composer (PHP)
48 | * Gems (Ruby)
49 | * Hex (Erlang/Elixir)
50 | * Maven (Java)
51 | * NPM (Javascript)
52 | * NuGet (.NET)
53 | * Pypi (Python)
54 | * More coming soon.
55 | * Identifies APIs and external service components including:
56 | * Service provider
57 | * Endpoint URIs
58 | * Data classification
59 | * Directional flow of data
60 | * Trust boundary traversal
61 | * Authentication requirements
62 | * Includes a comprehensive auditing workflow for triaging results
63 | * Configurable notifications supporting Slack, Microsoft Teams, WebEx, Webhooks, and Email
64 | * Supports standardized SPDX license ID’s and tracks license use by component
65 | * Easy to read metrics for components, projects, and portfolio
66 | * Native support for Kenna Security, Fortify SSC, ThreadFix, and DefectDojo
67 | * API-first design facilitates easy integration with other systems
68 | * API documentation available in OpenAPI format
69 | * OAuth 2.0 + OpenID Connect (OIDC) support for single sign-on (authN/authZ)
70 | * Supports internally managed users, Active Directory/LDAP, and API Keys
71 | * Simple to install and configure. Get up and running in just a few minutes
72 |
73 | [National Vulnerability Database]: https://nvd.nist.gov
74 | [GitHub Advisories]: https://www.github.com/advisories
75 | [Sonatype OSS Index]: https://ossindex.sonatype.org
76 | [VulnDB]: https://vulndb.cyberriskanalytics.com
77 | [Risk Based Security]: https://www.riskbasedsecurity.com
78 | [Supply Chain Component Analysis]: https://www.owasp.org/index.php/Component_Analysis
79 | [Software Bill-of-Materials]: https://www.owasp.org/index.php/Component_Analysis#Software_Bill-of-Materials_.28SBOM.29
80 | [CycloneDX]: https://cyclonedx.org
81 | [Exploit Prediction Scoring System (EPSS)]: https://www.first.org/epss/
82 |
--------------------------------------------------------------------------------
/tab_installation.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: Installation
4 | displaytext: Installation
5 | layout: null
6 | order: 3
7 | tab: true
8 | tags: dependency-track dtrack
9 |
10 | ---
11 |
12 | ## Installation
13 |
14 | Dependency-Track is distributed as Docker containers.
15 |
16 | ### Docker Compose
17 |
18 | ```bash
19 | curl -LO https://dependencytrack.org/docker-compose.yml
20 | docker-compose up -d
21 | ```
22 |
23 | ### Docker Swarm
24 |
25 | ```bash
26 | curl -LO https://dependencytrack.org/docker-compose.yml
27 | docker swarm init
28 | docker stack deploy -c docker-compose.yml dtrack
29 | ```
30 |
--------------------------------------------------------------------------------
/tab_integrations.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: Integrations
4 | layout: null
5 | order: 2
6 | tab: true
7 | tags: dependency-track dtrack
8 |
9 | ---
10 |
11 | ## Integrations
12 |
13 | 
14 |
--------------------------------------------------------------------------------
/tab_news.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: News
4 | layout: null
5 | order: 4
6 | tab: true
7 | tags: dependency-track dtrack
8 |
9 | ---
10 |
11 | ## News
12 |
13 | * 2022/05/18 [v4.5.0](https://docs.dependencytrack.org/2022/05/18/v4.5.0/) Released
14 | * 2022/02/18 [v4.4.1](https://docs.dependencytrack.org/2022/02/18/v4.4.1/) Released
15 | * 2022/02/17 [v4.4.0](https://docs.dependencytrack.org/2022/02/17/v4.4.0/) Released
16 | * 2021/09/20 [v4.3.6](https://docs.dependencytrack.org/2021/09/20/v4.3.6/) Released
17 | * 2021/09/20 [v4.3.5](https://docs.dependencytrack.org/2021/09/20/v4.3.5/) Released
18 | * 2021/08/31 [v4.3.4](https://docs.dependencytrack.org/2021/08/31/v4.3.4/) Released
19 | * 2021/08/20 [v4.3.3](https://docs.dependencytrack.org/2021/08/20/v4.3.3/) Released
20 | * 2021/08/07 [v4.3.2](https://docs.dependencytrack.org/2021/08/07/v4.3.2/) Released
21 | * 2021/08/03 [v4.3.1](https://docs.dependencytrack.org/2021/08/03/v4.3.1/) Released
22 | * 2021/08/02 [v4.3.0](https://docs.dependencytrack.org/2021/08/02/v4.3.0/) Released
23 | * 2021/05/07 [v4.2.2](https://docs.dependencytrack.org/2021/05/07/v4.2.2/) Released
24 | * 2021/03/20 [v4.2.1](https://docs.dependencytrack.org/2021/03/20/v4.2.1/) Released
25 | * 2021/03/17 [v4.2.0](https://docs.dependencytrack.org/2021/03/17/v4.2.0/) Released
26 | * 2021/02/09 [v4.1.0](https://docs.dependencytrack.org/2021/02/09/v4.1.0/) Released
27 | * 2021/01/12 [v4.0.1](https://docs.dependencytrack.org/2021/01/12/v4.0.1/) Released
28 | * 2021/01/03 [v4.0.0](https://docs.dependencytrack.org/2021/01/03/v4.0.0/) Released
29 | * 2020/03/22 [v3.8.0](https://docs.dependencytrack.org/2020/03/22/v3.8.0/) Released
30 | * 2020/01/07 [v3.7.1](https://docs.dependencytrack.org/2020/01/07/v3.7.1/) Released
31 | * 2019/12/16 [v3.7.0](https://docs.dependencytrack.org/2019/12/16/v3.7.0/) Released
32 | * 2019/10/01 [v3.6.1](https://docs.dependencytrack.org/2019/10/01/v3.6.1/) Released
33 | * 2019/09/28 [v3.6.0](https://docs.dependencytrack.org/2019/09/28/v3.6.0/) Released
34 | * 2019/07/17 [v3.5.1](https://docs.dependencytrack.org/2019/07/17/v3.5.1/) Released
35 | * 2019/06/07 [v3.5.0](https://docs.dependencytrack.org/2019/06/07/v3.5.0/) Released
36 | * 2019/04/16 [v3.4.1](https://docs.dependencytrack.org/2019/04/16/v3.4.1/) Released
37 | * 2018/12/22 [v3.4.0](https://docs.dependencytrack.org/2018/12/22/v3.4.0/) Released
38 | * 2018/11/13 [v3.3.1](https://docs.dependencytrack.org/2018/11/13/v3.3.1/) Released
39 | * 2018/10/25 [v3.3.0](https://docs.dependencytrack.org/2018/10/25/v3.3.0/) Released
40 | * 2018/10/02 [v3.2.2](https://docs.dependencytrack.org/2018/10/02/v3.2.2/) Released
41 | * 2018/09/21 [v3.2.1](https://docs.dependencytrack.org/2018/09/21/v3.2.1/) Released
42 | * 2018/09/06 [v3.2.0](https://docs.dependencytrack.org/2018/09/06/v3.2.0/) Released
43 | * 2018/06/19 [v3.1.0](https://docs.dependencytrack.org/2018/06/19/v3.1.0/) Released
44 | * 2018/05/02 [v3.0.4](https://docs.dependencytrack.org/2018/05/02/v3.0.4/) Released
45 | * 2018/04/13 [v3.0.3](https://docs.dependencytrack.org/2018/04/13/v3.0.3/) Released
46 | * 2018/03/30 [v3.0.2](https://docs.dependencytrack.org/2018/03/30/v3.0.2/) Released
47 | * 2018/03/29 [v3.0.1](https://docs.dependencytrack.org/2018/03/29/v3.0.1/) Released
48 | * 2018/03/27 [v3.0.0](https://docs.dependencytrack.org/2018/03/27/v3.0.0/) Released
49 | * 2017/10/08 [v3.0 Updates to community](https://groups.google.com/forum/#!topic/dependency-track/0PUJI5rNgzI)
50 | * 2017/06/16 [Presentation at OWASP Summit 2017](https://www.youtube.com/watch?v=88YAlzuDH04&t=50s)
51 |
--------------------------------------------------------------------------------
/tab_supporters.md:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | title: Supporters
4 | displaytext: Our Supporters
5 | layout: null
6 | order: 5
7 | tab: true
8 | tags: dependency-track dtrack
9 |
10 | ---
11 |
12 | ## Supporters
13 |
14 | Dependency-Track is developed by a worldwide team of volunteers.
15 |
16 | But we have also been helped by many organizations, either financially or by encouraging their employees to work on Dependency-Track:
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
--------------------------------------------------------------------------------