Skip to Content

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 37.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -63,7 +63,7 @@
63 63  
64 64  == Collection Project ==
65 65  
66 -In Dependency-Track, these Maven builds are organized under a **Collection Project**. Subprojects (for example, individual modules of a Maven project) are created as children of the DevOps portal project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
66 +In Dependency-Track, these Maven builds are organized under a **Collection Project**. Subprojects (for example, individual modules of a Maven project) are created as children of the collection. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
67 67  For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
68 68  
69 69  = Users and Roles =
... ... @@ -70,19 +70,18 @@
70 70  
71 71  * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
72 72  
73 -(% class="box warningmessage" %)
74 -(((
75 75  ⚠ **Note**
76 -Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
77 -)))
74 +Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
78 78  
79 -* When Dependency-Track is added as a tool to an existing or new project, a corresponding Dependency Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration : 
76 +* When Dependency-Track is added as a tool to an existing or new project, a corresponding subwiki is automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration : 
80 80  ** Role mapping: (((
81 -|=Project Role in DevOps Portal|=Permissions in Dependency-Track
82 -|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
83 -|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
84 -|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
85 -|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
78 +|=Project Role in DevOps Portal|=Permissions in XWiki
79 +|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
80 +|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
81 +|Developer|(% colspan="1" %)Similar to Master
82 +|Viewer|Read-only access. Can only view content, no edits or comments allowed
83 +
84 +A detailed description of the XWiki 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,21 +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 ==
91 +== 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.
93 +* WYSIWYG and wiki syntax editors
94 +* Version control and history tracking
95 +* Inline and structured content editing
96 +* Commenting and annotations
96 96  
98 +== Advanced Page & Document Management ==
97 97  
98 -== Impact Analysis ==
100 +* Hierarchical page structure (nested pages)
101 +* Templates for creating structured documents
102 +* Tags, categories, and metadata support
103 +* File attachments and preview
99 99  
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
105 +== Powerful Search and Navigation ==
102 102  
103 -== Analysis States ==
107 +* Full-text search (Solr-based)
108 +* Faceted search filters
109 +* Page index, breadcrumbs, and navigation panels
104 104  
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 +== Macros and Widgets ==
107 107  
113 +* Built-in and custom macros (charts, galleries, diagrams)
114 +* Embedding of rich media (videos, iframes, etc.)
115 +* Markdown and LaTeX support
108 108  
117 +
118 +
109 109  
© 2018-2025 T-Systems International GmbH