auditing
Here are 186 public repositories matching this topic...
-
Updated
Oct 28, 2020 - Shell
This rule is flagging regions where there's no trail for multi-region trails (i.e. it's flagging all the regions other than the one where the trail is).
-
Updated
Sep 12, 2018 - HTML
-
Updated
Apr 10, 2020 - Python
There are lots of other common development ports that we should check for, including (but not limited to):
-
5000(Flask and Kestrel's default port) -
9200(Elasticsearch's REST API)
WAF detection
-
Updated
Feb 20, 2020 - Go
-
Updated
Aug 30, 2020 - Go
-
Updated
Mar 24, 2020 - Shell
-
Updated
Oct 26, 2020 - Python
-
Updated
Sep 6, 2018 - Ruby
-
Updated
Nov 7, 2020 - Scala
-
Updated
Oct 28, 2020 - Python
-
Updated
Feb 8, 2020 - C
-
Updated
Jun 25, 2020 - Java
-
Updated
Jun 16, 2020 - C#
-
Updated
Oct 27, 2020 - Go
-
Updated
Mar 29, 2016 - PHP
-
Updated
Sep 11, 2020 - HTML
-
Updated
Nov 3, 2020 - Jupyter Notebook
-
Updated
Jul 26, 2019 - C#
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
-
Updated
Mar 25, 2019 - JavaScript
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."


It would be nice if lynis would gather (and report in the portal/reports) information about user-accounts: