jmhbnz/workshops
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Tweak wording.

Browse Source
This commit is contained in:
James Blair
2024-10-23 17:26:33 +13:00
parent f30a8af73f
commit 0b061fa8b7
2 changed files with 2 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/workshop/exercise4.mdx
View File

@ -28,7 +28,7 @@ The core banking payments processor namespace `prd-acme-payments` is vulnerable
## 4.2 What the %$^& do we do???? ## 4.2 What the %$^& do we do????
In the minutes following the alarming discovery you observe a series of rushed conversations and Microsoft Skype for Business™ conversations between Angie and various security team members, service owners and incident management team members. In the minutes following the alarming discovery you observe a series of rushed conversations and Microsoft Skype for Business™ chats between Angie and various security team members, service owners and incident management team members.
A critical incident has been raised but at this point the consensus is the application simple cannot be turned off. It's a core component of the banks payments processing and must continue running. A critical incident has been raised but at this point the consensus is the application simple cannot be turned off. It's a core component of the banks payments processing and must continue running.

6
data/workshop/exercise5.mdx
View File

@ -55,11 +55,7 @@ Scan finished you begin stepping through Melissa the individual results.
If you've successfully run the compliance scan and remediated the compliance issue please post an issue in `#event-anz-ocp-security-hackathon` with the message: If you've successfully run the compliance scan and remediated the compliance issue please post an issue in `#event-anz-ocp-security-hackathon` with the message:
> Please review [team name] solution for exercise 5, our payments processor application is now unhackable. > Please review [team name] solution for exercise 5, our cluster is now [percentage] compliant against NIST 800-53 at a cluster level.
**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 🎉 This exercise is worth `25` points. The event team will reply in slack to confirm your updated team total score 🎉
![safe](/static/images/security/hack-prevented.png)