Reverse Engineer
13 November 2013 | |
Lockheed Martin | |
Hanover, Maryland | |
United States | |
employer | |
Salaried employee | |
full time | |
yes | |
Want to work in a major crime lab surrounded by expert cyber security professionals?!? We’re looking for an exceptional malware analyst and reverse engineer with at least 2-5 years of software reverse engineering and software development experience. This person will play a critical role performing dynamic analysis of malware using debuggers and system tools to determine entrenchment, file system activity and network activity. They will perform static analysis of malware using IDA Pro to determine functionality. They will identify process, thread, kernel manipulation in malicious code and interact with running programs to perform analysis. They will report on malware analysis and general artifact discovery for dissemination. |
|
Experience with programming languages: Assembly language (X86) or C, C++. Two to five years of experience in software reverse engineering and/or software development. In-depth knowledge of IDA Pro/Debuggers, dynamic/static malware analysis and windows operating system internals (kernel, registry, file system, windows APIs). Bachelor of Science degree in Computer Science, Computer Engineering or related computer field, or equivalent computer related work experience. Department of Defense Basic Digital Forensic Examiner Certification or eligibility to take and pass the exam within 1 year from the date of hire. In order to be considered a candidate you must have an active Top Secret Clearance with eligibility for SCI. |
|
Computer forensic experience. Familiarization with VMWare Workstation, Wireshark, SysInternals tools, Visual Studio 2010, X84/ARM architecture, python, .net, Java, WinDbg. |
|
http://discoverlockheedmartin.com/cybersec/index.asp |
|
For more information, please contact Pete Bugnatto at peter.a.bugnatto@lmco.com Or visit the URL below where you can submit information and Pete will respond via your preferred method of contact. |
Leave a reply