Was this supposed to be moderated Funny?

If you focus on the high-level requirements, it is certainly easy to take them out of context.

Quoted from the PCI document [1], "Malicious software, commonly referred to as âoemalwareââ"including viruses, worms, and Trojansâ"enters the network during many business approved activities including employeesâ(TM) e-mail and use of the Internet, mobile computers, and storage devices, resulting in the exploitation of system vulnerabilities. Anti-virus software must be used on all systems commonly affected by malware to protect systems from current and evolving malicious software threats."

Is Linux commonly affected by malware? No auditor is going to expect UNIX servers to have anti-virus software installed.

Item 6, "Ha!" ... nevermind the multiple detailed requirements under the high level bullet.

PCI is fantastic. It allows IT departments leverage to implement sometimes costly best practices that companies prefer to consider cost centers.

I'm still hoping you're just trying to be funny.

[1] https://www.pcisecuritystandards.org/security_standards/download.html?id=pci_dss_v1-2.pdf

Security through obscurity is not security.

Full disclosure is a good thing. Unfortunately, the commercial focus of the Internet allows people to forget.

Not fully disclosing the nature of the vulnerability only minimizes one's ability to completely assess the circumstance.

Using irrelevant and inapplicable metaphors does not further your point.

Although RFP's policy [1] does not particularly address vulnerability assessment methodology, it is what I often like to reference when this comes up.

[1] http://www.wiretrip.net/rfp/policy.html