Begin working on exercise 5.
This commit is contained in:
@ -5,7 +5,7 @@ date: '2024-10-19'
|
||||
tags: ['openshift','security','cve management','rhacs']
|
||||
draft: false
|
||||
authors: ['default']
|
||||
summary: ""
|
||||
summary: "How do we deal with vulnerable workloads we can't patch?"
|
||||
---
|
||||
|
||||
IPSec was a quick job and the cluster is looking good after enabling it. Your afternoon job is to pair up with Angie again and review the vulnerability status of the ACME Financial Services workloads that are deployed on the cluster so far.
|
||||
@ -47,7 +47,7 @@ If you've successfully secured the banks vulnerable payments processor please po
|
||||
|
||||
> Please review [team name] solution for exercise 4, our payments processor application is now unhackable.
|
||||
|
||||
WARNING: The hackathon team will perform a brief penetration test of the application. If your application is not actually secured and remains exploitable by the log4shell vulnerability one of your OpenShift cluster nodes will be deleted for the lulz. No pressure!
|
||||
**WARNING: The hackathon team will perform a brief penetration test of the application. If your application is not actually secured and remains exploitable by the log4shell vulnerability one of your OpenShift cluster nodes will be deleted for the lulz. No pressure!**
|
||||
|
||||
This exercise is worth `25` points. The event team will reply in slack to confirm your updated team total score 🎉
|
||||
|
||||
|
||||
Reference in New Issue
Block a user