Most infosec forensics investigators walk a fine line. They must adhere to specific institutional processes, which, in many cases, are state and federal requirements. But they must also use a certain amount of pragmatism since no two investigations are exactly alike.
So while there may be a corporate best practice of collecting log files from all systems, that approach doesn't make sense if what you need is a single line of code from a log file to get you to the next level of the investigation, explains Richard Rushing, CISO of Motorola Mobility.
"I need to know if this user account logged into that server. And that information may already be somewhere else that doesn't require me to go through all the log files," he says. "That's the sort of thing people overlook sometimes." Process and pragmatism can work in tandem to help peel back the layers, Rushing adds.
With that in mind, here are 10 tips and refreshers for forensics pros working on IT incidents, suspected or real.
Terry Sweeney is a Los Angeles-based writer and editor who has covered technology, networking, and security for more than 20 years. He was part of the team that started Dark Reading and has been a contributor to The Washington Post, Crain's New York Business, Red Herring, ... View Full Bio