Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31

From version 40.4
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:22
Change comment: There is no comment for this version
To version 40.5
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -94,16 +94,24 @@
94 94  (% class="wikigeneratedid" %)
95 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 96  
97 +(% class="wikigeneratedid" %)
98 +You can explore the Auditing Basics section in the Dependency‑Track documentation for deeper insights.
97 97  
98 98  == Impact Analysis ==
99 99  
100 100  (% class="wikigeneratedid" %)
101 -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
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 102  
105 +(% class="wikigeneratedid" %)
106 +You can explore the Impact Analysis section in the Dependency‑Track documentation for deeper insights.
107 +
103 103  == Analysis States ==
104 104  
105 105  (% class="wikigeneratedid" %)
106 -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
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.
107 107  
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.
108 108  
116 +
109 109