Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

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