Wiki source code of Dependency Track

Version 53.5 by Boris Folgmann on 2025/09/03 14:17

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
49.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 and the continuously monitors 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
49.1	11	There are several useful resources available to get started with Dependency-Track:
6.1	12
50.1	13	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
6.1	14
48.1	15	= Accessing Dependency-Track =
6.1	16
51.1	17	Dependency-Track is integrated into the DevOps-as-a-Service tool chain, 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
51.1	21	1. A Dependency-Track license must be assigned to the user by a Portal Admin.
	22	1. Deptrack must be added to the tool list of the project by a Project Admin or Portal Admin.
6.1	23
25.1	24	(% class="box warningmessage" %)
	25	(((
	26	⚠ Note
48.1	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
52.1	30	After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service tool chain, can be accessed via the DevOps Portal or directly through the Depdency-Track 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
52.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. To resolve this issue, please log out and then log in again.
	42	For some reason, you may need to click more than one time on the OpenID button or go to the login page ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
	43	\\[[image:login1.png\|\|alt="Untitled2.png" data-xwiki-image-style-border="true" height="297" width="650"]]
23.2	44	)))
6.1	45
	46	== Via Direct URL ==
	47
49.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
52.2	51	If you are not already logged in to another tool in the tool chain or the DevOps portal, then you have to log in using your configured SSO credentials.
6.1	52
	53
36.2	54	= Projects =
26.1	55
53.5	56	After creating a DevOps project in the portal, a Dependency-Track project is automatically created. The type of the new project is a Collection Project. Sub projects (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.
53.4	57	For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
	58
	59	== Integration with Jenkins ==
	60
53.3	61	The [[Jenkins Shared Library>>url:https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/Jenkins/Jenkins%20Shared%20Library/]] will automatically create SBOM (Software Bill of Materials) files for maven projects and upload them to Dependency-Track.
26.1	62
53.2	63	[[image:1756907509490-678.png]]
45.2	64
53.4	65	A new Dependency-Track sub project is automatically created on the fly.
53.2	66
53.4	67	Currently, this option is only available for Maven projects.
53.2	68
26.2	69
53.4	70	== ==
27.1	71
36.1	72	= Users and Roles =
6.1	73
51.1	74	* 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	75
38.3	76	(% class="box warningmessage" %)
	77	(((
6.1	78	⚠ Note
51.1	79	Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
38.3	80	)))
6.1	81
51.1	82	* 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	83	** Role mapping: (((
38.3	84	\|=Project Role in DevOps Portal\|=Permissions in Dependency-Track
38.2	85	\|Admin\|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	86	\|Master\|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	87	\|Developer\|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	88	\|Viewer\|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
6.1	89	)))
	90
	91	= Main Features =
	92
40.4	93	== Auditing Basics ==
6.1	94
40.3	95	(% class="wikigeneratedid" %)
51.1	96	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	97
40.5	98	(% class="wikigeneratedid" %)
51.1	99	You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights.
6.1	100
40.4	101	== Impact Analysis ==
	102
40.3	103	(% class="wikigeneratedid" %)
51.1	104	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	105
40.5	106	(% class="wikigeneratedid" %)
51.1	107	You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights.
40.5	108
40.4	109	== Analysis States ==
	110
40.3	111	(% class="wikigeneratedid" %)
51.1	112	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	113
40.5	114	(% class="wikigeneratedid" %)
51.1	115	You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights.
6.1	116
40.5	117
6.1	118

Wiki source code of Dependency Track

DevOps-as-a-Service