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

Filter out Intelsat satellite network plane wifi from Impossible Travel #1358

Open
wants to merge 1 commit into
base: release
Choose a base branch
from

Conversation

geoffg-sentry
Copy link
Contributor

@geoffg-sentry geoffg-sentry commented Sep 18, 2024

Background

Intelsat provides in-flight wifi for a number of airlines (American, Alaska, etc) among other mobile services but like any ASN provides geographic information for a fixed spot on the globe. This leads to false positives when persons using in-flight wifi have login activity shortly before or after a login from in-flight. An example:

  • Login from LAX airport before boarding a flight at 17:00
  • Login from Intelsat in-flight wifi at 17:30 tied to Tysons Landing, Virginia.

Changes

Adds a check on ipinfo_asn lookups and excludes Intelsat's ASN AS22351 from triggering the rule or being included in new_login_stats. Any additional satellite network ASNs identified can be added to the SATELLITE_NETWORK_ASNS constant.

Testing

  • New test for a true positive impossible travel event but from a IP in AS22351 results
  • make lint
  • pat test --filter RuleID=Standard.ImpossibleTravel.Login

Intelsat provides in-flight wifi for a number of airlines (American, Alaska, etc) but like any ASN provides geographic information for a fixed spot on the globe. This leads to false positives when persons using in-flight wifi have login activity shortly before or after a login from in-flight.
@geoffg-sentry geoffg-sentry requested a review from a team as a code owner September 18, 2024 16:20
@ben-githubs
Copy link
Contributor

Hi Geoff, thanks for submitting! I've been reviewing your PR and I'm wondering why the current rule code doesn't satisfy your situation...

It appears that Intelsat gets identified by IPinfo as a VPN, and therefore the current code would not use it for any distance calculations in further events. (It does generate an alert, but the alert is INFO level and auto-dismissed, so it shouldn't generate any noise. The reason we still generate an alert for VPNs is in case the VPN designation was a mistake - you'll still have a record of the alert and the event details, if you review your alert history.)

Please let me know if there's something I'm not seeing!

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

Successfully merging this pull request may close these issues.

2 participants