Static Analysis on Windows
Trainees get hands-on with static reverse engineering tools and core analysis techniques, then apply them to obfuscated binaries, CrackMe challenges, license protections, and real malware samples.
Module Overview
Get hands-on with industry-standard static reverse engineering tools, including IDA, Ghidra, and Binary Ninja. You'll learn to navigate between pseudo-C and assembly representations, and work with core static analysis features such as function graphs, strings, imports and exports, symbols, and cross-references.
Learn to identify and analyze common obfuscation techniques used to hinder static analysis, and how to perform binary patching to work around them.
Apply your skills to real-world targets, including CrackMe challenges, license protection schemes, and malware samples, building the ability to independently perform static analysis of protected and malicious binaries.
Over 10 Years of Hands-On Expertise.
Effective security testing comes from the combination of the right tools, deep technical knowledge, and the people who know how to apply them. eShard has spent over 10 years developing all three, and our coaching programs put that same expertise directly in your hands.
Frequently Asked Questions
Most courses can be delivered online. Some modules, particularly those involving lab equipment, require onsite presence. Onsite training can be held at eShard's headquarters in Bordeaux, France, or at your own premises. The delivery format can be discussed and agreed upon before the final proposal.
Prerequisites vary by module. Some courses include introductory content for participants new to a topic, while others assume prior knowledge of cryptography or security testing. Each module page indicates the expected background.
Most programs accommodate 3 trainees per coach. Based on our experience, this ratio ensures everyone progresses at the same pace and gets the most out of the session. Contact us to discuss larger groups or custom arrangements.
Yes. Training programs are tailored to each team's technical level and objectives. If your team works on specific targets or protocols, this can be factored into the program before the session begins.
