-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
discussion: capa doesn't handle sandbox or API traces #48
Comments
Hey, I am interested in this project. How can I get started with this? |
This is a larger project. Are you interested in the context of GSoC? |
Yes, I am. So, should I send the proposal regarding my approach? |
Yes, and please see the other steps we point out, i.e., the patch preparation. |
Even I am interested, I'll send the proposal right away! |
Great, yes, please share it with us in the respective GSOC repo discussion or via email. Ideally, use Google Docs or a similar tool so we can add comments. |
Alright, I have sent it over email, do check and review! |
closed in v7 by @yelhamer |
capa relies on analysis of code structures to identify patterns. this is similar to matching sequences of API calls or other events in a sandbox, but not exactly. right now, capa rules don't directly translate to identifying behaviors from sandbox or debugging output, but it seems like there's a lot of overlap. maybe we can find a way to re-use a lot of work we've done for the static analysis rules.
The text was updated successfully, but these errors were encountered: