Tell me more ×
IT Security Stack Exchange is a question and answer site for IT security professionals. It's 100% free, no registration required.
up vote 0 down vote favorite

Does anyone have any experience using Maltego in a team? Not being a server/client architecture I'm wondering how to best utilize this tool when you have a pentest team of four to five people.

Possible approaches:

  1. Everyone on the team has a license and shares the .mtgx file.
  2. Have Maltego installed on a server and RDP/VNC to this server.
  3. Have Maltego installed on one PC and connect a screen for the whole team to see, but not interact.

Pros/Cons:

  1. Everyone can interact well enough, but it is expensive and only one can make changes to the file at a time.
  2. It's cheap but only one can interact at same time (RDP). If VNC is used more people can interact, but VNC performance tend to be poor.
  3. Nice for team with one team leader, but we change team leader upon projects. Also many projects are small so multiple projects at the same time.

I must say I'm not satisfied with any of my approaches, can anyone think of (or already use) another approach to use Maltego in a team?

(P.S. I know this might be more of a discussion than a clear cut QA, but I did not know where else to turn to)

share|improve this question
This should actually be a really simple answer, but not really a security one. If you need the functionality for the entire team to be able to work concurrently, pay the licences. It should be relatively straightforward for you to agree who is responsible for the .mtgx file Alternatively, as individual performance should not be a bottleneck, your VNC option should also work just fine. – Rory Alsop♦ Feb 20 at 12:01

closed as off topic by Rory Alsop♦ Feb 20 at 12:01

Questions on IT Security Stack Exchange are expected to relate to IT security within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.