Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +3,3 @@
1		-STILL UNDER CONSTRUCTION
2		-
3	3	[[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"]]
4	4
5	5	{{toc/}}
...	...	@@ -6,19 +6,17 @@
6	6
7	7	= Introduction =
8	8
9		-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, 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.
10	10
11	11	[[Vendor Page>>https://dependencytrack.org/]]
12	12
13		-There are several useful resources available to get started with Deptrack:
	11	+There are several useful resources available to get started with Dependency Track:
14	14
15	15	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
16	16
17		-[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
18		-
19	19	= Accessing Dependency-Track =
20	20
21		-Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it’s only offered in the Pilotkunden Preview. To get started, a few prerequisites need to be in place.
	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.
22	22
23	23	== Preconditions in DevOps portal to access Dependency-Track ==
24	24
...	...	@@ -94,16 +94,24 @@
94	94	(% class="wikigeneratedid" %)
95	95	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.
96	96
	93	+(% class="wikigeneratedid" %)
	94	+You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights.
97	97
98	98	== Impact Analysis ==
99	99
100	100	(% class="wikigeneratedid" %)
101		-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. docs.dependencytrack.org
	99	+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.
102	102
	101	+(% class="wikigeneratedid" %)
	102	+You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights.
	103	+
103	103	== Analysis States ==
104	104
105	105	(% class="wikigeneratedid" %)
106		-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. docs.dependencytrack.org +1
	107	+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.
107	107
	109	+(% class="wikigeneratedid" %)
	110	+You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency‑Track documentation for deeper insights.
108	108
	112	+
109	109