Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Security

+ - Conficker/Downadup mitigation

Submitted by
XenoPhage
XenoPhage writes "I'm working on possible mitigation scenarios for a potential Conficker/Downadup outbreak. One of the ideas we have is to "poison" our own DNS caches, effectively redirecting any infected clients to a local server. The thought is that this would help identify infected systems as well as prevent them from receiving updated instructions from command and control. The question is, however, how to do this, as well as what possible side effects will we encounter. Is this method absolutely taboo and should be avoided at all costs, or is this a valid method of detection/mitigation?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Conficker/Downadup mitigation

Comments Filter:

Shortest distance between two jokes = A straight line

Working...