Hello Brad,
It is not exactly a situation of the anti-virus products taking NAC into
account, but rather that a third-party (OPSWAT -
http://www.opswat.com/products/oesis-framework/supported-applications?type=antivirus)
is not up-to-date with the latest version. Cisco utilizes OPSWAT in
their compliance module of NAC and so support is reliant on OPSWAT being
updated. I believe there is a set timeline before support is added, but
I cannot find my documentation that indicates such.
Therefore, the option is to make one-off checks and rules to account for
latest version when they are not supported.
In terms of Security Center, I remember looking into it once for a
in-house application and the latest versions of it prevent
"unauthorized" access. It seemed that one would have to be certified to
interact with Security Center in order to prevent malware from having
access to it.
Dan
--
Dan Taube
Associate IT Support
Computer Infrastructure Support
Illinois State University
309.438.4357 [support]
309.438.8985 [direct]
On 5/22/12 8:54 AM, Terhune, Bradley N (Brad) wrote:
Good morning list!
A while back I sent out a memo asking if anyone knew if Cisco NAC
could check the Windows Security Center for compliance for AV and AV
defs. Does anyone have any ideas- any registry key to check against?
We were able to get Security Essentials 4.0 working with a registry
workaround.
How do you all handle new AV products coming into your environment?
These AV products don't seem to take the Cisco NAC into account. Some
currenty examples are Kaspersky 2012, AVG 2012, and Security
Essentials 4.0.
Our server is at 4.8 and so are our clients. Are we doing something
wrong? Are you all able to handle this better?
These seem like valid products. I hate that we have to tell them to
go get something else.
Thanks for any advice you might have.
Brad Terhune
[email protected] <mailto:[email protected]>
UTHSC ITS
