INFRA-9 Vulnerability Scanning

What is INFRA-9 Vulnerability Scanning Control?

Vulnerability scanning is the process of identifying security weaknesses and flaws in systems and the software running on them. This is an integral component of a vulnerability management program that has one overarching goal: to protect the organization from breaches and the exposure of sensitive data.

Available tools in the marketplace

The following listing is “crowdsourced” from our customer base or from external research. TrustCloud does not personally recommend any of the tools below, as we haven’t used them.

Vulnerability Scanning Tools
VM	Qualys
	Tenable Nessus
	AWS Inspector
Container	Snyk
	AWS ECR Image Scanning
	Qualys
	Anchore
	Clair

Available templates

TrustCloud has a curated list of templates, internally or externally sourced, to help you get started. Click on the link for a downloadable version.

• N/A: no template recommendation

Control implementation

NOTE: This control is 100% automated by TrustCloud. Connect your system to enjoy the benefits of automation.

For a manual implementation:

1. Install a vulnerability scanning tool to scan and analyze all vulnerabilities within your infrastructure.
   1. The tool must be configured to run continuously or on a frequent schedule (the schedule is up to each organization to determine).
   2. The tool must be configured to send a notification or alert when issues are found.
2. Implement a formal and repeatable way to resolve any issues identified. The issues must be resolved promptly (timeliness is up to each organization to define).

What evidence do auditors look for?

Most auditors, at a minimum, are looking for the below-suggested action.

1. Provide screenshots of the configuration settings of the tool showing that it is checking for vulnerabilities.
2. Provide a remediation ticket or document related to the issues found and the action steps taken to remediate the issue.

Evidence example

For the suggested action, an example is provided below:

1. Provide screenshots of the tool’s settings screen(s), showing that it is configured to continuously or frequently analyze your code.
   The following screenshot shows an example of a tool.
   
2. Provide a remediation ticket or document outlining issues found through the tool that shows that actions were taken to remediate the issue.
   The following screenshot shows an example of remediation configuration (This can include more detailed evidence of remediation)