Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -16,10 +16,14 @@
16	16
17	17	[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
18	18
	19	+[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
	20	+
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.
22	22
	24	+Dependency-Track is integrated into the DOSSS toolchain, but for now it’s only offered in the Pilotkunden Preview. To get started, a few prerequisites need to be in place.
	25	+
	26	+
23	23	== Preconditions in DevOps portal to access Dependency-Track ==
24	24
25	25	1. A Dependency-Track license must be assigned to the user
...	...	@@ -28,9 +28,18 @@
28	28	(% class="box warningmessage" %)
29	29	(((
30	30	⚠ **Note**
31		-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	+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
32	32	)))
33	33
	38	+
	39	+
	40	+
	41	+
	42	+
	43	+
	44	+
	45	+
	46	+
34	34	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.
35	35
36	36	== Via DevOps Portal ==
...	...	@@ -54,35 +54,32 @@
54	54	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.
55	55
56	56
57		-= Projects =
58	58
59		-== Dependency-Track Jenkins Integration ==
	71	+== Dependency-Track Jenkins Interaction ==
60	60
61		-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.
	73	+Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
62	62
63	63
64		-== Collection Project ==
	76	+== Collection Project und Unterprojekte ==
65	65
66		-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.
67		-For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
	78	+TODO
68	68
69		-= Users and Roles =
	80	+= Users, Projects and Roles =
70	70
71	71	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
72	72
73		-(% class="box warningmessage" %)
74		-(((
75	75	⚠ **Note**
76		-Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
77		-)))
	85	+Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
78	78
79		-* 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 :
	87	+* 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 :
80	80	** Role mapping: (((
81		-|=Project Role in DevOps Portal|=Permissions in Dependency-Track
82		-|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
83		-|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
84		-|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
85		-|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
	89	+|=Project Role in DevOps Portal|=Permissions in XWiki
	90	+|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
	91	+|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
	92	+|Developer|(% colspan="1" %)Similar to Master
	93	+|Viewer|Read-only access. Can only view content, no edits or comments allowed
	94	+
	95	+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/]]
86	86	)))
87	87
88	88	= Main Features =
...	...	@@ -89,21 +89,32 @@
89	89
90	90	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.
91	91
92		-== Auditing Basics ==
	102	+== Collaborative Content Editing ==
93	93
94		-(% class="wikigeneratedid" %)
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.
	104	+* WYSIWYG and wiki syntax editors
	105	+* Version control and history tracking
	106	+* Inline and structured content editing
	107	+* Commenting and annotations
96	96
	109	+== Advanced Page & Document Management ==
97	97
98		-== Impact Analysis ==
	111	+* Hierarchical page structure (nested pages)
	112	+* Templates for creating structured documents
	113	+* Tags, categories, and metadata support
	114	+* File attachments and preview
99	99
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
	116	+== Powerful Search and Navigation ==
102	102
103		-== Analysis States ==
	118	+* Full-text search (Solr-based)
	119	+* Faceted search filters
	120	+* Page index, breadcrumbs, and navigation panels
104	104
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
	122	+== Macros and Widgets ==
107	107
	124	+* Built-in and custom macros (charts, galleries, diagrams)
	125	+* Embedding of rich media (videos, iframes, etc.)
	126	+* Markdown and LaTeX support
108	108
	128	+
	129	+
109	109