I was recently engaged to help remediate some exposures found during the preparation for PCI DSS compliance reporting. They had run an external vulnerability scan with Nessus so that they could find exposures and fix them before the “official” scan was run.
Several vulnerabilities were found that would have caused the organization to fail their external vulnerability scan. Many of the vulnerabilities were due to an open port on the server. Several cross-site scripting vulnerabilities were found. Sample code from one of the installed applications was publicly accessible.
As we were working through these issues, a common theme came up.
How do we fix Issue X so that we pass the scan?
Now think about that a minute… Approaching the vulnerabilities with this attitude is kind of like fixing a flat tire with Fix-A-Flat. It may work, but you should still have the tire looked at by a professional.
Here’s a specific example from the vulnerability scan. Port 8080 was publicly available on the web server. Several vulnerabilities were found on 8080. It was suggested that we just block 8080 at the firewall. Sure that would work to keep the problems from being found in the external vulnerability scan. But is that the right fix? No.
The right fix was to harden the server by shutting down any unneeded services and to block an unneeded ports on the firewall and uninstall the sample code from the server and institute change control on servers and firewalls and ……
My final recommendation? Take steps to think beyond compliance requirements. Checkboxes and automated scans are helpful, but nothing replaces good analysis and testing. Meeting compliance requirements is a good starting point, but don’t omit really knowing the risks your organization faces.
- Dan
{ 0 comments }




