Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -1,45 +3,34 @@
1		-{{toc/}}
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
	3	+{{toc/}}
	4	+
5	5	= Introduction =
6	6
7		-Dependency-Track is an open-source software composition analysis (SCA) tool. It creates and manages a software bill of materials (SBOM) for projects. The tool continuously checks dependencies for known vulnerabilities. It also tracks license compliance of open-source components. Teams gain visibility and control over their software supply chain. Helps integrate security into DevOps/CI-CD pipelines efficiently.
	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.
8	8
9	9	[[Vendor Page>>https://dependencytrack.org/]]
10	10
11		-There are several useful resources available to get started with Deptrack:
	11	+There are several useful resources available to get started with Dependency Track:
12	12
13	13	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
14	14
15		-[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
16		-
17		-[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
18		-
19	19	= Accessing Dependency-Track =
20	20
21		-(% class="box warningmessage" %)
22		-(((
23		-Pilotkunden Preview ist
24		-)))
	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.
25	25
26	26	== Preconditions in DevOps portal to access Dependency-Track ==
27	27
28		-1. A Dependency-Track license must be assigned to the user
29		-1. Dependency-Track must be added to the tool list of the project
	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
30	30
31	31	(% class="box warningmessage" %)
32	32	(((
33	33	⚠ **Note**
34		-Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat
	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.
35	35	)))
36	36
	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.
37	37
38		-
39		-
40		-
41		-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.
42		-
43	43	== Via DevOps Portal ==
44	44
45	45	Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
...	...	@@ -49,7 +49,8 @@
49	49	(% class="box warningmessage" %)
50	50	(((
51	51	⚠ **Note**
52		-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:
	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.
53	53	\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
54	54	)))
55	55
...	...	@@ -61,30 +61,35 @@
61	61	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.
62	62
63	63
	54	+= Projects =
64	64
65		-== Dependency-Track Jenkins Interaction ==
	56	+== Dependency-Track Jenkins Integration ==
66	66
67		-Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
	58	+When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
68	68
69	69
70		-== Collection Project und Unterprojekte ==
	61	+== Collection Project ==
71	71
72		-= Users, Projects and Roles =
	63	+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.
	64	+For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
73	73
	66	+= Users and Roles =
	67	+
74	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)
75	75
	70	+(% class="box warningmessage" %)
	71	+(((
76	76	⚠ **Note**
77		-Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
	73	+Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
	74	+)))
78	78
79		-* When Dependency-Track is added as a tool to an existing or new project, a corresponding subwiki is automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration :
	76	+* 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 :
80	80	** Role mapping: (((
81		-|=Project Role in DevOps Portal|=Permissions in XWiki
82		-|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
83		-|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
84		-|Developer|(% colspan="1" %)Similar to Master
85		-|Viewer|Read-only access. Can only view content, no edits or comments allowed
86		-
87		-A detailed description of the XWiki role model can be found [[here>>https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Access%20Rights/Permission%20types/]]
	78	+|=Project Role in DevOps Portal|=Permissions in Dependency-Track
	79	+|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	80	+|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	81	+|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	82	+|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
88	88	)))
89	89
90	90	= Main Features =
...	...	@@ -91,32 +91,29 @@
91	91
92	92	Inside DevOps-as-a-Service, deptrack is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
93	93
94		-== Collaborative Content Editing ==
	89	+== Auditing Basics ==
95	95
96		-* WYSIWYG and wiki syntax editors
97		-* Version control and history tracking
98		-* Inline and structured content editing
99		-* Commenting and annotations
	91	+(% class="wikigeneratedid" %)
	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.
100	100
101		-== Advanced Page & Document Management ==
	94	+(% class="wikigeneratedid" %)
	95	+You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights.
102	102
103		-* Hierarchical page structure (nested pages)
104		-* Templates for creating structured documents
105		-* Tags, categories, and metadata support
106		-* File attachments and preview
	97	+== Impact Analysis ==
107	107
108		-== Powerful Search and Navigation ==
	99	+(% class="wikigeneratedid" %)
	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.
109	109
110		-* Full-text search (Solr-based)
111		-* Faceted search filters
112		-* Page index, breadcrumbs, and navigation panels
	102	+(% class="wikigeneratedid" %)
	103	+You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights.
113	113
114		-== Macros and Widgets ==
	105	+== Analysis States ==
115	115
116		-* Built-in and custom macros (charts, galleries, diagrams)
117		-* Embedding of rich media (videos, iframes, etc.)
118		-* Markdown and LaTeX support
	107	+(% class="wikigeneratedid" %)
	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.
119	119
	110	+(% class="wikigeneratedid" %)
	111	+You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency‑Track documentation for deeper insights.
120	120
121	121
122	122