You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ To understand a bit more about how that works, visit the git repo link above or
8
8
9
9
The idea with this is that imagine there is another Apache Struts or Log4j critical vulnerability that there is not yet a known CVE for so your vulnerability scans don't pick it up. This shows that Sysdig can help you catch the anomolous behaviors of that being expoited even as a zero day.
10
10
11
-
You can see various examples of how this works in the example-curls.sh file. Note that this tries to get the Node IP from kubectland assumes the port (30000 for the security-playground and 30001 for the security-playground-restricted).
11
+
You can see various examples of how this works in the [example-curls.sh](https://github.com/jasonumiker-sysdig/example-scenarios/blob/main/example-curls.sh) file. Note that this tries to get the Node IP from kubectl, so that has to be working, and assumes the port (30000 for the security-playground and 30001 for the security-playground-restricted) is reachable from the machine you are running it on.
12
12
13
13
NOTE: This is deployed with a service of type NodePort - if you'd prefer it to be a load balancer then modify that manifest to reconfigure the Service as well as the bash script addresses how you'd prefer. Just be careful as this is a very insecure app (by design) - don't put it on the Internet etc.
0 commit comments