Changes for page Dependency-Track

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

From version 40.3
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:21
Change comment: There is no comment for this version
To version 43.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +3,3 @@
1 -STILL UNDER CONSTRUCTION
2 -
3 3  [[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"]]
4 4  
5 5  {{toc/}}
... ... @@ -14,8 +14,6 @@
14 14  
15 15  [[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
16 16  
17 -[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
18 -
19 19  = Accessing Dependency-Track =
20 20  
21 21  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.
... ... @@ -89,20 +89,29 @@
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 -(% class="wikigeneratedid" id="HCollaborativeContentEditing" %)
93 -Auditing Basics
88 +== Auditing Basics ==
94 94  
95 95  (% class="wikigeneratedid" %)
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
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.
97 97  
98 98  (% class="wikigeneratedid" %)
99 -Impact Analysis
94 +You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights.
100 100  
96 +== Impact Analysis ==
97 +
101 101  (% class="wikigeneratedid" %)
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
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.
103 103  
104 104  (% class="wikigeneratedid" %)
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
102 +You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights.
106 106  
104 +== Analysis States ==
107 107  
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.
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 +
112 +
108 108