Skip Links

Network World

IT Careers: News and advice

The notification chain when a breach is suspected

Many IT departments are investing significant time and money on log management or security incident and event management tools. It might be to meet a regulation or mandate -- Payment Card Industry standards, for instance -- or to better understand what is happening in the computing environment. Such tools enable the administrators to take a lot of disparate bits of event information, correlate them and present them in a way in which it's easy to spot anomalies.

What happens when the person monitoring the log management or SIEM dashboard sees something a little out of the ordinary? He drills down for details, of course. But what happens (or should happen) when those details begin to suggest something ominous, such as a data breach or corporate fraud? At this point, a lot of care needs to be taken in how the log data is handled and who must be notified of the situation. How the data is handled could impact whether or not it can later be used as evidence in a criminal or civil charge. Who is notified of the suspected breach and how they contribute to the investigation is another delicate matter.

A few weeks ago, we provided best practice tips on preserving log data for a forensic investigation (see "Using computer log data to support a forensic investigation" here). In this article, we'll discuss the notification chain and how other experts support the investigation and its fallout.
Continued

Recent Newsletters | Archive

Post A Job!

PostSingle Job Posting
$250 for 60 days
Packages available

More ways to stay informed

NetworkWorld content as you like it

News

Career and Certification Blogs

Get instant email notification when white papers, webcasts, executive guides are added to our library. Stay informed and up-to-date with the latest on IT Technologies with Network World's Resource Alerts.