Binary analysis is the examination of compiled software directly to find what it contains, without relying on source code or a supplier's list. Tools inspect the finished files to identify the libraries and components included, and sometimes to look for known vulnerabilities.

It matters for SBOMs because a list produced from source code or build files may not match what actually ships. Analyzing the final product can reveal components that were not declared, such as code bundled in or statically linked, and it can check a supplier's list against reality.

It has limits. Identification relies on matching signatures and patterns, so it can miss components or misidentify them, especially when code has been modified or stripped of information. It may also raise false matches, and the results can differ between tools. It is usually more effort than reading a declared list, and legal limits on analyzing proprietary software can apply.

To use it, treat the results as a check on declared information, compare the output of more than one tool where it matters and review the findings manually before acting on them.