Changes for page Dependency-Track

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • deptrack.png
  • logo-dependency-track.YzQAjtqS_Z2pMQkR.webp

Details

Page properties

Content

...	...	@@ -11,5 +11,111 @@
11	11	Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
12	12
13	13	Collection Project und Unterprojekte
	14	+\\~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~##
14	14
	16	+
	17	+
	18	+
	19	+{{toc/}}
	20	+
	21	+[[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"]]
	22	+
	23	+= =
	24	+
	25	+= =
	26	+
	27	+= Introduction =
	28	+
	29	+Dependency-Track is an open-source software composition analysis (SCA) tool. It creates and manages a software bill of materials (SBOM) for projects. The tool continuously checks dependencies for known vulnerabilities. It also tracks license compliance of open-source components. Teams gain visibility and control over their software supply chain. Helps integrate security into DevOps/CI-CD pipelines efficiently.
	30	+
	31	+[[Vendor Page>>https://dependencytrack.org/]]
	32	+
	33	+There are several useful resources available to get started with Deptrack:
	34	+
	35	+[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
	36	+
	37	+[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
	38	+
	39	+[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
	40	+
	41	+= Accessing Dependency-Track =
	42	+
	43	+== Preconditions in DevOps portal to access Dependency-Track ==
	44	+
	45	+1. A Dependency-Track license must be assigned to the user
	46	+1. Dependency-Track must be added to the tool list of the project
	47	+
	48	+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.
	49	+
	50	+== Via DevOps Portal ==
	51	+
	52	+Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
	53	+
	54	+[[image:deptrack.png||alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
	55	+
	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:Untitled2.png||height="185" width="825"]]
	59	+
	60	+== Via Direct URL ==
	61	+
	62	+You can also access Dependency-Track directly using the following link format:
	63	+[[https:~~/~~/<customer~>.devops.t-systems.net/xwiki/wiki/<pkey~>/view>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance and <pkey> is the project key in lowercase letters.
	64	+
	65	+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.
	66	+
	67	+⚠ **Note**
	68	+Access to the main wiki at [[https:~~/~~/<customer~>.devops.t-systems.net/xwiki>>https://<customer>.devops.t-systems.net/xwiki]] is forbidden due to security restrictions and therefore this page cannot be viewed.
15	15
	70	+
	71	+= Users, Projects and Roles =
	72	+
	73	+* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
	74	+
	75	+⚠ **Note**
	76	+Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
	77	+
	78	+* 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 :
	79	+** Role mapping: (((
	80	+|=Project Role in DevOps Portal|=Permissions in XWiki
	81	+|Admin|View, comment, edit, and delete pages
	82	+|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
	83	+|Developer|(% colspan="1" %)Similar to Master
	84	+|Viewer|Read-only access. Can only view content, no edits or comments allowed
	85	+
	86	+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/]]
	87	+)))
	88	+
	89	+= Main Features =
	90	+
	91	+Inside DevOps-as-a-Service, XWiki is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
	92	+
	93	+== Collaborative Content Editing ==
	94	+
	95	+* WYSIWYG and wiki syntax editors
	96	+* Version control and history tracking
	97	+* Inline and structured content editing
	98	+* Commenting and annotations
	99	+
	100	+== Advanced Page & Document Management ==
	101	+
	102	+* Hierarchical page structure (nested pages)
	103	+* Templates for creating structured documents
	104	+* Tags, categories, and metadata support
	105	+* File attachments and preview
	106	+
	107	+== Powerful Search and Navigation ==
	108	+
	109	+* Full-text search (Solr-based)
	110	+* Faceted search filters
	111	+* Page index, breadcrumbs, and navigation panels
	112	+
	113	+== Macros and Widgets ==
	114	+
	115	+* Built-in and custom macros (charts, galleries, diagrams)
	116	+* Embedding of rich media (videos, iframes, etc.)
	117	+* Markdown and LaTeX support
	118	+
	119	+
	120	+
	121	+

deptrack.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.miladafshar-jahanshahit-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+14.2 KB

Content

logo-dependency-track.YzQAjtqS_Z2pMQkR.webp

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.miladafshar-jahanshahit-systemscom

Size

...	...	@@ -1,0 +1,1 @@
	1	+7.1 KB

Content