Integrating Recorded Future With Maltego (Beta Program)
August 14, 2014 • Matt Kodama
Webinar: How to use Maltego for better insight into cyber threats. Watch now.
The after-action report from Black Hat 2014 …
Paterva’s Maltego product is a great “Swiss army knife” for researching IT infrastructure – whether the context is performing recon for pen-testing, reverse engineering malware, or gathering threat intelligence. We’ve had many requests for an integration that allows analysts to directly access Recorded Future using Maltego transforms.
We previewed our beta integration at Black Hat, and got very positive feedback. Now we’re announcing the kickoff of a beta program to meet this integration need.
A few important facts:
- This beta program is limited to customers of our Recorded Future Cyber product.
- The functional focus is researching malware and APT IOC’s and infrastructure.
- Beta testers should be comfortable using and debugging Maltego local transforms written in python.
People do use Maltego for many other problem sets, not just deciphering malware infrastructure. That’s a start. We see great potential in this integration, and look forward to expanding the functional scope in future.
With that out of the way, on to the fun stuff!
To make our integration as compact as humanly possible, we are leveraging the core Maltego entities (IPv4, Domain, URL, etc.) and the malware entities defined by the Malformity project (Hash, Filename, Registry Entry, etc.). No point in reinventing the wheel!
As an analyst, the Recorded Future transforms help you enrich and put context around the threat indicators you are investigating — and enable you to move smoothly between enrichment with the Recorded Future OSINT information and enrichment with other open or confidential data sources.
The remainder of this blog post is an example walkthrough to give you a feel for this integration in its current state. This example is anti-spam, but the analogy to cyber crime or APT defense is straightforward.
If you’re a Recorded Future Cyber customer – and a Maltego customer – and are interested in participating in this beta program, please contact us at support [at] recordedfuture [dot] com.
If you’re interested in this integration but have a different investigation use case in mind – or are just too busy to get involved in a beta program this summer – please watch our recent webinar to take a closer look.
For our example, let’s say you’re investigating an endpoint infection, apparently from a spammer email link. The starting point for your investigation is the suspicious link domain, and the downloaded file.
Let’s find out what open sources can tell you about this Domain and Filename. It turns out, an anti-spammer has already investigated this and published a great report on the Dynamoo blog.
We have a read — and find that this report lists a lot more IOCs and infrastructure related to this spammer group. Let’s pull that info into our investigation.
Dynamoo also suggests:
[blockquote]The 18.104.22.168/25 range has some questionable sites in it, and you might want to block the whole lot as a precaution. You should definitely block 22.214.171.124 though.[/blockquote]
Hmm, good point. Let’s open the aperture and look at the netblocks around these IPs. We use Maltego to get the netblocks and AS numbers 36352 and 16397.
Now we flip back to Recorded Future to ask, are there other reports of malicious activity related to these AS numbers? Survey says …
The broad stripe across the middle of our investigation graph is all the open source reports of suspicious activity from these two ASNs, and the IOCs called out in those reports. Looks like a couple of ASNs that we should block, or at a minimum put detective controls around.
In case you’re specifically interested in the data output from this example, we’ll end this example with a listing of the hashes and file names linked to these two abused AS numbers.