auditing
Here are 184 public repositories matching this topic...
-
Updated
Sep 23, 2020 - Shell
Currently, facades implement good exception handling, but resource parsing does not. That means that for a given resource type, if parsing fails for any given resource, the fetch_all
method fails and stops, hence not parsing any additional resources.
All resources should be reviewed and updated, to ensure they handle parsing errors.
e.g., for AWS IAM roles (https://github.com/nccgroup/Scou
-
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)
-
Updated
Feb 20, 2020 - Go
-
Updated
Aug 30, 2020 - Go
-
Updated
Mar 24, 2020 - Shell
-
Updated
Oct 5, 2020 - Python
-
Updated
Sep 6, 2018 - Ruby
-
Updated
Oct 10, 2020 - Scala
-
Updated
Oct 2, 2020 - Python
-
Updated
Feb 8, 2020 - C
-
Updated
Jun 25, 2020 - Java
-
Updated
Jun 16, 2020 - C#
-
Updated
Aug 15, 2020 - Go
-
Updated
Mar 29, 2016 - PHP
-
Updated
Sep 11, 2020 - HTML
-
Updated
Aug 19, 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: