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

• Expired or soon to expire passwords (passwd -e)
• Locked accounts (passwd -S )
• Expired accounts (chage -E / chage -l )

Integrate provider and service “logos” in the HTML report, so that they are more tailored.

For example, if Scout is run against an AWS account, AWS logos should be included in the report, as well as each services' logo.

icon sets:

• https://aws.amazon.com/architecture/icons/
• https://cloud.google.com/icons/
• https://www.microsoft.com/en-us/download/details.aspx?id=41937

The implement

There are at least two more security relevant headers that we should test for and produce judgements on:

• Cross-Origin-Opener-Policy
• Cross-Origin-Embedder-Policy

More resources:

• https://hacks.mozilla.org/2020/07/safely-reviving-shared-memory/
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
• https://developer.mozilla.org/en-US/docs/Web/HT

Now that we want to give more value to it, it would be nice if we could break down the areas of development on the project based on conventional commits.

Things we could have there

• Stats per scope
• Stats per action
• Stats per author
• Time range selector for the statistics