Security architecture for the connected aircraft

Patent metadata

Field	Value
Publication number	US-10375087-B2
Application number	US-201414336230-A
Country	US
Kind code	B2
Filing date	Jul 21, 2014
Priority date	Jul 21, 2014
Publication date	Aug 6, 2019
Grant date	Aug 6, 2019

Abstract

Systems and methods of a security architecture for a connected aircraft are disclosed. In at least one embodiment, an avionics server comprises a plurality of device ports, wherein each of the plurality of device ports is coupled to a respective one of a plurality of device network interface cards and dedicated to a respective one of a plurality of avionics domains which corresponds to the respective device network interface card. Further, at least one processing device is configured to identify one or more signals from a respective user received at one or more of the plurality of device ports and to verify whether the user has access to the respective avionics domains that are dedicated to the one or more device ports over which the one or more signals are received.

First claim

What is claimed is:

1. An avionics server comprising:
a plurality of domains, wherein each one of the plurality of domains comprises a separate dedicated firewall restricting access to a plurality of applications and/or services on each one of the plurality of domains;
a plurality of device ports, wherein each one of the plurality of device ports is dedicated to a single respective one of the plurality of domains;
a plurality of device network interface cards, wherein each one of the plurality of device network interface cards is coupled to a single respective one of the plurality of device ports; and
at least one processing device configured to identify one or more signals from a respective user device received, via the respective plurality of device network interface cards, at one or more of the plurality of device ports and to verify, by the respective dedicated firewall, whether the user has access to the respective domains that are dedicated to the one or more device ports over which the one or more signals are received.

2. The avionics server of claim 1 , wherein the plurality of domains includes one or more of the following domains: an aircraft control domain, an airline information services domain, a passenger information and entertainment service domain, or a passenger owned devices domain.

3. The avionics server of claim 1 , wherein the at least one processing device is further configured to monitor the one or more signals for suspicious, unsafe, or malicious activity.

4. The avionics server of claim 1 , wherein the at least one processing device is further configured to compare the one or more signals being received from the user with one or more signals being received from a second user.

5. The avionics server of claim 1 , wherein the at least one processing device is further configured to:
compare the user with a list of prohibited users and deny the user access to the avionics server when the user is included in the list of prohibited users.

6. The avionics server of claim 1 , further comprising a datalink port and a datalink network interface card for receiving signals via a datalink and wherein the at least one processing device is configured to direct the signals from the datalink port to a corresponding domain.

7. The avionics server of claim 1 , wherein the avionics server includes the plurality of device network interface cards.

8. The avionics server of claim 1 , wherein the avionics server is an application computing platform including one or more virtual machines hosting the plurality of applications and/or services.

9. A method comprising:
receiving one or more signals from a device at one or more of a plurality of device ports, via a respective plurality of device network interface cards, wherein each one of the plurality of device ports is coupled to a single respective one of the plurality of device network interface cards, and wherein each one of the plurality of device ports is dedicated to a single respective one of a plurality of domains;
identifying the one or more device ports that are receiving the one or more signals from the device;
verifying, by a separate respective dedicated firewall on each one of the plurality of domains, whether the device has access to the respective one or more domains that are dedicated to the one or more identified device ports; and
forwarding the one or more signals to the one or more domains that the device has access to.

10. The method of claim 9 , wherein the plurality of domains include one or more of the following domains: an aircraft control domain, an airline information services domain, a passenger information and entertainment service domain, or a passenger owned devices domain.

11. The method of claim 9 , further comprising monitoring the one or more signals for suspicious, unsafe, or malicious activity.

12. The method of claim 9 , further comprising comparing the one or more signals being received by the device with one or more signals being received by a second device.

13. The method of claim 9 , further comprising comparing the device with a list of prohibited devices.

14. The method of claim 13 , further comprising denying the device access to the plurality of domains when the device is included in the list of prohibited devices.

15. A system comprising:
a plurality of device network interface cards; and
an avionics server comprising:
a plurality of domains, wherein each one of the plurality of domains comprises a separate dedicated firewall restricting access to a plurality of applications and/or services on each one of the plurality of domains; and
a plurality of device ports, wherein each one of the plurality of device ports is dedicated to a single respective one of the plurality of domains;

wherein each one of the plurality of device ports is coupled to a single respective one of the plurality of device network interface cards, which corresponds to the respective domain, and
wherein the avionics server is configured to identify one or more signals from a respective user device received, via the respective plurality of device network interface cards, at one or more of the plurality of device ports, and to verify, by the respective dedicated firewall, whether the user has access to the respective domains that are dedicated to the one or more device ports over which the one or more signals are received.

16. The system of claim 15 , wherein the plurality of domains includes one or more of the following domains: an aircraft control domain, an airline information services domain, a passenger information and entertainment service domain, or a passenger owned devices domain.

17. The system of claim 15 , wherein the avionics server is further configured to monitor the one or more signals for suspicious, unsafe, or malicious activity.

18. The system of claim 15 , wherein the avionics server is further configured to compare the one or more signals being received from the user with one or more signals being received from a second user.

19. The system of claim 15 , wherein the avionics server is further configured to compare the user with a list of prohibited users.

20. The system of claim 19 , wherein the avionics server is further configured to deny the user access to the avionics server when the user is included in the list of prohibited users.

Assignees

• Honeywell Int Inc

Inventors

• Kirk James C
• Johnson Daniel P
• Palovick Iii Joseph J
• Mann Dewey
• Gerlock Derick Lucas

Classifications

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• H04L63/1408

  by monitoring network traffic (monitoring network traffic per se H04L43/00) · CPC title

• H04L63/101 Primary

  Access control lists [ACL] · CPC title

• G06F2221/2113

  Multi-level security, e.g. mandatory access control · CPC title

• H04L63/1416 Primary

  Event detection, e.g. attack signature detection · CPC title