ARTEMIS is an open-source tool, that implements a defense approach against BGP prefix hijacking attacks. It is (a) based on accurate and fast detection operated by the AS itself, by leveraging the pervasiveness of publicly available BGP monitoring services, and it (b) enables flexible and fast mitigation of hijacking events. Compared to existing approaches/tools, ARTEMIS combines characteristics desirable to network operators such as comprehensiveness, accuracy, speed, privacy, and flexibility. With the ARTEMIS approach, prefix hijacking can be neutralized within a minute!
Table of Contents
- Getting Started
- Minimum Technical Requirements
- How to Install and Setup
- How to Run and Configure
- Development Team and Contact
- Authors and Contributors
- Side Projects
- Acknowledgements and Funding Sources
- Powered By
Depending on the preferences of the user, ARTEMIS can be used in 3 basic modes according to the combination of enabled micro-services in the user interface:
- Passive monitor (monitoring enabled)
- Passive detector (monitoring + detection enabled)
- Active joint detector and user-triggered mitigator (monitoring + detection + mitigation enabled)
Any of these combinations is valid. To start with, we recommend using mode (2). Mode (3) is under development (currently only a mitigation wrapper is offered).
You can read more about the ARTEMIS methodology, blog posts, presentations, publications and research experiments on the ARTEMIS webpage.
This repository contains the software of ARTEMIS as a tool. ARTEMIS can be run on a server/VM as a modular and extensible multi-container (microservice) application. It has been officially tested at AMS-IX, a major greek ISP, FORTH (a dual-homed edge academic network), and Internet2 (a major US R&E backbone network). Several other network operators use it either in production or in a testing environment.
For a detailed list of supported features please check the CHANGELOG file (sections: "Added"). The following main features are supported:
- Real-time monitoring of the changes in the BGP routes of the prefixes originated by the AS running ARTEMIS, via:
- Real-time detection and notifications of BGP prefix hijacking attacks/events of the following types (please refer to the attack taxonomy in our ARTEMIS IEEE/ACM ToN paper):
- exact-prefix, type 0/1, any data plane manipulation
- sub-prefix, any type (0/1/-), any data plane manipulation
- squatting attacks, type 0 (others are N/A), any data plane manipulation
- policy violations (route leaks) due to long paths towards no-export prefixes
- Automatic/custom tagging of detected BGP hijack events (ongoing, resolved, ignored, under mitigation, withdrawn, outdated and dormant).
- Manual or manually controlled mitigation of BGP prefix hijacking attacks.
- Comprehensive web-based User Interface (UI).
- Configuration file editable by the operator (directly or via the UI), containing information about: prefixes, ASNs, monitors and ARTEMIS rules ("ASX originates prefix P and advertises it to ASY").
- Support for both IPv4 and IPv6 prefixes (millions of routed prefixes depending on your resources).
- Support for both mobile and desktop environments (UI): sample screenshots.
- Support for
docker-compose(local single-server deployment) and
- Support for multiple modes of operation (passive monitor/detector, active mitigator, etc.).
- Support for historical BGP update replaying.
- Support for automated generation of the configuration file.
- Support for RPKI validation of hijacked prefixes.
- Compatibility with
- Modularity/extensibility by design.
- CI/CD (Travis CI, Codecov).
Please check this page.
ARTEMIS is built as a multi-container Docker application.
The following instructions will get you a containerized
copy of the ARTEMIS tool up and running on your local machine using the
For instructions on how to set up ARTEMIS
in a Kubernetes environment, please check the related docs page.
Minimum Technical Requirements
- CPU: 4 cores (note that needed CPU cores depend on the number of separate processes, e.g., detectors or database modules you spawn)
- RAM: 4+ GB (note that needed memory depends on the number of configured prefixes/rules/asns and load of incoming BGP updates, see here for more details)
- HDD: 50 GB (less may suffice, depending on the use case for storing BGP updates and hijack alerts)
- NETWORK: 1 public-facing network interface (optionally: one internal interface for connection with local route collectors)
- OS: Ubuntu Linux 16.04+ (other Linux distributions will work too)
- SW PACKAGES:
docker-composeshould be pre-installed (see instructions later) and
dockershould have sudo privileges, if only non-sudo user is allowed
Moreover, one may optionally configure firewall rules related to the server/VM. We recommend using ufw for this task. Please check the comments in the respective script we provide and set the corresponding <> fields in the file before running:
NOTE: For security reasons, we highly recommend protecting your machine with such rules. ARTEMIS tries to minimize external port exposure to minimize the attack surface on the system itself.
How to Install and Setup
To download and install the required software packages, please follow steps 1 through 6 described in this docs section.
To setup the tool (as well as https access to it via the web application), please follow steps 1 through 5 described in this docs section.
Note that specifically for testing purposes, we now support
VirtualBox VM automation;
please check out this docs page for simple instructions on how to spin up a fully functioning ARTEMIS VM, running all needed microservices, within a minute.
How to Run and Configure
docker-compose up -d
Please consult this docs section if you need to activate additional services.
Visit web UI and configure ARTEMIS:
By visiting the system page:
- edit the basic configuration file of ARTEMIS that serves as the ground truth for detecting BGP hijacks (consult this docs section first)
- control the monitoring, detection and mitigation modules.
Stop ARTEMIS (optional)
Note: We highly recommend going through the detailed docs instructions before using ARTEMIS for the first time. You can further use several other microservices orthogonal to ARTEMIS (like
routinator) by using the main ARTEMIS
docker-compose yaml plus the additional yamls:
docker-compose -f docker-compose.yaml -f docker-compose.<other_service>.yaml -... <up>/<down>/...
A running demo of ARTEMIS based on the configuration of our home institute (FORTH) can be found here. You can access the demo as a guest (non-admin) user by using the following credentials:
- username: "guest"
- password: "guest@artemis"
Please do not request new accounts on the demo portal. Use the given credentials to browse ARTEMIS as a guest user. In case you need admin access, simply clone ARTEMIS locally and use the given configuration file.
Please check this file.
Development Team and Contact
We follow a custom Agile approach for our development.
If you need to contact us about a bug, an issue or a question you have; you can reach us over at our Slack Community Channel. Otherwise, you can contact the ARTEMIS developers via e-mail using the ARTEMIS mailing list.
Please check this file.
Authors and Contributors
Please check this file.
The ARTEMIS software is open-sourced under the BSD-3 license. Please check the license file.
Note that all external dependencies are used in a way compatible with BSD-3 (that is, we conform to the compatibility rules of each and every dependency); the associated software packages and their respective licenses are documented in detail in this file, where we provide links to their homepages and licenses. Please let us know in case any of the information contained there is out-of-date to update it.
- Prototype software to enable auto-configuration and auto-mitigation in ARTEMIS using
Ansible: Github repo.
Acknowledgements and Funding Sources
This work is supported by the following funding sources on the European side (FORTH):
- European Research Council (ERC) grant agreement no. 790575 (PHILOS Project)
- European Research Council (ERC) grant agreement no. 338402 (NetVolution Project)
- RIPE NCC Community Projects Fund
The following funding sources supported the collaboration with CAIDA UCSD, on the US side:
- National Science Foundation (NSF) grants OAC-1848641 and CNS-1423659
- Department of Homeland Security (DHS) Science and Technology Directorate, Cyber Security Division (DHS S&T/CSD) via contract number HHSP233201600012C
- Comcast Innovation Fund
DISCLAIMER: We do not own these logo images. All links to the respective project pages from where the logos were downloaded are contained in this file, together with their respective licenses. The sole purpose of this section is to thank the open-source software projects that enabled ARTEMIS with their functionality and APIs, by making them as visible as possible. The list of project logos is not exhaustive. Image copyright is retained by the respective project's copyright owners.