Changes for page Dependency-Track

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Dependency Track
	1	+Dependency-Track

Content

...	...	@@ -4,13 +4,13 @@
4	4
5	5	= Introduction =
6	6
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.
	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.
8	8
9	9	[[Vendor Page>>https://dependencytrack.org/]]
10	10
11		-There are several useful resources available to get started with Dependency Track:
	11	+There are several useful resources available to get started with Dependency-Track:
12	12
13		-[[Dependency Track Documentation>>https://docs.dependencytrack.org/]]
	13	+[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
14	14
15	15	= Accessing Dependency-Track =
16	16
...	...	@@ -27,7 +27,7 @@
27	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.
28	28	)))
29	29
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.
	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.
31	31
32	32	== Via DevOps Portal ==
33	33
...	...	@@ -45,7 +45,7 @@
45	45
46	46	== Via Direct URL ==
47	47
48		-You can also access Dependency Track directly using the following link format:
	48	+You can also access Dependency-Track directly using the following link format:
49	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.
50	50
51	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.
...	...	@@ -53,17 +53,17 @@
53	53
54	54	= Projects =
55	55
56		-After creating a DevOps project in the portal, a Dependency Track project is automatically created.
	56	+After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
57	57
58		-== Dependency Track Jenkins Integration ==
	58	+== Dependency-Track Jenkins Integration ==
59	59
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.
	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.
61	61
62	62
63	63	== Collection Project ==
64	64
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.
66		-For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency Track documentation.
	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.
	66	+For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
67	67
68	68	= Users and Roles =
69	69