Skip to content
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

File extraction #120

Closed
geekscrapy opened this issue Aug 2, 2018 · 1 comment
Closed

File extraction #120

geekscrapy opened this issue Aug 2, 2018 · 1 comment
Assignees
Milestone

Comments

@geekscrapy
Copy link

Request Type: Question

Are there currently any examples / thoughts on how to deal with file extraction / unpacking upon submission? An example of this would be an extractor such as the EmlParser finding an attachment and returning that file somehow (maybe in the report base64'd, or a url link to a filestore associated with Cortex). Other examples are Cuckoo returning a new file that has been dumped as an observable - how should these files be returned?

If analyzers are able to return extracted files, this could then lead to recursion of extraction. For example a very simple zip extractor could extract files, detect their type and resubmit to those particular analyzers automatically. Going along with the EmlParser example: Being able to automatically run IP analyzers against any IP's found in the eml. And the same with Cuckoo.

Has this already been considered? If so, what's the status? TIA!

@nadouani
Copy link
Contributor

Hello, this is in fact something not yet available but will be considered soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants