The number of exploits and tools available to hackers are so vast, and software technologies evolving so rapidly, that it is very possible, maybe likely, that you will experience a hacked website.

When addressing such an event, it can be helpful to have a short checklist of tasks to perform in your recovery process. Doing the right things in the right order will be key to maximize your chances of successful and complete recovery, as well as mitigation of future events.

Your ToDo List

Your ToDo list will contain 2 types of tasks: Preparation tasks and Action tasks. Preparation tasks make NO CHANGES to your web site or any related or underlying components AT ALL.

Your preferred FIRST action MUST be make sure that the hacker has no way to continue accessing the system; ANY OTHER action that changes the web site may alert the hacker that he has been discovered before his access has been blocked, and you do not want to trigger the hacker into either perpetrating MORE damage, or covering his tracks.

Remember: once the event has happened, it must be treated not only as a reason to fix, but equally as a motivation to harden and secure.

  • Prepare: Reaction plan
  • Prepare: Battle sheet
  • Action: Take your system offline
  • Prepare: Clone your system to a testbed or staging server
  • Prepare: Scan your website for vulnerabilities; identify and confirm suspected intrusion point
  • Action: Fix the vulnerability
  • Action: Bring the fixed version of the site back online; whenever possible, you should redeploy the sanitized version of your website to a clean OS/Web Server setup
  • Prepare: Monitor your new and improved website
  • Prepare: Make a Reaction Plan for FUTURE events.

This article was published on Hack Hex website, under How-to section, written by Dawood Khan. Share & leave us some comments on what you think about this topic or if you like to add something.

Tags: cyber security, ethical hacking training, Event, hacked, hacking courses, hacking tools, infosec news, Penetration Testing, Recover, Website,