Skip to content

Commit b396c42

Browse files
authored
updated the README
added things we scan for at bottom of README
1 parent b4dae9f commit b396c42

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

README.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,7 @@
33
A GitHub Action that analyses your web application for security and availability issues.
44
When you add this to GitHub Actions we will analyze your web app everytime you deploy to a
55
public endpoint and let you know if what you've just deployed is secure and meets your
6-
requirements.
7-
8-
See the section below
6+
requirements. See below for what types of issues this action scans for.
97

108
```
119
name: Example Workflow Using SecureStack Web Vulnerability Exposure Action
@@ -42,5 +40,12 @@ NOTE - to understand possible values for the action input `flags`, run the Secur
4240
3. Copy the value of the application id on the View Application screen.
4341
4. Paste into the value of the `securestack_app_id` action input for the step using the SecureStack action in your workflow.
4442

43+
## What vulnerabilities do we find?
44+
1. Scans web application for out of date and vulnerable applicaiton components
45+
2. Identifies whether basic security controls like WAF, firewalls, and security headers are being used
46+
3. Finds all public facing assets & helps you understand your application attack surface
47+
4. Identifies misconfigurations in existing WAF or CDN
48+
5. Identifies if app is using CSP or security headers and whether they're working
49+
6. Finds WAF bypass attacks for Akamai, Cloudflare & Imperva
4550

4651
Made with 💜 by [SecureStack](https://securestack.com)

0 commit comments

Comments
 (0)