Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Ghidra is the NSA’s reverse engineering suite, released as open source in 2019, combining a multi-architecture disassembler with a decompiler that reconstructs readable C-like code.

What Is Ghidra?
Ghidra is a software reverse engineering suite built by the United States National Security Agency and released as open source at the RSA Conference in March 2019. It takes a compiled binary and reconstructs what the program does: a disassembly of the machine instructions, a cross-referenced map of functions and data, and a decompiled view that reads like C.
The release changed the field. Before it, a decompiler of comparable quality meant a Hex-Rays licence costing thousands of pounds per architecture. Afterwards, any analyst, student, or small security team had one. Published vulnerability research and malware analysis increased visibly in the years that followed, and university courses rebuilt their syllabuses around it.
The core workflow is the same for every binary. Ghidra parses the file format, identifies the architecture, disassembles the code sections, recovers function boundaries, resolves imports and strings, and builds a cross-reference database. The analyst then works through that database, renaming functions and variables, applying data types, and gradually turning an anonymous instruction stream into something that can be reasoned about.
Three capabilities carry most of the weight:
Beyond those, Ghidra offers scripting in Java and Python, a version tracking feature for comparing two builds of the same program, the BSim function similarity database for finding known code in unknown binaries, and a server mode allowing several analysts to work on one project together.
The practical comparison with IDA Pro comes down to this. IDA has a faster and more polished interactive interface, a stronger debugger, a very large body of third-party plugins, and the FLIRT signature library for identifying statically linked code. Ghidra has a decompiler for every architecture at no cost, a better collaborative project model, open source that can be audited and extended, and no licensing friction for a team that needs ten seats.
Most working analysts keep both and move between them. There is no meaningful rivalry; the useful question is which one answers the current question faster.
Two conclusions follow from the existence of a free, capable decompiler, and both are uncomfortable for software vendors.
First, obfuscation buys time rather than secrecy. Packing, control flow flattening, and string encryption all raise the effort required, and none of them prevents a determined analyst from reaching the logic. Any security that depends on an attacker not reading your binary is already lost. See code obfuscation.
Second, patch diffing means the clock starts when you publish, not when exploitation begins. Organisations that treat a vendor advisory as the beginning of a comfortable scheduling discussion have the timeline wrong; for internet-facing systems the realistic exploitation window after a patch is days.
At Privia Security, our Hardware Penetration Test Services include binary and firmware analysis of the code running on embedded devices.
Yes, entirely. It is released by the NSA under the Apache 2.0 licence with the source code published on GitHub, and there is no paid tier, no feature-limited edition, and no licensing server. It is also actively developed, with regular releases adding processor support and decompiler improvements, and it accepts contributions from outside the agency.
A disassembler converts machine code into assembly instructions, which is an exact but verbose representation. A decompiler goes further and reconstructs higher-level structure, producing C-like pseudocode with loops, conditionals, and function calls. The output is not the original source and variable names are lost, but it is far faster to read, particularly on an unfamiliar processor architecture.
It gained a debugger in version 10, with support for connecting to GDB, LLDB, and the Windows debugging engine, but it is less mature than IDA Pro’s. Many analysts use Ghidra for static analysis and a separate debugger such as x64dbg, WinDbg, or GDB for dynamic work, moving findings between the two as the analysis develops.
Assume a motivated analyst can read your binary. Obfuscation raises the cost and buys time; it does not provide secrecy. Keep secrets off the client entirely, enforce authorisation on the server, and store keys in hardware. Also treat your own patches as disclosures, since patch diffing reveals the vulnerability to anyone who downloads the update.
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.