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

Potential Goals and milestones #49

Open
Evan-Sa opened this issue Feb 10, 2018 · 8 comments
Open

Potential Goals and milestones #49

Evan-Sa opened this issue Feb 10, 2018 · 8 comments

Comments

@Evan-Sa
Copy link
Collaborator

Evan-Sa commented Feb 10, 2018

I have a short list of ideas for 2018 that I was interested in for ssma development. I wanted to hear some feedback on these ideas before going forward.

Create on option that Prints detailed yara results that show what strings hit on the sample

Display Marco Offsets in the same way that oledump or oletools does

Develop a detailed display option that Dumps PE and PE sections info in the same way manalyze or Pecheck does (header, sections, etc...)

Develop a framework for static analysis

Create an output to CSV or PDF report option

write a simple cheat sheet the commands are little confusing (I've had feedback were people didn't realize you needed a period to do the directory scan or couldn't get the virus total option to work embarrassingly I still don't know how to use that feature.

@pielco11
Copy link
Collaborator

I've others ideas too, like setting up a remote-scan-service so that on could:

  • scan locally and share the reports with the server;
  • scan remotely and share the reports with the server.

So that one well be able to compare malware, download and/or upload reports, etc.
One could choose to share its stuff with everyone, with its team or with no one, also could choose to delete the malware after analysis or keep it available for everyone. In other words a complete control of the stuff. Others ideas are ready to come.

I have a server so that I could host it by myself.

@Evan-Sa
Copy link
Collaborator Author

Evan-Sa commented Feb 13, 2018

I think that would be a very valid use case. Most of analysis needs to stay local but having that DB resource for intelligence is very useful. I have not seen many great solutions would this be a username/password setup were people request access. Or your analysis gets a generated Id number and you can use that Id # with command options share publicly, share with certain users, delete the reporte

@pielco11
Copy link
Collaborator

Now as now my plans are these:

  • auth with pass (key) and user;
  • full control of sharing policy.

Users will sign up freely and will have unmetered scan requests, this could change during time based by load and in this case I could limit the number of requests per specific time range to not overload the server and to give everyone a stable service.

Passwords and usernames will be protected with salt, pepper, PBKDF2 and friends.

With "full control of sharing policy" I mean, but it's not limited to:

  • choose if one wants to share samples with no-one/a specific team/everyone;
  • choose if its (of the user) details will be available publicly, in this case "date" and "username" will be shared (e.g.: user: MarioBros date: dd-mm-yyyy sha512: 123...);
  • choose to share the reports with no-one/a specific team/everyone;
  • in any case I will not keep IPs or any identifiable information.

For example: a registered user could choose to upload a sample as anonymous, don't store the sample but share the report.

I'm widely open to every suggestion.

@pielco11
Copy link
Collaborator

@Evan-Sa I found this interesting repo that I forked (to add minor enhancements), check it out, I think that could be useful

@Evan-Sa
Copy link
Collaborator Author

Evan-Sa commented Mar 7, 2018

@pielco11 I downloaded your fork I found it pretty helpful. I would like to the see the same output in ssma when you sue the document flag. I am looking into a detailed display for the matching strings in yara signatures apparently such a thing is possible in the yara python library. if anyone has done this before please let me know

@pielco11
Copy link
Collaborator

pielco11 commented Mar 9, 2018

@Evan-Sa quicksand_lite is written is C, that could be not so easy to play with. Maybe using the compiled version and parse the output from quicksand to ssma. Plus quicksand drops embedded exes and objects, also these dropped elements could be analyzed with ssma for a deeper and more complete scan, imho.

The best thing to do would be creating a python lib for quicksand, but this will require lot of time and not basic knowledge.

@secrary
Copy link
Owner

secrary commented Mar 9, 2018

Guys, you are doing great job, but I'm sorry, don't have a time to help :(
I've add you to Collaborators

@Evan-Sa
Copy link
Collaborator Author

Evan-Sa commented Mar 31, 2018

@pielco11 I downloaded your fork I found it pretty helpful. I would like to the see the same output in ssma when you sue the document flag. I am looking into a detailed display for the matching strings in yara signatures apparently such a thing is possible in the yara python library. if anyone has done this before please let me know

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