Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cea-sec/ivre
Network recon framework. Build your own, self-hosted and fully-controlled alternatives to Shodan / ZoomEye / Censys and GreyNoise, run your Passive DNS service, build your taylor-made EASM tool, collect and analyse network intelligence from your sensors, and much more! Uses Nmap, Masscan, Zeek, p0f, ProjectDiscovery tools, etc.
https://github.com/cea-sec/ivre
bro easm external-attack-surface-management hacktoberfest masscan network network-discovery network-recon network-reconnaissance network-security nmap nmap-parser nmap-results-analyse nmap-scripts osint projectdiscovery scan-ports scans security zeek
Last synced: 5 days ago
JSON representation
Network recon framework. Build your own, self-hosted and fully-controlled alternatives to Shodan / ZoomEye / Censys and GreyNoise, run your Passive DNS service, build your taylor-made EASM tool, collect and analyse network intelligence from your sensors, and much more! Uses Nmap, Masscan, Zeek, p0f, ProjectDiscovery tools, etc.
- Host: GitHub
- URL: https://github.com/cea-sec/ivre
- Owner: ivre
- License: gpl-3.0
- Created: 2014-09-12T13:34:56.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2024-10-25T19:46:59.000Z (17 days ago)
- Last Synced: 2024-10-29T11:13:53.488Z (13 days ago)
- Topics: bro, easm, external-attack-surface-management, hacktoberfest, masscan, network, network-discovery, network-recon, network-reconnaissance, network-security, nmap, nmap-parser, nmap-results-analyse, nmap-scripts, osint, projectdiscovery, scan-ports, scans, security, zeek
- Language: Python
- Homepage: https://ivre.rocks/
- Size: 28.4 MB
- Stars: 3,462
- Watchers: 170
- Forks: 638
- Open Issues: 50
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
[](https://gitter.im/ivre/ivre)
[](https://twitter.com/IvreRocks)
[](https://infosec.exchange/@ivre)
[](https://github.com/ivre/ivre)
[](https://pypi.org/project/ivre/)
[](https://hub.docker.com/u/ivre/)
[](https://github.com/ivre/ivre/actions/workflows/mongodb.yml/?branch=master)
[](https://github.com/ivre/ivre/actions/workflows/elastic.yml/?branch=master)
[](https://github.com/ivre/ivre/actions/workflows/postgres.yml/?branch=master)
[](https://github.com/ivre/ivre/actions/workflows/tinydb.yml/?branch=master)
[](https://github.com/ivre/ivre/actions/workflows/sqlite.yml/?branch=master)
[](https://github.com/ivre/ivre/actions/workflows/maxmind.yml/?branch=master)
[](https://github.com/ivre/ivre/actions/linting/mongodb.yml/?branch=master)
[](https://doc.ivre.rocks/en/latest/?badge=latest)
# IVRE #
IVRE
(Instrument de veille sur les réseaux extérieurs) or DRUNK (Dynamic
Recon of UNKnown networks) is a network recon framework, including
tools for passive and active recon. IVRE can use data from:
- Passive tools:
- [Zeek](https://zeek.org/)
- [Argus](http://qosient.com/argus/)
- [Nfdump](https://github.com/phaag/nfdump)
- [p0f](https://lcamtuf.coredump.cx/p0f3/)
- [airodump-ng](https://www.aircrack-ng.org/)
- Active tools:
- [Nmap](https://nmap.org/)
- [Masscan](https://github.com/robertdavidgraham/masscan)
- [ZGrab2](https://github.com/zmap/zgrab2)
- [ZDNS](https://github.com/zmap/zdns)
- [Nuclei](https://nuclei.projectdiscovery.io/)
- [httpx](https://github.com/projectdiscovery/httpx)
- [dnsx](https://github.com/projectdiscovery/dnsx)
- [tlsx](https://github.com/projectdiscovery/tlsx)
- [Dismap](https://github.com/zhzyker/dismap/)
The advertising slogans are:
- (in French): IVRE, il scanne Internet.
- (in English): Know the networks, get DRUNK!
- (in Latin): Nunc est bibendum.
The names IVRE and DRUNK have been chosen as a tribute to "Le
Taullier".
## Overview ##
You can have a look at the [project homepage](https://ivre.rocks/),
the
**[screenshot gallery](https://doc.ivre.rocks/en/latest/overview/screenshots.html)**,
and the
[quick video introduction](https://www.youtube.com/watch?v=GBu5QMq6ewY)
for an overview of the Web interface.
We have a **demonstration instance**, just [contact us](#contact) to
get an access.
A few
**[blog posts](http://pierre.droids-corp.org/blog/html/tags/ivre.html)**
have been written to show some features of IVRE.
## Documentation ##
[IVRE's documentation](https://doc.ivre.rocks/) is hosted by Read The
Docs, based on files from the [doc/](doc/) directory of the
repository.
On an IVRE web server, the `doc/*` files are available, rendered,
under `/doc/`.
On a system with IVRE installed, you can use a `--help` option with
most IVRE CLI tools, and `help(ivre.module)` with most IVRE Python
sub-modules.
## License ##
IVRE is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
IVRE is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
[along with IVRE](doc/license.rst). If not, see
[the gnu.org web site](http://www.gnu.org/licenses/).
## Support ##
Try `--help` for the CLI tools, `help()` under Python and the "HELP"
button in the web interface.
Have a look at the
[FAQ](https://doc.ivre.rocks/en/latest/overview/faq.html)!
Feel free to contact the author and offer him a beer if you need help!
If you don't like beer, a good scotch or any other good alcoholic
beverage will do (it is the author's unalienable right to decide
whether a beverage is good or not).
## Contributing ##
Code contributions (pull-requests) are of course welcome!
The project needs scan results and capture files that can be provided
as examples. If you can contribute some samples, or if you want to
contribute some samples and would need some help to do so, or if you
can provide a server to run scans, please contact the author.
## Contact ##
For both support and contribution, the
[repository](https://github.com/ivre/ivre) on Github should be
used: feel free to create a new issue or a pull request!
You can also join the
[Gitter conversation](https://gitter.im/ivre/ivre) (that is the
preferred way to get in touch for questions), or use the e-mail `dev`
on the domain `ivre.rocks`.
## Talking about IVRE ##
### Research ###
If you are using IVRE in you research, please cite it as follows:
IVRE contributors. *IVRE, a network recon framework*.
[https://github.com/ivre/ivre](https://github.com/ivre/ivre),
2011-2022.
Here is the appropriate bibtex entry:
@MISC{ivre,
title = {{IVRE}, a network recon framework},
author={IVRE contributors},
url = {https://ivre.rocks/},
howpublished = {\url{https://github.com/ivre/ivre/}},
year = {2011--2022},
}
### Technical documents & blog posts ###
You can mention "IVRE, a network recon framework", together with the
project homepage, [https://ivre.rocks/](https://ivre.rocks/) and/or
the repository,
[https://github.com/ivre/ivre](https://github.com/ivre/ivre).
On twitter, you can follow and/or mention
[@IvreRocks](https://twitter.com/IvreRocks).