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,21 +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		-[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
20		-
21	21	= Accessing Dependency-Track =
22	22
23		-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.
24	24
25	25	== Preconditions in DevOps portal to access Dependency-Track ==
26	26
...	...	@@ -56,7 +56,7 @@
56	56	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.
57	57
58	58
59		-= Projects =
	53	+= Projects =
60	60
61	61	== Dependency-Track Jenkins Integration ==
62	62
...	...	@@ -63,26 +63,28 @@
63	63	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.
64	64
65	65
66		-== Collection Project und Unterprojekte ==
	60	+== Collection Project ==
67	67
68		-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 collection. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
	62	+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.
	63	+For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
69	69
70	70	= Users and Roles =
71	71
72	72	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
73	73
	69	+(% class="box warningmessage" %)
	70	+(((
74	74	⚠ **Note**
75		-Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
	72	+Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
	73	+)))
76	76
77		-* 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 :
	75	+* 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 :
78	78	** Role mapping: (((
79		-|=Project Role in DevOps Portal|=Permissions in XWiki
80		-|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
81		-|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
82		-|Developer|(% colspan="1" %)Similar to Master
83		-|Viewer|Read-only access. Can only view content, no edits or comments allowed
84		-
85		-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/]]
	77	+|=Project Role in DevOps Portal|=Permissions in Dependency-Track
	78	+|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	79	+|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	80	+|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	81	+|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
86	86	)))
87	87
88	88	= Main Features =
...	...	@@ -89,32 +89,29 @@
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		-== Collaborative Content Editing ==
	88	+== Auditing Basics ==
93	93
94		-* WYSIWYG and wiki syntax editors
95		-* Version control and history tracking
96		-* Inline and structured content editing
97		-* Commenting and annotations
	90	+(% class="wikigeneratedid" %)
	91	+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.
98	98
99		-== Advanced Page & Document Management ==
	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.
100	100
101		-* Hierarchical page structure (nested pages)
102		-* Templates for creating structured documents
103		-* Tags, categories, and metadata support
104		-* File attachments and preview
	96	+== Impact Analysis ==
105	105
106		-== Powerful Search and Navigation ==
	98	+(% class="wikigeneratedid" %)
	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.
107	107
108		-* Full-text search (Solr-based)
109		-* Faceted search filters
110		-* Page index, breadcrumbs, and navigation panels
	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.
111	111
112		-== Macros and Widgets ==
	104	+== Analysis States ==
113	113
114		-* Built-in and custom macros (charts, galleries, diagrams)
115		-* Embedding of rich media (videos, iframes, etc.)
116		-* Markdown and LaTeX support
	106	+(% class="wikigeneratedid" %)
	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.
117	117
	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.
118	118
119	119
120	120