-
Updated
Oct 15, 2021 - Shell
auditing
Here are 221 public repositories matching this topic...
-
Updated
Sep 7, 2021 - Shell
-
Updated
Apr 10, 2020 - Python
-
Updated
Sep 12, 2018 - HTML
.well-known (RFC) is becoming an increasingly popular destination for stashing site-wide metadata. Some of that metadata is relevant to site security or may unintentionally leak information, so we should scan it.
Some starting points:
- Presence of/interesting things in an MTA-STS policy (RFC)
- This might be
WAF detection
-
Updated
Oct 4, 2021 - Go
-
Updated
Jun 24, 2021 - Go
-
Updated
Oct 1, 2021 - Python
-
Updated
Mar 24, 2020 - Shell
-
Updated
Oct 12, 2021 - Python
-
Updated
Sep 6, 2018 - Ruby
-
Updated
Oct 18, 2021 - Scala
-
Updated
Nov 21, 2020 - Go
-
Updated
Mar 20, 2021 - C
-
Updated
Jun 25, 2020 - Java
-
Updated
Mar 29, 2021 - C#
-
Updated
Mar 29, 2016 - PHP
-
Updated
Sep 25, 2021 - HTML
-
Updated
Aug 14, 2021 - Jupyter Notebook
-
Updated
Jul 26, 2019 - C#
-
Updated
Aug 4, 2021 - Ruby
The same way we have flags for avoiding indexing and scanning forks or repositories on personal namespaces, we should add one for ignoring repositories that are marked as private, in both GitLab and GitHub.
-
Updated
May 25, 2016 - Python
Improve this page
Add a description, image, and links to the auditing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the auditing topic, visit your repo's landing page and select "manage topics."


The https://github.com/nccgroup/ScoutSuite/blob/master/ScoutSuite/providers/gcp/rules/findings/iam-lack-of-service-account-key-rotation.json finding should only flag
USER_MANAGEDkeys (https://cloud.google.com/iam/docs/reference/rest/v1/projects.serviceAccounts.keys), asSYSTEM_MANAGEDkeys are "managed and rotated by Google"