Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -89,29 +89,20 @@
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 ==
	92	+(% class="wikigeneratedid" id="HCollaborativeContentEditing" %)
	93	+Auditing Basics
93	93
94	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	+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. docs.dependencytrack.org +1
96	96
97	97	(% class="wikigeneratedid" %)
98		-You can explore the Auditing Basics section in the Dependency‑Track documentation for deeper insights.
	99	+Impact Analysis
99	99
100		-== Impact Analysis ==
101		-
102	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.
	102	+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
104	104
105	105	(% class="wikigeneratedid" %)
106		-You can explore the Impact Analysis section in the Dependency‑Track documentation for deeper insights.
	105	+3. Analysis States 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
107	107
108		-== Analysis States ==
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.
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		-
116		-
117	117