Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.1: Run Automated Vulnerability Scanning Tools #9

Open
codydumont opened this issue Sep 18, 2019 · 0 comments
Open

3.1: Run Automated Vulnerability Scanning Tools #9

codydumont opened this issue Sep 18, 2019 · 0 comments

Comments

@codydumont
Copy link

---- issue 1
Vulnerability Scanning Coverage - The ratio of endpoints covered by at least one vulnerability scanning tool to the total number of endpoints

While I agree in principle, all scans are not created equal. So I think we need to define what scan is at this level. A ping sweep, or syn scan, is far different than credentialed scan. So we should establish a minimal goal for the scan. Since 3.2 is authenticated scan, I assume this is an uncredentialed scan at a minimum. So I think service enumeration, OS Detection, TCP Scan, or Syn Scan, and any other basic uncredentialed information is required here.

------ issue 2
Vulnerability Scanner Configuration Quality

This metric goes to my "issue 1", we need some guidance on what is configuration requirements.

---- Issue 3
The ratio of SCAP-validated scanners to the total number of vulnerability scanners

So if the organization has a web application scanner, Nessus, and NMAP, the total scanners is 3, and SCAP validated is 1. Does this look correct? again I would have examples in here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant