{"id":581,"date":"2020-04-19T10:01:30","date_gmt":"2020-04-19T10:01:30","guid":{"rendered":"http:\/\/www.pcidssguide.com\/?p=581"},"modified":"2023-10-09T13:44:24","modified_gmt":"2023-10-09T13:44:24","slug":"pci-vulnerability-scan-requirements","status":"publish","type":"post","link":"https:\/\/pcidssguide.com\/pci-vulnerability-scan-requirements\/","title":{"rendered":"What are the Requirements for PCI DSS Vulnerability Scanning?"},"content":{"rendered":"\n\n\n\n\n

Whether you are aware of it or not, hackers can exploit your network’s vulnerabilities and gain access to your sensitive data.<\/p>\n\n\n\n

Web server shortcomings, e-mail clients, POS applications, and operating systems can allow attackers to access your systems. Installing security updates and patches for cardholder systems or sensitive data environments will help fix many of the newly found bugs and vulnerabilities before attackers have a chance to exploit them.<\/p>\n\n\n\n

See Also: How to Successfully Pass a PCI Compliance Scan<\/a><\/strong> <\/p>\n\n\n\n

But to fix these vulnerabilities, you need to find them first. For this, you need to scan your systems by testing for vulnerabilities.<\/p>\n\n\n\n

An essential requirement of the Payment Card Industry Data Security Standard (PCI DSS) is 11.2, also known as the PCI vulnerability scanning requirement. This requirement requires companies to perform internal and external vulnerability scans four times a year in three months and after any significant network changes, irrespective of its size.<\/p>\n\n\n\n

But PCI DSS requirement 11.2<\/a> is not just about scanning network components and servers to identify vulnerabilities before attackers. It is also about improving and improving processes to stop vulnerabilities from reappearing.<\/p>\n\n\n\n

It takes more effort than most people realize to meet PCI DSS requirement 11.2. Here are helpful hints as you can apply it to meet PCI DSS vulnerability scanning requirements.<\/p>\n\n\n\n

How Vulnerability Scanners Work<\/strong><\/h2>\n\n\n\n

An internal or external PCI DSS vulnerability scan checks the configuration of specific devices and software through internal or external IP addresses, such as ports and services, to check for vulnerabilities.<\/p>\n\n\n\n

PCI vulnerability scanners provide different tools and scripts designed for vulnerability testing. Such tools vary but may include software operated by the Certified Scan Provider (ASV), command-line files, GUI interfaces, and open source technologies.<\/p>\n\n\n\n

Tenable Nessus<\/a> and Qualys<\/a> are widely recognized and used vulnerability scanning tools.<\/p>\n\n\n\n

Scan tools run a series of control scenarios on your networks, commonly known as a vulnerability scan, which can take 1-3 hours for a quick scan or over 10 hours for a more extensive scan. Scan times may differ depending on your environment.<\/p>\n\n\n\n

Control scenarios are designed to define device settings, configurations and behaviors that can lead to exploitable vulnerabilities. For example, if your scan examines operating system versions and finds an outdated Windows XP operating system, that operating system will be marked as vulnerable.<\/p>\n\n\n\n

See Also: What You Need to Know About Internal Penetration Tests<\/a><\/strong><\/p>\n\n\n\n

Vulnerability scanning is designed to be non-intrusive. It scans merely alerts and gives you a logged overview of suspected vulnerabilities for you to take action. Vulnerability scanning, unlike penetration testing, does not exploit vulnerabilities in your network and does not take testing further.<\/p>\n\n\n\n

See Also: What You Should Know About External Penetration Testing<\/a><\/strong> <\/p>\n\n\n\n

As you check your scan results, you will most likely find CVE (common vulnerability and exposure) numbers in your notifications. If not provided to you by the scanning provider, it will be easier for you to become familiar with the National Vulnerability Database<\/a> to examine CVE records to identify and prioritize risks.<\/p>\n\n\n\n

What are the Differences Between Internal and External Vulnerability Scans?<\/strong><\/h2>\n\n\n\n

PCI DSS requires two independent PCI vulnerability scanning methods, internal and external. Because internal and external scans evaluate a network by scanning it from different perspectives.<\/p>\n\n\n\n

An external PCI vulnerability scan checks for vulnerabilities at the end of your network or website. An internal vulnerability scan looks for network vulnerabilities by simply scanning local resources within your network.<\/p>\n\n\n\n

Generally, only ASV scans are considered sufficient for PCI DSS compliance concerning internal and external vulnerability scanning. Still, both external ASV scans and local vulnerability scans are required for PCI compliance.<\/p>\n\n\n\n

Your ASV will not perform your quarterly internal PCI vulnerability scanning. ASVs only perform external security scans. Your ASV may also install an internal vulnerability scanning tool on your network, but this does not eliminate the need for internal and external scanning.<\/p>\n\n\n\n

Therefore, it is best to double-check that you have performed your internal scanning and followed your vulnerability management procedures.<\/p>\n\n\n\n

You can choose from the following options to meet internal vulnerability scanning requirements:<\/p>\n\n\n\n