Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 38.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:09
on 2025/09/03 13:09
Change comment:
There is no comment for this version
To version 40.4
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:22
on 2025/09/03 13:22
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -70,18 +70,19 @@ 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 +((( 73 73 ⚠ **Note** 74 -Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track. 76 +Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track. 77 +))) 75 75 76 -* When Dependency-Track is added as a tool to an existing or new project, a corresponding subwikiis automatically created. Users assigned to the project in the DevOps Portal are then added to thesubwiki with the roles defined in the configuration :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 : 77 77 ** Role mapping: ((( 78 -|=Project Role in DevOps Portal|=Permissions in 81 +|=Project Role in DevOps Portal|=Permissions in Dependency-Track 79 79 |Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 80 80 |Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 81 81 |Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 82 82 |Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY 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/]] 85 85 ))) 86 86 87 87 = Main Features = ... ... @@ -88,32 +88,21 @@ 88 88 89 89 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. 90 90 91 -== Collaborative Content Editing ==92 +== Auditing Basics == 92 92 93 -* WYSIWYG and wiki syntax editors 94 -* Version control and history tracking 95 -* Inline and structured content editing 96 -* Commenting and annotations 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. 97 97 98 -== Advanced Page & Document Management == 99 99 100 -* Hierarchical page structure (nested pages) 101 -* Templates for creating structured documents 102 -* Tags, categories, and metadata support 103 -* File attachments and preview 98 +== Impact Analysis == 104 104 105 -== Powerful Search and Navigation == 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 106 106 107 -* Full-text search (Solr-based) 108 -* Faceted search filters 109 -* Page index, breadcrumbs, and navigation panels 103 +== Analysis States == 110 110 111 -== Macros and Widgets == 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 112 112 113 -* Built-in and custom macros (charts, galleries, diagrams) 114 -* Embedding of rich media (videos, iframes, etc.) 115 -* Markdown and LaTeX support 116 116 117 - 118 - 119 119