Receiver inputs are visible
Probes can reveal reachable aircraft receivers, viewers, and flight data messaging interfaces.
Industry blocklist
Aviation Systems blocklist
Review observed scanner sources around exposed receivers and flight data interfaces without changing the data exchange itself.
The coverage
What our sensors observed
Our sensors saw probes against aircraft tracking receivers, flight data services, and aviation messaging endpoints. The coverage centers on interfaces that collect or exchange operational data.
Why use this feed
Receivers and flight data services may need outside senders to keep data flowing. Review observed scanner sources at the firewall around a reachable input, viewer, or messaging edge, then check the rule against senders that are meant to connect. The feed gives operators addresses to review without changing the receiver or message exchange. Its scope is these exposed data interfaces, not every aviation system.
The challenges
Scanning can reveal a reachable service before an exploit attempt, whether a flaw is known or still undisclosed. Our sensors record sources doing that probing. A firewall rule using the feed can deny a listed source before its next connection reaches your service, without needing to recognize the exploit itself.
After the receiver responds
If an exposed receiver or message service has a weakness, traffic after the probe may try that flaw.
Before a remote site log
The feed can filter a listed source at a receiver edge before that station sees its first connection.
Edge enforcement
Defend your edge
The feed loads matching rules into your firewall. Listed sources are intercepted before crossing the edge; traffic with no match continues to your services.
Where this feed fits
Use the observed source list where your existing edge controls meet these reachable services.
Review scanner sources at the edge of an aircraft data receiver that can be reached from outside.
Apply the list around an exposed input service that accepts receiver data. Confirm which senders need to connect.
Use the feed where a flight data service ingests or shares messages. Keep approved data sources available.
Review the list around a reachable aviation messaging interface. Check exceptions with the people who manage the exchange.
Put the list in front of a public receiver viewer or dashboard. Viewer access may need different rules from receiver inputs.
Use one updated list at the firewalls for several exposed receiver sites. Keep site specific sender rules where needed.
Industry blocklist
Start blocking observed scanner sources.
Choose this industry, connect the feed to your firewall, and review access with the people who run each service.