topic Re: PCI Compliance - 86476 Web Server Stopped Responding in General Topics

PCI Compliance - 86476 Web Server Stopped Responding

cenders — Fri, 16 May 2025 14:38:23 GMT

First time in years, getting this failed result to a PCI scan. 86476 Web Server Stopped Responding.

Their tech suggests it has something to do with my PAN WAF/IDS and they have a bunch of IP addresses/ranges that I can whitelist. I find this odd as I've never had to whitelist them before and I've passed many many scans prior to this.

How do I whitelist the Sysnet servers from any sort of WAF when they scan my external IP address?

Or is this some sort of glitch in their scanner.

Re: PCI Compliance - 86476 Web Server Stopped Responding

mshekh — Sat, 17 May 2025 00:30:01 GMT

Hi @cenders ,

Thanks for info, I am not sure, what method they are using to scan, if they are scanning the network behind your firewall then you have to open the requested ports to pass through the traffic from firewall.

Second if they are scanning your firewall exposed Public IPs, then you don't need to do anything.

Third if they are scanning firewall itself with logging to firewall then you have to allow the firewall access to there IP's to ssh / https the device for further scanning.

Re: PCI Compliance - 86476 Web Server Stopped Responding

cenders — Tue, 20 May 2025 19:11:43 GMT

It is an external scan, scanning the exposed public IP for any vulnerabilities.

Re: PCI Compliance - 86476 Web Server Stopped Responding

mshekh — Wed, 21 May 2025 02:32:18 GMT

Hi @cenders ,

Thanks for info, If public facing IP's are allowed for specific source then you have to add those IP, if you have source any then you don't need to make any config change at your end...