Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 40.5
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:23
on 2025/09/03 13:23
Change comment:
There is no comment for this version
To version 41.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:25
on 2025/09/03 13:25
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -95,7 +95,7 @@ 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 97 (% class="wikigeneratedid" %) 98 -You can explore the Auditing Basics section in the Dependency‑Track documentation for deeper insights. 98 +You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights. 99 99 100 100 == Impact Analysis == 101 101 ... ... @@ -103,7 +103,7 @@ 103 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. 104 104 105 105 (% class="wikigeneratedid" %) 106 -You can explore the Impact Analysis section in the Dependency‑Track documentation for deeper insights. 106 +You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights. 107 107 108 108 == Analysis States == 109 109