Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -83,6 +83,8 @@
83	83	|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
84	84	|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
85	85	|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
	86	+
	87	+A detailed description of the Dependency-Track 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,29 +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 ==
	94	+== 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.
	96	+* WYSIWYG and wiki syntax editors
	97	+* Version control and history tracking
	98	+* Inline and structured content editing
	99	+* Commenting and annotations
96	96
97		-(% class="wikigeneratedid" %)
98		-You can explore the Auditing Basics section in the Dependency‑Track documentation for deeper insights.
	101	+== Advanced Page & Document Management ==
99	99
100		-== 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
101	101
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.
	108	+== Powerful Search and Navigation ==
104	104
105		-(% class="wikigeneratedid" %)
106		-You can explore the 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
107	107
108		-== Analysis States ==
	114	+== Macros and Widgets ==
109	109
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.
	116	+* Built-in and custom macros (charts, galleries, diagrams)
	117	+* Embedding of rich media (videos, iframes, etc.)
	118	+* Markdown and LaTeX support
112	112
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.
115	115
116	116
117	117