Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Reverse engineering works out how something behaves without the source code or the documentation, by reading what the machine actually runs.

What Is Reverse Engineering?
Reverse engineering is the practice of determining how a system works by examining the artefact itself rather than its documentation. In security that usually means reading compiled code: a disassembler turns machine instructions back into assembly, a decompiler produces approximate source, and a debugger lets you watch the program execute one step at a time. The source code is gone, but the behaviour was never hidden, because the processor has to be told exactly what to do.
Ghidra, released publicly by the NSA in 2019, brought a capable decompiler within reach of anyone, and it remains the usual starting point alongside the commercial IDA Pro and Binary Ninja. Debugging on Windows is typically done with x64dbg or WinDbg, and dynamic instrumentation with Frida, which hooks functions in a running process and is particularly effective against mobile applications. Managed code barely needs reverse engineering at all: .NET assemblies and Android applications decompile close to their original form unless they have been deliberately protected.
Beyond the basics, emulators let you run code from one architecture on another, which matters for router and industrial device firmware, and symbolic execution frameworks reason about which inputs reach which paths without running every possibility.
Serious targets fight back. Anti-debugging checks detect an attached debugger and alter behaviour, timing checks notice the delays stepping introduces, and obfuscation flattens control flow or translates the program into a bespoke bytecode interpreted at runtime. Packers ensure that nothing meaningful exists on disk at all.
The general answer is to combine approaches. Dynamic analysis recovers decrypted strings and resolved functions that static reading cannot reach, a memory dump taken after unpacking becomes the input for static work, and specific anti-analysis checks are patched out once identified. Progress is iterative, and knowing when a question has been answered well enough matters more than completeness.
This is the part that is most often assumed and least often checked. Under the Copyright, Designs and Patents Act 1988, section 50B permits decompilation of a lawfully obtained program to obtain the information needed to create an independently written interoperable program, provided that information is not otherwise readily available and is not used for anything else. Section 50BA permits a lawful user to observe, study, and test a program to determine the ideas and principles underlying it. Both rights are protected: section 296A makes contract terms purporting to prohibit them void, so a licence clause banning reverse engineering cannot override them.
Those permissions are narrower than they sound. They do not authorise redistributing recovered code, circumventing technical protection measures, or breaching confidentiality obligations that exist independently of copyright. Testing software running on someone else’s systems also engages the Computer Misuse Act 1990, so authorisation in writing is required before any assessment of a third party’s platform. Analysing malware you encountered on your own network sits comfortably within normal practice; analysing a supplier’s product does not, without their agreement.
Build the skill deliberately rather than hoping for it. Start with small, well-documented binaries, work through published malware analyses with the sample in front of you, and keep notes that another analyst could follow. At Privia Security, our hardware penetration test services apply firmware and binary analysis to devices where no source code is available to the people deploying them.
In defined circumstances, yes. The Copyright, Designs and Patents Act 1988 permits decompilation for interoperability and allows a lawful user to study and test a program to understand its principles, and contract terms attempting to remove those rights are void. The permissions are narrow, so redistributing recovered code, defeating protection measures, or testing systems you do not own remains unlawful.
For serious binary work, yes, although less than people expect. Decompilers produce readable pseudocode for most compiled code, so assembly is needed mainly to verify what the decompiler guessed and to handle optimised or obfuscated sections. Familiarity with x86-64 and ARM calling conventions, stack layout, and common compiler patterns covers the majority of day-to-day analysis.
It is the comparison of a program before and after an update to identify exactly what changed. Because vendors rarely describe vulnerabilities in detail, attackers diff patched binaries to locate the fixed flaw and work backwards to a working exploit, often within days of release. This is the mechanism behind n-day attacks, and the reason patch deployment speed matters as much as patch availability.
Ghidra, because it is free, includes a decompiler, runs everywhere, and has extensive published material built around it. Pair it with x64dbg for dynamic work on Windows. Begin with programs whose source you can read afterwards, so you can check your conclusions, then move to documented malware samples where a published analysis exists to compare against your own.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.