Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Conficker/Downadup mitigation

XenoPhage (242134) writes | more than 5 years ago

Security 0

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?"

cancel ×

0 comments

Sorry! There are no comments related to the filter you selected.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>