Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -1,3 +1,5 @@
	1	+STILL UNDER CONSTRUCTION
	2	+
1	1	[[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"]]
2	2
3	3	{{toc/}}
...	...	@@ -12,6 +12,8 @@
12	12
13	13	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
14	14
	17	+[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
	18	+
15	15	= Accessing Dependency-Track =
16	16
17	17	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.
...	...	@@ -72,7 +72,7 @@
72	72	Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
73	73	)))
74	74
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 :
	79	+* When Dependency-Track is added as a tool to an existing or new project, a corresponding pris 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	76	** Role mapping: (((
77	77	|=Project Role in DevOps Portal|=Permissions in Dependency-Track
78	78	|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
...	...	@@ -79,6 +79,8 @@
79	79	|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
80	80	|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
81	81	|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
	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/]]
82	82	)))
83	83
84	84	= Main Features =
...	...	@@ -85,29 +85,32 @@
85	85
86	86	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.
87	87
88		-== Auditing Basics ==
	94	+== Collaborative Content Editing ==
89	89
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.
	96	+* WYSIWYG and wiki syntax editors
	97	+* Version control and history tracking
	98	+* Inline and structured content editing
	99	+* Commenting and annotations
92	92
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.
	101	+== Advanced Page & Document Management ==
95	95
96		-== Impact Analysis ==
	103	+* Hierarchical page structure (nested pages)
	104	+* Templates for creating structured documents
	105	+* Tags, categories, and metadata support
	106	+* File attachments and preview
97	97
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.
	108	+== Powerful Search and Navigation ==
100	100
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.
	110	+* Full-text search (Solr-based)
	111	+* Faceted search filters
	112	+* Page index, breadcrumbs, and navigation panels
103	103
104		-== Analysis States ==
	114	+== Macros and Widgets ==
105	105
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.
	116	+* Built-in and custom macros (charts, galleries, diagrams)
	117	+* Embedding of rich media (videos, iframes, etc.)
	118	+* Markdown and LaTeX support
108	108
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.
111	111
112	112
113	113