Describe the bug
Online docs for NETW-3200 are not yet implemented.

Version

• Distribution: Ubuntu 18.04
• Lynis version: 3.0.0

Expected behavior
A (minimal) description of the problem should exist and ideally a general direction on how to fix the issue.

Output

A new discovery!

Oops, looks like this control is not listed yet in the database.

Want to help 

In a server / client setup it would be great if Trivy would expose some metrics about the scans happen with the central server.
Some useful metrics for my implementation:

• Last DB Update (timestamp)
• Last DB Update Attempt (timestamp)
• Sum of Issues found
• Sum of Issues found splited up in SEVERITY
• Sum of Issues found splited up in sources (OS, Python, Node etc)

As Trivy is build to

Multiples wiki issues.

Typos

• https://github.com/infobyte/faraday/wiki/Executive-Report#using-markdown-on-a-report: -lenguage +language

Bad links

• https://github.com/infobyte/faraday/wiki/Executive-Report#requirements: https://github.com/infobyte/faraday/wiki/first-steps, the nedpoint first-steps doesn't exist anymore.

Images

• https://github.com/infob

Paste the full User-Agent String here

Time: Tue Jul 16 19:23:36 2019 -0300 
IP: 58.250.125.148 (CN/China/sogouspider-58-250-125-148.crawl.sogou.com) 
Failures: 5 (nginx_444) 
Interval: 3600 seconds 
Blocked: Temporary Block for 86400 seconds [LF_CUSTOMTRIGGER] 

Log entries: 

58.250.125.148 - - [16/Jul/2019:19:14:38 -0300] "GET / HTTP/1.1" 444 0 "-" "Sogou web spider/4.0(+htt

now that we're getting a few more contributers, standardize on ubuntu / osx as the dev os, and include more instructions here: https://github.com/intrigueio/intrigue-core/wiki/Setting-up-a-Test-Environment-on-Ubuntu-Linux

The database is saved to and used from the current directory versus somewhere better like ~/.vfeed/. This hampers several things, but most notably putting a symlink somewhere in my path to be able to call/use vfeedcli.py from any directory (cd ~/bin; ln -s path/to/vFeed/vfeedcli.py vfeed) like a system-wide command.

Btw, I have a patch for this already and will sent a PR shortly.

I would love to see a short section about the error codes of check.

Black (under Command line options) does that and it helped me a lot:

--check                     Don't write the files back, just return the
                              status.  Return code 0 means nothing would
                              change.  Return code 1 means some fi

I did a basic line edit of the "Usage" section, but next it needs reorganization and more information.

Would anyone want to spend time on a call or two to help me understand some of the commands? Some of them aren't obvious to me from the command line help, so they might benefit from better explanation.

(I'll continue to work on this section, but having a technical expert to answer some of