For credentialed scans of Windows systems, Nessus can detect the presence of many leading anti-virus solutions. This blog entry will discuss what sort of information can be reported, how this is relevant for compliance and vulnerability audits and the specific anti-virus solutions supported.
Auditing Anti-Virus Deployments
Nessus uses credentialed scans of Windows systems to audit the local files and registry settings to determine both the presence of an anti-virus solution, if it is indeed running and if it is up to date.
For supported anti-virus solutions, a separate Nessus plugin is used to specifically identify that software and determine if the signatures are up to date. At Tenable, our research group monitors vendor signature updates for each solution and then updates the corresponding Nessus plugin. To take advantage of this sort of auditing, your Nessus scanners should be subscribed for either the Registered Feed or the Direct Feed.
There are many reasons why an anti-virus solution can't receive an updated list of new signatures. Some of these could be due to licensing issues, expiring demos or even network connectivity issues such as DNS or firewall changes. In some cases, mal-ware or a new virus may have gotten into a system and explicitly attacked the existing anti-virus solution.
For IT organizations that wish to minimize complexity, detecting unauthorized anti-virus solutions present on the corporate network is very useful. Having multiple anti-virus solutions on one system can lead to performance, compatibility and stability issues.
Compliance and Vulnerability Auditing
For compliance, if an organization has selected one or more anti-virus solutions, being able to audit this with Nessus can prove to an auditor that a solution is indeed installed, in use and up to date. Residing solely on software enumeration won't let you know if an anti-virus has been installed, but has been disabled. It also won't let you know if the license or network connectivity is up to date.
Depending on the function of a system that is being scanned by Nessus, not having an anti-virus solution may be considered a vulnerability. Also, if it is assumed that a system is protected by an anti-virus solution, but in fact the solution isn't running, or does not have the latest signatures then it isn't really protected.
Detected Anti-Virus Applications
At the time of this writing, the following anti-virus solutions are detected as installed, running and up-to-date by Nessus:
- #24232 BitDefender Check
- #20284 Kaspersky Anti-Virus Check
- #12107 McAfee Anti Virus Check
- #21608 NOD32 Antivirus System Check
- #12106 Norton Anti Virus Check
- #12215 Sophos Anti Virus Check
- #20283 Panda Antivirus Check
- #21725 Symantec Anti Virus Corporate Edition Check
- #16192 Trend Micro Anti Virus Check
- #24344 Windows Live OneCare AntiVirus Check
Nessus also has plugin #16193 which aggregates the results from these other plugins. It is useful if you are in a multiple anti-virus solution environment and just want to find hosts that have a solution installed and operational.
The above plugins only report an issue if a problem is found with the detected anti-virus solution. Plugin #16193 reports if a system does have a known working anti-virus solution.Anda sedang membaca artikel tentang
Auditing Anti-Virus Products with Nessus
Dengan url
http://free3-antivirus.blogspot.com/2009/11/auditing-anti-virus-products-with.html
Anda boleh menyebar luaskannya atau mengcopy paste-nya
Auditing Anti-Virus Products with Nessus
namun jangan lupa untuk meletakkan link
Auditing Anti-Virus Products with Nessus
sebagai sumbernya
0 komentar:
Post a Comment