How good solution website hijacking?

  By way of knowing what your site has no security problem?

       IIS7 website monitoring
  test whether the site was hijacked, if the domain name is the wall, DNS information pollution detection.
  Website hijacking solve a very good way to analyze the effect after the next traffic hijacking There are several forms show?
  1, A label
  2, IMG tag
  3, IFRAME tag
  which has a same point, that there is a link, link domain name and domain name of the site is not linked! So there is a train of thought in these additional nodes into Dom's time to kill, so you almost can not get up! Specific ideas are as follows:
  1. Configure white list domain site
  2 binding MutationObserver on Body *, interception related events dom additional
  3, remove the domain name out there is no match to the
  4 reported was deleted domain name (to determine whether the error deleted)
  MutationObserver: so it is said that almost get away! However, the above solution is already running the ad, you can not deal with it before it?
  Then consider additional advertising carriers usually several ways by which it?
  1, an additional Script tag
  2, directly added to the end of the HTML Body if standing in the operator's point of view it? I usually choose an additional Script tag, because good maintenance, all I just need to focus on the Script content, channel management, upgrades, update I just change the link ok. So based on this, is not able to find a way to get almost the first, and in fact, the solution is the same as the first solution, only need to add a Script tag in the list of detected tags.
  So, for hijacking the site, we ought to grasp the different solutions can respond to different types of hijacking oh.

Guess you like

Origin www.cnblogs.com/xiaokeaia/p/11506110.html