Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -14,12 +14,12 @@
14	14
15	15	= Accessing Dependency-Track =
16	16
17		-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.
	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.
18	18
19	19	== Preconditions in DevOps portal to access Dependency-Track ==
20	20
21		-1. A Dependency-Track license must be assigned to the user
22		-1. Deptrack must be added to the tool list of the project
	21	+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.
23	23
24	24	(% class="box warningmessage" %)
25	25	(((
...	...	@@ -67,15 +67,15 @@
67	67
68	68	= Users and Roles =
69	69
70		-* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency Track are disabled (UI and API)
	70	+* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
71	71
72	72	(% class="box warningmessage" %)
73	73	(((
74	74	⚠ **Note**
75		-Projects in the DevOps portal are mapped to the corresponding project in Dependency Track.
	75	+Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
76	76	)))
77	77
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:
	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:
79	79	** Role mapping: (((
80	80	|=Project Role in DevOps Portal|=Permissions in Dependency-Track
81	81	|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
...	...	@@ -89,26 +89,26 @@
89	89	== Auditing Basics ==
90	90
91	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.
	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.
93	93
94	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.
	95	+You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights.
96	96
97	97	== Impact Analysis ==
98	98
99	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.
	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.
101	101
102	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.
	103	+You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights.
104	104
105	105	== Analysis States ==
106	106
107	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.
	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.
109	109
110	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.
	111	+You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights.
112	112
113	113
114	114