Tip

Specific steps to repel hackers

If you've been the target of a hack, there are specific actions you should take to repel the invader(s). The first step is to determine whether or not the hack originated from within or outside of your organization.

For Internal Hacks

  • Keep regular audit trails. Make a copy of all logs, both electronic and hand-written notes.
  • Pause the server service.
  • Immediately kill/suspend the offending user's connection to the server(s).
  • Do NOT delete the connection. You will need it to access resources that the rogue user created or took control of. Some network services will recognize this disabling immediately, and cut off access to the user - even while connected.
  • Use the SHUTDOWN or SHUTGUI utilities found in the Windows NT/W2K Resource Kit. This will buy you valuable time and disrupt the hacker's invasion by precious minutes. That may not sound like much, but it gives you time to troubleshoot and track. And, more importantly with the account disabled, the malicious user will be unable to log back onto the domain.
  • Call management. Confront the perpetrator; escort them to Human Resources and formally charge them with violation of company policy. Depending on individual corporate security policy, you may also want to notify the appropriate law enforcement authorities, press charges and have the user reprimanded/escorted from the building. This of course, depends on the severity of the infraction and whether or not it was a first time offense.
  • Review audit trails. This will give you a history of the hack and help you identify any accomplices.
  • Close the loophole that allowed the hack.

For External Hacks

  • Monitor and record all activities. Track the hacker and determine the point of entry.
  • Pause the server service.
  • Disable/but do not delete the connection.
  • Continue to follow the steps outlined above for internal hackers.
  • Maintain audit trail logs and take detailed notes of the properties of the attack. This will be used as evidence if/when your organization decides to prosecute. If you don't have evidence you can't prosecute.
  • Immediately notify management, as well as, appropriate law enforcement and security professionals.
  • Block the hacker's IP address at the port or router until you can gain control.

DiDio is a Giga Group analyst who covers Windows 2000 and third-party products and utilities


This was first published in November 2000

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.