Steps to Effectively Respond to a Security Incident and Threats on a Wireless Network

Only available on StudyMode
  • Download(s) : 157
  • Published : December 11, 2005
Open Document
Text Preview
Sean Franks
BIS 634

Steps to Effectively Respond to a Security Incident and Threats on a Wireless Network

Incident response is usually one of those security areas that tend to be impromptu—companies don't think about it until they have to. But that needs to change. In this paper I will discuss five steps - identification, containment, eradication, and recovery and follow up a business use to effectively response to a security threat and I will suggest four actions -use encryption and passwords, e-mail protection, install antivirus software, install workstation firewalls a businesses can take to effectively prevent a security incident in the future. Businesses today must manage growing risks to their mission critical networks from attacks such as spyware, rogue wireless LANs, compromised remote/VPN users, DDOS attacks, system misconfigurations, and unpatched OS's, all of which increase the risk of a network breach and interruption to both sales and business operations. Does your business operate a network that has public access? If you monitor that network—you are monitoring your network, right?—then sooner or later, you're going to have a security incident. How you respond to such an incident often decides how long your network will continue to function as a part of your business. Incident response is usually one of those security areas that tend to be impromptu—you don't think about it until you have to. But that needs to change. Every organization should develop an incident response policy (IRP). Security incidents don't wait for organizations to have their ducks in a row. In fact, they tend to occur at the most inopportune times. Let's look at five steps businesses can take to effectively respond to a security incident. Identification

First, identify the traffic to determine whether it poses a threat to your network. If your logs (i.e., IDS, firewall, event, etc.) uncover an issue or a user reports a problem, analyze the information to determine...
tracking img