Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 33.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 12:55
on 2025/09/03 12:55
Change comment:
There is no comment for this version
To version 52.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 14:10
on 2025/09/03 14:10
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Dependency Track1 +Dependency-Track - 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/}} ... ... @@ -6,26 +6,22 @@ 6 6 7 7 = Introduction = 8 8 9 -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 monitoringdependencies 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.7 +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 and the continuously monitors 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. 10 10 11 11 [[Vendor Page>>https://dependencytrack.org/]] 12 12 13 -There are several useful resources available to get started with Dep track:11 +There are several useful resources available to get started with Dependency-Track: 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 -[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]] 20 - 21 21 = Accessing Dependency-Track = 22 22 23 -Dependency-Track is integrated into the DO AAS toolchain, but for now it’s onlyofferedinthePilotkunden Preview. To get started, a few prerequisites need to be in place.17 +Dependency-Track is integrated into the DevOps-as-a-Service tool chain, but for now it is only available to pilot customers. To get started, a few prerequisites need to be in place. 24 24 25 25 == Preconditions in DevOps portal to access Dependency-Track == 26 26 27 -1. A Dependency-Track license must be assigned to the user 28 -1. Dep endency-Track must be added to the tool list of the project21 +1. A Dependency-Track license must be assigned to the user by a Portal Admin. 22 +1. Deptrack must be added to the tool list of the project by a Project Admin or Portal Admin. 29 29 30 30 (% class="box warningmessage" %) 31 31 ((( ... ... @@ -33,18 +33,8 @@ 33 33 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. 34 34 ))) 35 35 30 +After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service tool chain, can be accessed via the DevOps Portal or directly through the Depdency-Track URL. 36 36 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 -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. 47 - 48 48 == Via DevOps Portal == 49 49 50 50 Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile: ... ... @@ -54,8 +54,9 @@ 54 54 (% class="box warningmessage" %) 55 55 ((( 56 56 ⚠ **Note** 57 -If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again: 58 -\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]] 41 +If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions. To resolve this issue, please log out and then log in again. 42 +For some reason, you may need to click more than one time on the OpenID button or go to the login page ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session. 43 +\\[[image:login1.png||alt="Untitled2.png" data-xwiki-image-style-border="true" height="297" width="650"]] 59 59 ))) 60 60 61 61 == Via Direct URL == ... ... @@ -66,64 +66,64 @@ 66 66 If you are not already logged in to another tool in the toolchain or the DevOps portal, then you have to login using your configured SSO credentials. 67 67 68 68 54 += Projects = 69 69 70 - ==Dependency-TrackJenkinsInteraction==56 +After creating a DevOps project in the portal, a Dependency-Track project is automatically created. 71 71 72 - NursdcPipeline() wirdunterstützt,nurmaven(bisher),alles automatisch58 +== Dependency-Track Jenkins Integration == 73 73 60 +When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track project. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects. 74 74 75 -== Collection Project und Unterprojekte == 76 76 77 - TODO63 +== Collection Project == 78 78 79 -= Users, Projects and Roles = 65 +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 +For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation. 80 80 68 += Users and Roles = 69 + 81 81 * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API) 82 82 72 +(% class="box warningmessage" %) 73 +((( 83 83 ⚠ **Note** 84 -Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track. 75 +Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track. 76 +))) 85 85 86 -* 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:78 +* 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: 87 87 ** Role mapping: ((( 88 -|=Project Role in DevOps Portal|=Permissions in XWiki 89 -|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS' 90 -|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content 91 -|Developer|(% colspan="1" %)Similar to Master 92 -|Viewer|Read-only access. Can only view content, no edits or comments allowed 93 - 94 -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/]] 80 +|=Project Role in DevOps Portal|=Permissions in Dependency-Track 81 +|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 82 +|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 83 +|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 84 +|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY 95 95 ))) 96 96 97 97 = Main Features = 98 98 99 - InsideDevOps-as-a-Service, deptrack is mainlyusedfor writing specificationsand documentations. See below for a list of the main features of XWiki.89 +== Auditing Basics == 100 100 101 -== Collaborative Content Editing == 91 +(% class="wikigeneratedid" %) 92 +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. 102 102 103 -* WYSIWYG and wiki syntax editors 104 -* Version control and history tracking 105 -* Inline and structured content editing 106 -* Commenting and annotations 94 +(% class="wikigeneratedid" %) 95 +You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights. 107 107 108 -== Advanced Page & DocumentManagement==97 +== Impact Analysis == 109 109 110 -* Hierarchical page structure (nested pages) 111 -* Templates for creating structured documents 112 -* Tags, categories, and metadata support 113 -* File attachments and preview 99 +(% class="wikigeneratedid" %) 100 +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. 114 114 115 -== Powerful Search and Navigation == 102 +(% class="wikigeneratedid" %) 103 +You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights. 116 116 117 -* Full-text search (Solr-based) 118 -* Faceted search filters 119 -* Page index, breadcrumbs, and navigation panels 105 +== Analysis States == 120 120 121 -== Macros and Widgets == 107 +(% class="wikigeneratedid" %) 108 +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. 122 122 123 -* Built-in and custom macros (charts, galleries, diagrams) 124 -* Embedding of rich media (videos, iframes, etc.) 125 -* Markdown and LaTeX support 110 +(% class="wikigeneratedid" %) 111 +You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights. 126 126 127 127 128 - 129 129
- XWiki.XWikiComments[0]
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.miladafshar-jahanshahit-systemscom - Comment
-
... ... @@ -1,13 +1,0 @@ 1 -[[https:~~/~~/docs.dependencytrack.org/>>url:https://docs.dependencytrack.org/]] 2 - 3 -Optionales Tool: aktivieren als Project Admin für das Projekt, zuweisen von Lizenzen als Portal Admin an die entsprechenden User 4 - 5 -Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat ~-~-> Done 6 - 7 -Dashboard -> DepTrack Login Seite ~-~-> DOne 8 - 9 -Pilotkunden Preview ist 10 - 11 -Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch 12 - 13 -Collection Project und Unterprojekte - Date
-
... ... @@ -1,1 +1,0 @@ 1 -2025-09-03 08:45:10.589