Test Scope

Vulnerability Testing Scope

Audited by Netcraft is an automated vulnerability test of Internet-connected networks which checks for security vulnerabilities and configuration errors caused by system and network maintenance. The service detects all hosts within an Internet address range, and then performs a methodical examination of the detected hosts by applying tests for common misconfigurations and security weaknesses in all the services being offered. Key features of the service include:

Test Scope

Network examination reports cover all machines in the given address ranges from which responses were detected. For each machine detected, the services and characteristics of the machine are analysed.

TCP/IP characteristics
ICMP responses and other TCP/IP characteristics of the machine are examined. These are used to report operating systems and system uptimes where available.
TCP services
A table of available TCP services, and information obtained about them, is produced. Netcraft's tests identify the network service on each port — in particular, standard network services running on non-standard ports are identified and fully tested.
UDP services
A table of UDP ports which are believed to be open, and any information obtained from them. Note that due to the design of the UDP protocol, false positives are common in identifying active UDP ports, especially if firewalls are filtering content from these ports. If filtering is in place, our test suite switches to an alternative technique, sending well-formed packets to standard UDP services, and using other means (like RPC portmapper) to find listening services.
Vulnerabilities
Our test suite contains tests for a large range of vulnerabilities in standard network services. All the standard network services offered are tested for appropriate vulnerabilities.
SSL Services
Netcraft's tests against standard services, like HTTP, SMTP and IMAP, are all applied against the corresponding SSL services too. This is particularly important for highly secure services, where the main website may be very simple with only a few pages, but the HTTPS site offers a dynamic web application, using different software and a wider range of server modules. This is also important for sites using IDS systems, as the behaviour they experience over an SSL service may be different to the unwrapped service on the same machine. TLS wrapped services are also tested in full.
Web Content
When analysing the sercurity of web servers, a content trawl is performed. This process begins with your site's start page, and from there follows links to other pages on your site (limited to a certain depth and number of pages). This analysis is used to find web server technologies used by your site, like active server pages, CGI scripts, etc. If these technologies are discovered, further tests are performed, looking for misconfigurations and server vulnerabilities that may cause security problems, such as obtaining the source of server side scripts.

Stealth scans and spoofing attacks are not part of this automated test, since they require a more individual approach. Bespoke applications and server side scripts are also not covered by this automated scan. These are best covered by an in-depth analysis.

False Positives

Some vulnerabilities cannot be directly tested without disrupting your server. Denial of service attacks would obviously cause disruption if your system was vulnerable. Buffer overflow attacks are too dangerous to run against a live server. Therefore Netcraft avoids testing such vulnerabilities directly.

Netcraft identifies such vulnerabilities via indirect methods. Fingerprinting the operating system, the software installed, and the configuration of that software gives enough information to determine whether the server may be vulnerable to an exploit. If vulnerable software, or software in a vulnerable configuration, is found, then the vulnerability is reported as a "possible" vulnerability. It is also possible, however, that you are using a product that was vulnerable, for which you have applied a patch or configuration change that cannot be detected by our test. In this case the vulnerability will continue to be reported even though you are not vulnerable, because the patch cannot be safely tested. This is called a false positive.

Once a false positive has been investigated, Netcraft provides a facility to mark vulnerabilities that are false positives on your report. On future reports, a mark will appear in the "false positive" column for that vulnerability, and by hovering the mouse over the mark, the viewer can see when it was investigated and by whom. A count of the number of false positives is shown at the top of the report, just under the number of vulnerabilities — this allows you to see how many vulnerabilities have already been investigated, and how many remain.

Marking vulnerabilities as false positives is also valuable if you wish to use the Audited by Netcraft seal: the date of the last clean test will not be updated until any false positives have been marked as such.

CVE Names

Netcraft provides CVE names, where possible, for each vulnerability. These allow cross-referencing with other sources of information about the vulnerabilities discovered during our tests.

CVE (Common Vulnerabilities and Exposures) is a dictionary of standardised names for vulnerabilities and other information security exposures, which has been adopted by a large number of organisations throughout the computer security industry. CVE names are often quoted in security advisories.

The CVE name for each vulnerability is included as part of the information for each vulnerability in the report. In online reports generated by Netcraft, the CVE name is included in the "CVE name" column in the vulnerability table. In the "printable" reports, the CVE name is included in brackets after the vulnerability description. You can search reports for a particular CVE name using the text searching ability of your browser application.

Please note that not all vulnerabilities that are tested during a Network Examination will have an exact match to a CVE name. Usually this is because either the CVE entry is too specific or Netcraft's tests include vulnerabilities for which no CVE entry exists. If there is no matching CVE entry then no corresponding CVE name is given in the report.

Netcraft retrieve new copies of the base CVE database once per week. The version of the CVE database used for any given report is indicated at the end of the report.

CVE and the CVE logo are registered trademarks of The MITRE Corporation.

Errors and Omissions

If you find any serious inaccuracies in the report, or in the advisories referenced by the report, then please contact us at security@netcraft.com