Quarterly scanning, held to the standard payment processors require.
PCI DSS requires internal and external vulnerability scans at least every three months. PackerIT scans on a platform certified as a PCI Approved Scanning Vendor (ASV) solution and explains every finding in plain language.
What PCI DSS requires
Requirement 11.3 of PCI DSS v4.0.1 calls for vulnerability scans of your cardholder data environment at least once every three months, both inside your network and from the internet, with high-risk and critical findings fixed and rescanned until they pass. Scans are also required after any significant change to the environment.
How PackerIT helps
- External scans on a PCI ASV-certified platform, the standard payment processors require
- Internal scans of the systems in and connected to your cardholder data environment
- Prioritized findings with clear remediation steps, so failures get fixed quickly
- Rescans to confirm the fixes, on a quarterly schedule we keep track of with you
Not only for merchants
Even if you never touch a card number, ASV-grade scanning is a useful benchmark: it is the independent standard payment processors rely on, and a higher bar than most other frameworks require.
From first call to confirmed fix
Nothing is scanned until you have approved exactly what is in scope.
Scoping call
We confirm your external IP addresses, domains and internal network ranges, and a schedule that fits your compliance cycle.
Written authorization
You sign off on the exact targets and testing window before any scan runs.
Scanning
External scans test your internet-facing systems from outside, the way an attacker sees them. Internal scans cover servers, workstations, firewalls, routers and switches.
Report
An executive summary for leadership, plus prioritized findings with severity ratings and clear remediation steps, in PDF or HTML.
Review & rescan
We walk through the results with your team, then rescan to confirm the fixes are closed.