Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to not generate an origin hijack alert if the prefix has a valid ROA #595

Open
racompton opened this issue Apr 7, 2021 · 2 comments

Comments

@racompton
Copy link

It would be nice if in the config there was an option to not generate origin hijack alerts if Artemis sees a valid ROA for the prefix which has been sent by the validator.

@vkotronis
Copy link
Member

The logic of the hijack alerting is the following: "if there is a mismatch between the config file and the incoming BGP updates from external or other sources, then declare alert". We accompany such alerts with the ROA validation status; however, ROAs and alerts are complementary since the Source of Truth is always the config file info. In this feature request, you refer to automatically adding the RPKI ROA truth info to the config file so that no origin alerts are triggered if ROAs cover them, is that correct? Or checking also the ROA before triggering the alert, and if valid, do not trigger at all but silently continue?
In the end it comes down to auto-integrating RPKI information into the ARTEMIS ground truth, and keeping it up-to-date, right?

@racompton
Copy link
Author

I'm thinking more checking the ROA before triggering the alert and if valid, do not trigger at all but silently continue. Perhaps create a new tag for the alerts such as "RPKI valid" and apply this tag instead of "Ongoing".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants