Confickr and Us
Thank goodness this has turned out to be a dud so far. It did prove to us, once again, how valuable and forward looking our investment in Altiris products has turned out to be For our part we prepared for this is several ways:
1. With patch management we ensured that the relevant Microsoft patch was pushed out to all clients and moniroed the compliance throughout.
2. We put a host integrity check on our Sygate clients to put users who did not have the patch in a locked down mode.
3. We prepared jobs in NS to disable autorun features on USB devices.
4. Monitored and remediated virus signature levels.
I'm not foolish enough to believe that we aren't immune to attack but at least, perhaps, we made it a little harder for the bad guys.
Of course, our workstation services team insisted that I put all this stuff on CDs, just in case machines needed to be yanked off the network.
.
About Security Community Blog
The Security Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Security community. Any authenticated Connect member can contribute to this blog.
It's all about keeping security up to date
As the various documentation on Confickr repeatedly tells us, the loophole that confickr exploits, was plugged by Microsoft quite a long time ago, so if you are keeping your environment up to date with security releases and your antivirus products up to date with virus patterns, then you are very unlikely to be hit.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Patch managing is one of the
Patch managing is one of the most important aspects in every corporate environment ( and not only!).
Also the Carubin suggestion "prepared jobs in NS to disable autorun features on USB devices" is another good point to prepare a good defence from USB infections.
Would you like to reply?
Login or Register to post your comment.