CAPA¶
What CAPA does¶
Using this tool
CAPA supports malware analysis. In this guide, you will use it to identify likely capabilities in a known training executable and validate rule evidence. Follow the steps below and keep the output with your notes.
Tool guide at a glance¶
Identify likely capabilities in a known training executable and validate rule evidence.
An inert or purpose built training sample stored in a disposable isolated analysis VM.
A static observation or capability finding with sample hash, tool output, and confidence statement.
Evidence and safety
Do not execute unknown samples on SUSA. Disable shared folders and credentials, and use only authorised training material. Record the input identifier, tool version, relevant commands or settings, time and time zone, output location, and any errors or limitations as you work.
Choose your journey¶
01Understand the evidenceLearn the malware analysis concepts and limitations.Complete when you can explain what the evidence can and cannot show.Beginner · No tool required 02Follow the CAPA guideFollow the steps and screenshots below.Complete when the documented workflow produces its expected output.Guided · SUSA workstation · Time varies 03Interactive labPractise the tool workflow in a safe browser simulation.Complete when the guided result is supported by the case evidence.Beginner · Browser only 04Full LabUse your own training data, keep the output and explain what you found.Complete when another analyst can reproduce and verify the outcome.Intermediate · Isolated lab
How the labs complement this guide
The Interactive Lab uses example records to practise investigation decisions. It does not run the installed tool or establish how that version behaves. The Full Lab uses your own training environment and evidence. Obtain or create the required input before starting; a case name in an exercise is not a download.
Accessing CAPA in SUSA¶
CAPA analyses executable files, shellcode, .NET modules, and sandbox reports to identify the capabilities they contain. Rather than detecting malware families, it highlights what a program is capable of doing, such as installing services, acting as a backdoor, or communicating over HTTP.
Download the latest stable standalone CAPA binaries from the official release page.
Extract the ZIP archive to the C:\Tools\capa directory.
Adding CAPA to PATH environment variable¶
Open Environment Variables (Start → Environment Variables → Edit the system environment variables → Environment Variables).
Under User variables, select path and click Edit.
Click New and add (one entry per line):
Click OK (then OK on other windows to save changes).
Testing CAPA¶
Open an administrator Command Prompt and run CAPA against notepad.exe: