Draft: Added EyeWitness

[cyberamt]

EyeWitness is a software that creates screenshots of web applications and can display simple response headers.

This pull request adds EyeWitness as an extra module to artemis. Since EyeWitness has a GPL 3.0 license, I did not put the pull request in the main Artemis repository.

Important: This pull-request is to be understood as a draft, the functionality to display images in the frontend of Artemis is not fully implemented.

@kazet

I would like to ask what you think is the easiest / best way to save images created by EyeWitness in the database and display them later in the frontend. Do you have any tips for me? I will then adapt the code accordingly to reflect this functionality. EyeWitness currently generates images, but these are not saved anywhere and cannot be called up.

[kazet]

Hello,

What about adding a view with domains tree? So that you can browse identified assets, some metadata and screenshot? This will allow us to move in the direction when Artemis doesn't just perform a scan, but continuously monitors your assets.

What about using a software we can use in the main repository (e.g. chromium is able to make screenshots)?

[cyberamt]

Under the hood, EyeWitness uses Selenium to access websites and take screenshots. You could of course reprogram this functionality, but I thought it would be nice to have some settings etc. at hand. If you want I can also close this merge request and try to implement it in the main repo. The advantage here is of course that it works, EyeWitness is stable and you don't have to reinvent the wheel twice.

[kazet]

Hello,

For chromium, you can perform a screenshot using chromium --headless --screenshot https://example.com . If you would prefer to introduce EyeWitness due to other features, could you describe them? If there are significant benefits of using EyeWitness, what about having a generic "asset map" functionality in the main repo and providing EyeWitness screenshots and other metadata as a separate module?