Skip to content

Commit 7ed9cfa

Browse files
authored
Merge pull request #8 from redhat-gpte-devopsautomation/main
Update
2 parents 6295556 + 40f37ea commit 7ed9cfa

File tree

8 files changed

+9
-2
lines changed

8 files changed

+9
-2
lines changed
-16.1 KB
Loading
-25.3 KB
Loading
10.6 KB
Loading
59.2 KB
Loading
-128 KB
Binary file not shown.
165 KB
Loading
154 KB
Loading

content/modules/ROOT/pages/chapter03.adoc

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -203,9 +203,9 @@ image::63_ACS_Image_Check_Task.png[]
203203

204204
image::64_Image_Check_Result.png[]
205205

206-
=== Task 6: Export SBOM
206+
=== Task 6: Upload SBOM to Repository
207207

208-
image::65_Scan_Export_SBOM_Task.png[]
208+
image::65_Upload_SBOM_Repo_Task.png[]
209209

210210

211211
* You then demonstrate how to access the generated *SBOM* by clicking the link that's readily available in your pipeline view.
@@ -216,6 +216,13 @@ image::57_SBOM_Link.png[]
216216

217217
image::66_SBOM.png[]
218218

219+
=== Task 7: Upload SBOM to TPA
220+
221+
image::65_Upload_SBOM_TPA_Task.png[]
222+
223+
224+
* In this step, the SBOM is uploaded to Trusted Profile Analyzer. We do this to turn the raw SBOM into actionable information. For example, TPA can identify dependencies in your image that are targets of known Common Vulnerabilities and Exploits (CVEs). These CVE's can be viewed on the Trusted Profile Analyzer console for the specific SBOM uploaded.
225+
219226
=== Demonstrating the Secure Deploy Process
220227

221228
* Addressing the QA engineer, you begin, “Now, I'm going to show you how to validate that an image is signed before deploying it for testing.”

0 commit comments

Comments
 (0)