1 / 10

Enhancing Computer Forensics Education: Strategies for Effective Classroom Implementation

This presentation addresses the challenge of teaching a comprehensive one-quarter course in computer forensics. It emphasizes the need for meaningful labs, focusing on the forensics process, incident recognition, evidence collection, analysis, and reporting findings. Key overlaps with computer security, networking, and legal aspects are discussed to create a cohesive curriculum. Practical laboratory setups, exercises for tool familiarization, and case analysis are highlighted as essential components for student engagement and skill-building. Resources like the Honeynet Project and SANS are provided for further learning.

kalare
Télécharger la présentation

Enhancing Computer Forensics Education: Strategies for Effective Classroom Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Computer Forensics in the Classroom Chris Eagle Naval Postgraduate School cseagle@nps.edu

  2. The Challenge • A one quarter course in computer forensics • Appropriate number of hours • Meaningful labs • More than just a survey of current state of forensics field

  3. Background • The “forensics process” • Pre-incident planning • Incident recognition and response • Evidence collection • Evidence analysis • Reporting of findings

  4. Recognizing Overlap • Much of forensics overlaps with other areas • Introductory computer security • Viruses, worms, steganography, cryptographic hashing, etc. • Networking and network defense • Secure management of systems • Recognize and reinforce, but don’t repeat

  5. Technical vs. Non-technical • What are the goals for your course? • High level SANS style overview? • Low level technically oriented? • How much time to dedicate to non-technical material • Legal issues • Handling and presentation of evidence • Could each be entire courses

  6. Laboratory Setup • Many considerations • Shared lab? • Windows vs. *nix • Open source vs. proprietary • Expense • VMware and its limitations • VMware Player • Use of “hostile” tools and/or content • Unhappy system administrators

  7. Lab Exercises • O/S Familiarity • Tool familiarization • Evidence collection • How do you “plant” evidence • Evidence analysis • Final project? • Report style • Case analysis • Consider case development

  8. Emphasizing Computer Science • Education vs. training • How does it all tie in to their studies • What are the challenges in forensics? • Binary analysis • RAM and virtual memory analysis • Steganalysis • Others

  9. Resources • Honeynet Project • Challenges and whitpapers • http://www.honeynet.org • SANS • Courses, newsletters • http://www.sans.org • Sleuth Kit • Collection and analysis tools and newsletter • http://www.sleuthkit.org

  10. Conclusion • Questions • Contact info • Chris Eagle • cseagle@nps.edu • 831-656-2378

More Related