New capa (identify capabilities in executable files) module with ATT&CK support (S18) #1212
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m-1-k-3
added
enhancement
|
New container (v1.4.1e) should be available for testing now |
m-1-k-3
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feature
As we have learned from the paper "ERS0: Enhancing Military Cybersecurity with AI-Driven SBOM for Firmware Vulnerability Detection and Asset Management" (see here) there might be some interest in using capa in EMBA. We are aware that capa is only supporting x86/64 architectures and so it is somehow limited in the firmware field. Nevertheless, if we have a supported architecture the results are quite useful:
The image shows also the links to the ATT&CK framework and to the MBCProject
Do not merge until we have the docker base image updated!