SecOps - Security's a Need-to-Know Event Problem
- — Jan. 29, 2013, 1:24 a.m.
Security OPS teams are often limited by their own rules. When an event is suspected, the only people allowed to have knowledge and information about the suspected event are security people, which limits not only the effectiveness of that investigative body, but also the effectiveness of detection, early-warning, and response ultimately. This need-to-know problem is the reason why many organizations have separate IT OPS and Security OPS event managers, ticketing systems, and investigative processes...Read the full article
Sign up now »
Protect resources and ensure security compliance through incident detection, response, and remediation.
Incident handling is a vast topic, but here are a few tips for you to consider in your incident response. I hope you never have to use them, but the odds are at some point you will and I hope being ready saves you pain (or your job!).
- Have an incident response plan.
- Pre-define your incident response team
- Define your approach: watch and learn or contain and recover.
- Pre-distribute call cards.
- Forensic and incident response data capture.
- Get your users on-side.
- Know how to report crimes and engage law enforcement.
- Practice makes perfect.
I’m dating myself, but I remember when holiday shopping involved pouring through ads in the Sunday paper, placing actual phone calls from tethered land lines to research product stock and availability, and actually driving places to pick things up. Now, holiday shoppers can do all of that from a smartphone or tablet in a few seconds, but there are some security pitfalls to be aware of.