Your shopping cart is currently empty.
Login
United Kingdom
Select regional store:
Requirement 11 of the PCI DSS (Payment Card Industry Data Security Standard) describes the need to regularly and frequently carry out tests to identify unaddressed security issues and scan for rogue wireless networks. Regular testing is fundamental to ensuring that an organisation is prepared for a range of attacks.
IT Governance’s PCI compliance penetration tests aim to assess your security systems, public-facing devices and systems, databases, and other systems that store, process or transmit cardholder data in order to discover your vulnerabilities before cyber criminals do.
Our penetration testing service will help you determine whether and how a malicious user could gain unauthorised access to assets that affect the fundamental security of your system, files, logs and/or cardholder data, and confirm that the controls required by the PCI DSS are in place and effective.
All identified vulnerabilities are presented in a format that allows your organisation to assess its relative business risk and the cost of remediation.PCI DSS Requirements 11.3.1 and 11.3.2 state that penetration testing must be performed at least annually and after any significant changes – for example, infrastructure or application upgrades or modifications, or after installing new system components. Organisations that do not regularly test the security controls governing their network and Internet-facing application leave vulnerabilities for criminal hackers to exploit. However, payment card data is usually the primary target in attacks against commercial environments.
Our penetration tests will help you:
Meet the penetration testing requirements of the PCI DSS with our comprehensive web application, infrastructure or wireless network penetration tests.
Merchants/service providers |
Quarterly* external vulnerability scan (ASV) |
Quarterly* internal vulnerability scan |
Annual** penetration test (Level 2) |
Quarterly wireless network analysis |
Annual web application vulnerability scan1 |
|---|---|---|---|---|---|
| Req. 11.2.2 | Req. 11.2.1 | Req. 11.3 | Req. 11.1 | Req. 6.6 | |
| RoC |
 |
|
++ |
|
|
| SAQ D for merchants |
|
|
|
|
|
| SAQ D for service providers |
|
|
++ |
|
|
| SAQ C |
|
|
# |
|
|
| SAQ C-VT |
# |
||||
| SAQ P2PE-HW | |||||
| SAQ B | |||||
| SAQ B-IP |
|
# |
|||
| SAQ A-EP |
|
|
+ |
|
|
| SAQ A | |||||
Purchase the required test |
 |
 |
|
 |
 |
* Or after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades).
** Or after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a subnetwork added to the environment, or a web server added to the environment).
# Only required for testing network segmentation if any is present.
+ Only external penetration test required.
++ For service providers, any network segmentation must be tested every six months.
1 Or after any change to the application. Applicable if developing own applications or using a third-party non-PCI-certified web application.