Some use cases¶
As a framework, IVRE has several possible use cases. Of course, you probably want to use only parts of what IVRE can do.
Your own Shodan / ZoomEye / Censys / Binaryedgeio / whatever¶
You can use IVRE as a private (or even public, if you want) alternative to Shodan (or any other similar service).
The main difference with public services is that you will have the control of your data. You can scan whatever you want (your private networks, public networks, a specific country or Autonomous System, the whole Internet, etc.), for any port or protocol. You can run any query on your data; no-one has to know what you are really looking for.
Of course, this require more work than just using an existing public service, but the benefits are huge!
IVRE does not come with a scanner, and takes advantage of Nmap, Masscan and Zgrab / Zgrab2. Depending on your use case, you can choose one
or use both (IVRE will happily merge the results for you). Remember to
-oX option (which works with both Nmap and Masscan) or
-o for Zgrab2, as IVRE needs the XML output file for Nmap and
Masscan, and JSON for Zgrab2.
You can use
ivre runscansagent or
ivre runscansagentdb to run Nmap scans against wide targets (more)
You will then store the results from the XML or JSON output files into
IVRE database using
See IVRE with Kibana if you want to use Kibana to explore your scan results.
Your own Passive DNS service¶
Passive DNS services log DNS answers into a database and let you run queries against them.
They can be queried using
ivre iphost CLI tool, as in the
following example (the results come from a PCAP file used in IVRE’s
$ ivre iphost ipv4.icanhazip.com ipv4.icanhazip.com A 126.96.36.199 (188.8.131.52:53, 1 time, 2014-01-02 09:37:57.197000 - 2014-01-02 09:37:57.197000) ipv4.icanhazip.com A 184.108.40.206 (220.127.116.11:53, 1 time, 2014-01-02 09:37:57.197000 - 2014-01-02 09:37:57.197000) ipv4.icanhazip.com A 18.104.22.168 (22.214.171.124:53, 1 time, 2014-01-02 09:37:57.197000 - 2014-01-02 09:37:57.197000) ipv4.icanhazip.com A 126.96.36.199 (188.8.131.52:53, 1 time, 2014-01-02 09:37:57.197000 - 2014-01-02 09:37:57.197000) $ ivre iphost 184.108.40.206 ipv4.icanhazip.com A 220.127.116.11 (18.104.22.168:53, 1 time, 2014-01-02 09:37:57.197000 - 2014-01-02 09:37:57.197000) ipv4.icanhazip.com A 22.214.171.124 (126.96.36.199:53, 1 time, 2014-01-02 09:37:57.197000 - 2014-01-02 09:37:57.197000)
To see an interactive session of IVRE using passive data (including DNS answers), have a look at Passive network analysis.
Yeti is a platform meant to organize observables, indicators of compromise, TTPs, and knowledge on threats in a single, unified repository.
It comes with an “analytics” plugin that uses IVRE’s data to create links between IP addresses, hostnames, certificates, etc.
To learn more about this plugin, have a look at its documentation.
Cortex is a tool to analyze observables for SOCs, CSIRTs and security researchers; it integrates well with TheHive.
It comes with an “Analyzer” that uses IVRE’s data to report intelligence about Autonomous Systems, certificates, domain and host names, IP addresses, networks, open ports, etc.
To learn more about this analyzer, have a look at its documentation.
Blog posts and other resources¶
The author’s blog has some IVRE-related blog posts that might be useful.
Here is a list of other blog posts about or around IVRE:
Scan the hosts that hit your honeypots, and exploit the results!
Scanning SAP Services:
IVRE tests & reviews: