Wiki source code of Dependency Track

Version 47.1 by Milad Afshar-Jahanshahi on 2025/09/03 13:45

version	line-number	content
8.1	1	[[image:logo-dependency-track.YzQAjtqS_Z2pMQkR.webp\|\|alt="Grafana Icon Logo PNG vector in SVG, PDF, AI, CDR format" data-xwiki-image-style-alignment="end" height="52" width="190"]]
6.1	2
29.1	3	{{toc/}}
28.1	4
6.1	5	= Introduction =
	6
46.1	7	Dependency Track is an open-source Software Composition Analysis (SCA) tool that helps organizations manage and secure their software supply chain. It automatically generates and maintains a Software Bill of Materials (SBOM) for projects, continuously monitoring dependencies for known vulnerabilities. In addition, it tracks license compliance of open-source components, giving teams greater visibility and control. By integrating seamlessly into DevOps and CI/CD pipelines, Dependency Track makes it easier to embed security throughout the development lifecycle.
6.1	8
9.1	9	[[Vendor Page>>https://dependencytrack.org/]]
6.1	10
43.2	11	There are several useful resources available to get started with Dependency Track:
6.1	12
46.2	13	[[Dependency Track Documentation>>https://docs.dependencytrack.org/]]
6.1	14
46.1	15	= Accessing Dependency Track =
6.1	16
44.1	17	Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it is only available to pilot customers. To get started, a few prerequisites need to be in place.
26.2	18
13.1	19	== Preconditions in DevOps portal to access Dependency-Track ==
6.1	20
44.2	21	1. A Dependency Track license must be assigned to the user
	22	1. Deptrack must be added to the tool list of the project
6.1	23
25.1	24	(% class="box warningmessage" %)
	25	(((
	26	⚠ Note
44.2	27	Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency Track project.
25.1	28	)))
	29
44.2	30	After completing the preconditions, a project in Dependency Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
6.1	31
	32	== Via DevOps Portal ==
	33
16.1	34	Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
6.1	35
15.2	36	[[image:deptrack.png\|\|alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
6.1	37
23.2	38	(% class="box warningmessage" %)
	39	(((
6.1	40	⚠ Note
45.1	41	If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again.
	42	For some reason, you may need to click more than one option in OpenID or trigger the login section ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
18.1	43	\\[[image:login1.png\|\|alt="Untitled2.png" height="250" width="600"]]
23.2	44	)))
6.1	45
	46	== Via Direct URL ==
	47
45.2	48	You can also access Dependency Track directly using the following link format:
23.1	49	[[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/projects>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance.
6.1	50
	51	If you are not already logged in to another tool in the toolchain or the DevOps portal, then you have to login using your configured SSO credentials.
	52
	53
36.2	54	= Projects =
26.1	55
45.2	56	After creating a DevOps project in the portal, a Dependency Track project is automatically created.
26.1	57
45.2	58	== Dependency Track Jenkins Integration ==
26.1	59
45.2	60	When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency Track project. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
26.1	61
45.2	62
36.2	63	== Collection Project ==
26.2	64
45.2	65	In Dependency Track, these Maven builds are organized under a Collection Project. Subprojects (for example, individual modules of a Maven project) are created as children of the DevOps portal project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
46.1	66	For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency Track documentation.
27.1	67
36.1	68	= Users and Roles =
6.1	69
46.1	70	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency Track are disabled (UI and API)
6.1	71
38.3	72	(% class="box warningmessage" %)
	73	(((
6.1	74	⚠ Note
47.1	75	Projects in the DevOps portal are mapped to the corresponding project in Dependency Track.
38.3	76	)))
6.1	77
46.1	78	* When Dependency Track is added as a tool to an existing or new project, a corresponding Dependency Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration:
6.1	79	** Role mapping: (((
38.3	80	\|=Project Role in DevOps Portal\|=Permissions in Dependency-Track
38.2	81	\|Admin\|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	82	\|Master\|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	83	\|Developer\|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	84	\|Viewer\|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
6.1	85	)))
	86
	87	= Main Features =
	88
40.4	89	== Auditing Basics ==
6.1	90
40.3	91	(% class="wikigeneratedid" %)
46.1	92	Dependency Track offers a robust auditing workflow: you can triage findings on individual projects, add comments, and record analysis decisions. The platform logs a complete audit trail for each action. Users with the VULNERABILITY_ANALYSIS permission can perform these audits, and audit histories are visible to anyone with the VIEW_VULNERABILITY permission.
6.1	93
40.5	94	(% class="wikigeneratedid" %)
46.1	95	You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency Track documentation for deeper insights.
6.1	96
40.4	97	== Impact Analysis ==
	98
40.3	99	(% class="wikigeneratedid" %)
46.1	100	Dependency Track enables organizations to assess how a vulnerability affects their environment. If a vulnerability is published in a supported datasource (e.g., NVD, GitHub Advisories, OSS Index, VulnDB), the platform dynamically identifies all affected projects. This allows you to answer: "What is affected?" and "Where am I affected?" at a glance.
6.1	101
40.5	102	(% class="wikigeneratedid" %)
46.1	103	You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency Track documentation for deeper insights.
40.5	104
40.4	105	== Analysis States ==
	106
40.3	107	(% class="wikigeneratedid" %)
46.1	108	Dependency Track tracks the status of findings through their lifecycle via "analysis states". These help teams understand whether findings are new, under review, suppressed, or resolved. You can reference the Analysis States section in the documentation for full details on available statuses and workflows.
6.1	109
40.5	110	(% class="wikigeneratedid" %)
46.1	111	You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency Track documentation for deeper insights.
6.1	112
40.5	113
6.1	114

Wiki source code of Dependency Track

DevOps-as-a-Service