Changes for page Dependency-Track

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

From 36.2 to 36.1 From 45.1 to 44.2

From version 44.2

edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:33

Change comment: There is no comment for this version

To version 36.2

edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:04

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,3 +1,5 @@
++STILL UNDER CONSTRUCTION
++
  [[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"]]
  {{toc/}}
@@ -4,30 +4,34 @@
  = Introduction =
--Dependency Track is an open-source Software Composition Analysis (SCA) tool that helps organizations manage and secure their software supply chain. It automatically generates and maintains a Software Bill of Materials (SBOM) for projects, continuously monitoring dependencies for known vulnerabilities. In addition, it tracks license compliance of open-source components, giving teams greater visibility and control. By integrating seamlessly into DevOps and CI/CD pipelines, Dependency-Track makes it easier to embed security throughout the development lifecycle.
++Dependency-Track is an open-source Software Composition Analysis (SCA) tool that helps organizations manage and secure their software supply chain. It automatically generates and maintains a Software Bill of Materials (SBOM) for projects, continuously monitoring dependencies for known vulnerabilities. In addition, it tracks license compliance of open-source components, giving teams greater visibility and control. By integrating seamlessly into DevOps and CI/CD pipelines, Dependency-Track makes it easier to embed security throughout the development lifecycle.
  [[Vendor Page>>https://dependencytrack.org/]]
--There are several useful resources available to get started with Dependency Track:
++There are several useful resources available to get started with Deptrack:
  [[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
++[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
++
++[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
++
  = Accessing Dependency-Track =
--Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it is only available to pilot customers. To get started, a few prerequisites need to be in place.
++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.
  == Preconditions in DevOps portal to access Dependency-Track ==
--1. A Dependency Track license must be assigned to the user
--1. Deptrack must be added to the tool list of the project
++1. A Dependency-Track license must be assigned to the user
++1. Dependency-Track must be added to the tool list of the project
  (% class="box warningmessage" %)
  (((
  ⚠ **Note**
--Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency Track project.
++Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency-Track project.
  )))
--After completing the preconditions, a project in Dependency Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
++After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
  == Via DevOps Portal ==
@@ -59,7 +59,7 @@
  == Collection Project ==
--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.
++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.
  For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
  = Users and Roles =
@@ -66,19 +66,18 @@
  * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
--(% class="box warningmessage" %)
--(((
  ⚠ **Note**
--Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
--)))
++Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
--* 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 :
++* 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 :
  ** Role mapping: (((
--|=Project Role in DevOps Portal|=Permissions in Dependency-Track
--|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
--|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
--|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
--|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
++|=Project Role in DevOps Portal|=Permissions in XWiki
++|Admin|   POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
++|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
++|Developer|(% colspan="1" %)Similar to Master
++|Viewer|Read-only access. Can only view content, no edits or comments allowed
++
++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/]]
  )))
  = Main Features =
@@ -85,29 +85,32 @@
  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.
--== Auditing Basics ==
++== Collaborative Content Editing ==
--(% class="wikigeneratedid" %)
--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.
++* WYSIWYG and wiki syntax editors
++* Version control and history tracking
++* Inline and structured content editing
++* Commenting and annotations
--(% class="wikigeneratedid" %)
--You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights.
++== Advanced Page & Document Management ==
--== Impact Analysis ==
++* Hierarchical page structure (nested pages)
++* Templates for creating structured documents
++* Tags, categories, and metadata support
++* File attachments and preview
--(% class="wikigeneratedid" %)
--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.
++== Powerful Search and Navigation ==
--(% class="wikigeneratedid" %)
--You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights.
++* Full-text search (Solr-based)
++* Faceted search filters
++* Page index, breadcrumbs, and navigation panels
--== Analysis States ==
++== Macros and Widgets ==
--(% class="wikigeneratedid" %)
--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.
++* Built-in and custom macros (charts, galleries, diagrams)
++* Embedding of rich media (videos, iframes, etc.)
++* Markdown and LaTeX support
--(% class="wikigeneratedid" %)
--You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency‑Track documentation for deeper insights.