Thecurrent version of Maltegoisvisibleinthetitlebar:
Version 4.1.15 brings with it a rework of the graph export features in the form ofupdatedCSVand Excelfilestructures,aswell asgraphexporttoXMLintheyEd and Gephi GraphML formats (more on this below and also on our documentationdocs.maltego.com.)
We have also worked on fixing bugs that have been reported by you such as deadlocks when reaching 10,000 entities in CE or Classic. This ensures smooth use of Maltego without roadblocks in between your important investigation. Overall, the update entails the following changes and bug fixes:
NEW FEATURE OVERVIEW
Export Graph to Table
During your investigations, you might want to export graphs to a tabular format forusein other software, or toincorporatein a report. The newexport options give you a bit more flexibility in how thegraphdata is represented in these tables.
Let’s create a simple graph to export:
As before, the Graph Export Wizardallows you to choose whether you want to export the whole graph or just a selection.Depending on what data youchoose to include in the export, you might end up generating duplicate rows. Removetheseduplicatesautomatically by checking theRemove duplicate rowsoption.
When choosing the exportdetails, there are two main options:
Export a table containing theSource andTargetEntitiesvalue onlyor
Export a table withAllProperty Values.
When you want to export all the property values, you can choosethat theyareGrouped by Entity typewith blank lines separating them, oras anEntity property flat map.
When you export the properties,you also get a list of the links in the graph, and there is an option to export that to aSeparate Link Fileinstead.
Exporting Source and Target Entities value only
For the above example graph,exporting only the source and target entities will producethe following result:
ExportingAll Property Values, Grouped by Entity type
Exportingthe entitieswith their properties, grouped by type, produces the table below.
The export also includes a list of the links, using the ‘EntityID’ reference tolinktwo entities. These can be in a separate file or at the bottom of the list of entities as in this example:
Data is grouped into two header rows and multiple property value rows.
The first row(1)includes the entity type and display values of the properties
The second row(2)contains the property name
The remainingrows(3)includethe property values
Exporting All Property Valuesas a flat map
Exporting the entities and their properties as a flat table produces a file like the one below. Noticethatthere is only one header-row, and thatproperties are only populated where relevant in an entity.As an example, only the Website entity has avalue for the‘ports’ property.
Export Graph as XML
There are three GraphML formats to which you can export:
one used by Maltego,
one by yEd and
another by Gephi.
Please take note:
Unfortunately, the GraphML format is not standardised, with different applications using the format in a different way. There is no agreed way to store metadata within the XML file, and not even whetherthe y-axis runs from the top to the bottom, or the other way around.Therefore,more export formats with the same extensionmustbe supported.
The Save dialog presents the two new export formats along with the existing Maltego GraphML XML format. There is also a checkbox to select whether you want to export only the selected entities.
Let’s import theGraphML exports into applications thatsupporttheseformats.
This is what the graph looks like in yEd:
And after a bit of tweaking on how it is rendered, this is what the same graph looks like in Gephi:
We would like to thank you all for your feedback and unwavering support. We are happy to incorporate it in our updates and will continue to do so in the future.