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
+20-7Lines changed: 20 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,19 +26,24 @@ NOTE - to understand possible values for the action input `flags`, run the Secur
26
26
27
27
`$ bloodhound-cli recon --help`
28
28
29
-
## Create your SecureStack API Key and save as GitHub Secret
29
+
## Create your SecureStack API Key as GitHub Secret
30
30
31
-
1. Log in to [SecureStack](https://app.securestack.com) and go to the Profile -> GENERATE KEY screen.
32
-
2. Generate an API key and copy the value.
33
-
3. Go to Settings for your GitHub repository and click on Secrets at the bottom left.
34
-
4. Create a new secret named SECURESTACK_API_KEY_SECRET and paste the value from step 2 into the field.
31
+
1. Create a [SecureStack](https://app.securestack.com) account using your GitHub credentials. You get 20 scans for free and you don't need to add a credit card.
32
+
2. Once you are logged in go to "Profile" in the black drawer on the left, and then -> GENERATE KEY tab.
33
+
3. Generate an API key and copy the value.
34
+
4. Go to Settings for your GitHub repository and click on Secrets -> Actions at the bottom left.
35
+
5. Create a new secret named SECURESTACK_API_KEY and paste the value from step 2 into the field.
35
36
36
37
## Retreiving your SecureStack Application ID
37
38
38
39
1. Log in to [SecureStack](https://app.securestack.com).
39
-
2. Open the application you wish to analyse.
40
+
2. Open the application you wish to analyse. If you haven't created a managed application you can follow the directions in this [VIDEO](https://youtu.be/mapgawLMVKg) to create one.
40
41
3. Copy the value of the application id on the View Application screen.
41
-
4. Paste into the value of the `securestack_app_id` action input for the step using the SecureStack action in your workflow.
42
+
4. Go to Settings for your GitHub repository and click on Secrets -> Actions at the bottom left.
43
+
5. Create a new secret named SECURESTACK_APP_ID and paste the value from step 3 into the field.
44
+
45
+
## Watch this video to learn how to setup your first GitHub Action with SecureStack
46
+
[](http://www.youtube.com/watch?v=0sYXsCmY2es"Video Title")
42
47
43
48
## What vulnerabilities do we find?
44
49
1. Scans web application for out of date and vulnerable applicaiton components
@@ -48,4 +53,12 @@ NOTE - to understand possible values for the action input `flags`, run the Secur
48
53
5. Identifies if app is using CSP or security headers and whether they're working
49
54
6. Finds WAF bypass attacks for Akamai, Cloudflare & Imperva
50
55
56
+
## Check out our other GitHub Actions:
57
+
1.[SecureStack Secrets Analysis](https://github.com/marketplace/actions/securestack-secrets-analysis) - Scan your application for embedded api keys, credentials and senstive data.
58
+
2.[SecureStack Software Composition Analysis (SCA)](https://github.com/marketplace/actions/securestack-application-composition-analysis) - Scan your running application url for cloud misconfigurations and web vulnerabilities.
59
+
3.[SecureStack Log4j Analysis](https://github.com/marketplace/actions/securestack-log4j-vulnerability-analysis) - Scan your application for Log4j/Log4Shell vulnerabilities.
60
+
61
+
## Learn more about SecureStack with our YouTube Channel:
0 commit comments