You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we add an option of adding more features to the JSON file. Right now i see the Source, Destination, Protocol, SrcPort, DestPort. Other options can be details about the packet itself (Time, Sequence Number, Flags etc..). I am trying to build a graph in neo4j.
I currently am able to create a graph with the code below
WITH "file:///home/xxx/dump/output.json" AS url
CALL apoc.load.json(url)
YIELD value AS NetworkTraffic
UNWIND NetworkTraffic AS items
MERGE (s:Packet{id: items.Source, protocol:items.Prtocol, Srcport:Items.SrcPort})
MERGE (d:Packet{id: items.Destination, Destport:Items.DestPort})
CREATE (s) -[r:connects]->(d)
RETURN s,d,r;
The text was updated successfully, but these errors were encountered:
Hi @cgoat,
Thanks you for your suggestion.
I found it a usefull feature and it will be implemented in the next releases - so keep follow 😃
Cheers,
Oded.
Hi @cgoat
I have done a massive refactor to handle this feature.
Network Map user control now have a control describes the node details (open ports, DNS records, sessions count)
The exported files including a new file named "BruteShark Network Nodes Data.json" that holds all the nodes details.
Can we add an option of adding more features to the JSON file. Right now i see the Source, Destination, Protocol, SrcPort, DestPort. Other options can be details about the packet itself (Time, Sequence Number, Flags etc..). I am trying to build a graph in neo4j.
I currently am able to create a graph with the code below
WITH "file:///home/xxx/dump/output.json" AS url
CALL apoc.load.json(url)
YIELD value AS NetworkTraffic
UNWIND NetworkTraffic AS items
MERGE (s:Packet{id: items.Source, protocol:items.Prtocol, Srcport:Items.SrcPort})
MERGE (d:Packet{id: items.Destination, Destport:Items.DestPort})
CREATE (s) -[r:connects]->(d)
RETURN s,d,r;
The text was updated successfully, but these errors were encountered: