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

Reading in the data for analysis #3

Open
So-Cool opened this issue May 19, 2016 · 7 comments
Open

Reading in the data for analysis #3

So-Cool opened this issue May 19, 2016 · 7 comments
Assignees
Labels

Comments

@So-Cool
Copy link
Collaborator

So-Cool commented May 19, 2016

The simplest solution is reading in the JSONs placed in the /storage directory. At later stages it might be worth developing something more natural.

@So-Cool So-Cool self-assigned this May 19, 2016
@hgascon
Copy link
Member

hgascon commented May 19, 2016

@jbremer, besides JSONs in /storage, what are the other options implemented in cuckoo to store the analysis results? @So-Cool you can start by reading the JSON files but abstract this importing from the analysis so that data can be queried from several sources.

@jbremer
Copy link
Collaborator

jbremer commented May 19, 2016

If we fully integrate this new module later on then you simply get access to the full dictionary which is also saved as reports/report.json (and which you'll be using for now). So that way you replace the json.load(...) with a couple boilerplate lines of code from Cuckoo. Integration is pretty easy :-)

@hex1010
Copy link

hex1010 commented May 19, 2016

Are we assuming we will run this module only on report.json like if we want to work on mem dumps for feature extraction ?

@hgascon
Copy link
Member

hgascon commented May 19, 2016

@hex1010 What features would you extract from the memory dump?

@hex1010
Copy link

hex1010 commented May 19, 2016

DIff with baseline mem dump ? Does baseline feature support it at present ?

@jbremer
Copy link
Collaborator

jbremer commented May 19, 2016

Baseline feature only targets volatility output. Doing a complete (or partial) memory dump differential is out of scope here (but I don't think that's what you meant, right?)

@hex1010
Copy link

hex1010 commented May 19, 2016

I was thinking more on these lines http://www.dfrws.org/2012/proceedings/DFRWS2012-6.pdf but looks like its a stretch goal ..

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

No branches or pull requests

4 participants