Analytics
6/11/2013
08:17 AM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Tech Insight: What You Need To Know To Be A Cyber Forensics Pro

A look at the skills, experience, and personality traits that make a successful forensics expert

[Jason Sachowski is a security professional at ScotiaBank. His content is contributed through the auspices of the (ISC)2 Executive Writers Bureau.]

Cyber forensics has become a hot topic in security -- and a critical skill that many enterprises would like to hire. But exactly what skills and experience does a security pro need to become a forensics expert?

The first set of skills is knowledge of IT technology and its relationship to the collection of security data and digital evidence. For example:

• From the boot sequence to process handling and resource allocations, you must understand the many elements of operating systems and how each OS influences the existence of digital evidence.

• Beneath the OS, you must be able to differentiate the underlying file systems -- how and where digital evidence is structured, stored, and accessed.

• Behind these logical components, you must have a solid knowledge of how physical hardware -- or storage media -- determines how digital evidence is stored and distributed

These aspects of forensics are also useful in other security-related pursuits, such as e-discovery or incident response, making them foundational skills that are essential to every cyber forensic professional. Depending on where you practice and the technologies in your environment, you may also need other technical skills and knowledge, such as cryptography or network communications.

One of the keys to cyber forensics is how you analyze and interpret data. If you rely too much on subjective viewpoints based on your own experience, you may overlook evidence. On the other hand, too much reliance on raw data can also lead to wrong or incomplete conclusions. Software tools have made it easy for just about anyone to perform forensic "analysis," but finding data is only one piece of a larger and more complex puzzle.

Analytics is about the ability to extract meaning, sort through masses of data, and find the hidden patterns and unexpected correlations. It's not about knowing everything -- it's about finding what is relevant and getting closer to the right elements with the right people. To do that, you need to maintain a level of objectivity; set aside your personal and professional influences and biases and focus on the data.

Forensics professionals cannot solely rely on technology to solve problems -- they must build analytical skills that are learned and refined by thinking through trial-and-error. For example, a good forensic investigator doesn't rely solely on the data found online -- printouts, handwritten notes, or manuals may also provide important evidence.

Forensics pros also need some understanding of the law. In additional to understanding process and procedures followed by law enforcement or your employer, you must ensure that all digital evidence is handled in a way that will stand up in court. While you don't need to be a lawyer, here are a few critical precautions and requirements you must ensure are upheld throughout every digital investigation:

• Safeguards must be taken to preserve the original data. This requires taking a bit-level image that can be used throughout the analysis process; the original should not be touched.

• Verify that all data remains unaltered in its originally identified state. Use hash algorithms to validate the authenticity of all data.

• Establish and maintain a proper chain of custody throughout the data's life cycle, from identification to destruction. Evidence must be inventoried, labeled, and controlled to ensure it is not altered or contaminated.

When you're working with digital investigations, always keep in mind that evidence -- or even perhaps you -- may end up in court. Just like police officers record events in their notebooks, forensic investigators must maintain documentation for every interaction.

For example, a forensic investigator's logbook should include (at a minimum): the date, time, and analyst's full name for each interaction. It should illustrate page number/sequence and have no whitespace available -- fill that space with a solid line to prevent supplementary comments from being inserted.

Aside from a logbook, there are other important pieces of documentation that are required throughout the investigation life cycle:

• Acquisition (or seizure) forms must be completed -- prior to being removed from a crime scene -– to accurately identify the evidence and when it was seized.

• Exhibit numbers should be assigned using a centralized record book to catalog and inventory evidence as part of the investigation.

• Labels should be appended to all evidence, associating it to the investigation along with its respective exhibit number.

• Chain of custody must be maintained to demonstrate when and where the evidence is handled, stored, and ownership transferred.

The final piece of documentation is the investigative report. As a technical professional, you will be required to translate techniques, methodologies, and findings so they can be communicated and reproduced across business, civil, or criminal court settings. This can be an overwhelming task for a technical individual who -- depending on experience -- has had limited involvement in the business aspects of cyber forensics.

The ability to navigate both technical and business settings is important in cyber forensics. Whether you are looking to further your industry credibility or advance your career, you need to show you can operate outside the purely technical environment. In addition, you must be able to show that you can consistently apply forensics principles to other IT fields, including e-discovery or incident response.

Cyber forensics is one of the fastest-growing and most in-demand areas of specialty in security. However, it isn't easy to establish your credibility in a way that is universally accepted. (ISC)2 is making an effort to certify this expertise with its new Cyber Forensics Professional certification, but the program is still brand new. You may have to establish your own credentials, both legal and professional.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web