The invention relates generally to computer networks, and more specifically, for securely updating computer configuration files of a specific automobile type and a specific automobile.
The automobile industry is undergoing tremendous changes, such as forms of mobile computing for different services. Some computing services concern the automobile (e.g., configuration files) while others concern individuals riding in the automobile (e.g., Spotify).
Network security for the services can be critical for the personal safety of drivers and passengers. For example, malicious actors can make configuration changes intentionally and non-malicious actors can make configuration changes unintentionally, that harmfully affect computer vision systems to misinterpret video feeds. In another example, an incorrect configuration file may be sent in error due to many different manufacturers of cars and different models by each manufacturer. These models may even be configured with respect to a particular region. Keeping configuration rules for network security and other aspects of the operation up to date on an automobile can thus be vulnerable to network transport.
What is needed is a robust technique for securely updating computer configuration files of a specific automobile type and a specific automobile.
To meet the above-described needs, methods, computer program products, and systems for securely updating computer configuration files of a specific automobile type and a specific automobile.
In one embodiment, a three-level configuration mechanism to configure/update the mass vehicles, is set forth, using a signed configuration mechanism certificate/signature/configuration to prevent tampering.
In another embodiment, configuration files and updates to configuration files from automobile manufacturer are stored in a database. Certificates are also stored for each individual automobile generated from a unique Vehicle Identification Number (VIN) of a specific automobile along with an IP associated with the specific automobile.
In yet another embodiment, a request to check for updated configuration files for a specific automobile and a specific automobile type is received in real-time over the data communication network. Comparing a checksum of received request against stored configuration file, checks for an update. If there is an update, a signature is generated using the certificate from the unique VIN number portion and the stored configuration file for encrypting the stored configuration file. The signature and stored configuration file is transmitted to the specific automobile for local configuration update.
Advantageously, computer devices for automobiles are improved with better security.
In the following drawings, like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.
Methods, computer program products, and systems for securely updating configuration files of a specific automobile type and a specific automobile. The following disclosure is limited only for the purpose of conciseness, as one of ordinary skill in the art will recognize additional embodiments given the ones described herein.
In one embodiment, the components of the system 100 are coupled in communication over a private network connected to a public network, such as the Internet. In another embodiment, system 100 is an isolated, private network, or alternatively, a set of geographically dispersed LANs. The components can be connected to the data communication system 199 via hard wire (e.g., automotive server 110). The components can also be connected via wireless networking (e.g., automobiles 140A-C). The data communication network 199 can be composed of any combination of hybrid networks, such as an SD-WAN, an SDN (Software Defined Network), WAN, a LAN, a WLAN, a Wi-Fi network, a cellular network (e.g., 3G, 4G, 5G or 6G), or a hybrid of different types of networks. Various data protocols can dictate format for the data packets. For example, Wi-Fi data packets can be formatted according to IEEE 802.11, IEEE 802, 11r, 802.11be, Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 and the like. Components can use IPV4 or Ipv6 address spaces.
One embodiment of the system 100 in operation is described in the following non-limiting example, as illustrated in
A three-level configuration mechanism configures and updates mass vehicles. A signed configuration mechanism of certificate, signature and configuration prevents tampering.
In one embodiment, the automobiles 140A-C are gas or electric-powered vehicles (e.g., car, truck, SUV, motorcycle, or scooter), driven by humans or computers, with a computer system that is integral to operation of the vehicle. A non-limiting example of manufacturers includes Ford, Chevrolet, Tesla, Jeep, Toyota and Honda. Vehicles may also be identified as part of a specific fleet with custom updates, such as a school bus fleet, a military fleet, a post office fleet, a rental fleet, a trucking company, or the like.
The automobile 140A (or any automobile) can pull configuration (with signature and certificate) from the automotive server 110, in one embodiment. The automotive server 110 can push configuration, in another embodiment. For security, the automotive server 110 uses private key to sign the configuration file, and the automobile 140A uses a certificate to verify the configuration file (to avoid the configuration file being tampered with). The configuration update occurs when the associated configuration has been updated on the automotive server 110. In one case, the automobile 140A periodically pushes signature/checksum to the automotive server 110, for comparing this signature/checksum with current configuration's signature/checksum. If changed, the automobile 140A proceeds to update its configuration.
An implementation of a three-level configuration includes a device level configuration, a device group and a profile. Device level configuration can include connection timeout/Update control/license. A device group can be used to group cars. The automobile 140A can be classified into a group, and car can be adjusted to other groups at any time (the cars at same group will have the same external interfaces, such as the same network interface), and device group has device level configuration, such as vlan/dns/route. Using configuration profile, each profile has a complete security configuration (as template), such as configure ips/ids/dlp/application control/firewall etc. Each device group can choose to apply a certain profile, and then the profile+device group+device configuration will be rendered into a complete configuration (file) for this device. In an embodiment, the complete configuration is stored as a unified configuration format, such as Json/xml.
The automobile 140A will periodically send its configuration file's checksum/signature to admin server, server will compare it with current checksum/signature to verify if it is changed, and update the configuration status.
When the automotive server 110 finds out configuration changed, it will set this configuration status as changed. The automobile 140A can query the configuration status, if configuration changed, it will pull the latest file from the automotive server 110.
For user device group to group automobiles, a automobile can be classified into a group and be adjusted to other groups at any time (the same group will have the same external interface, such as the same net card interface name), at device group, related configuration can be devised, such as vlan/dns/route.
Each configuration profile can be a complete configuration (template). It can configure security policy (ips/application control/dlp/anti-malware)/firewall, etc.). Each device group can choose to apply a certain profile, and then the profile render (rendering, mainly to replace the network interface called by the profile with its own specific device interface) into its own configuration (file); then mark the configuration file to be updated.
The automotive server 110 uses a certificate to encrypt/signature the configuration file, generate a signature, combine the configuration and signature and certificate into the configuration file. The automobile 140A uses the certificate to signature the configuration file and get the new signature, then compare it with the signature which recorded in the configuration file. If these two signatures are different, it means this configuration file was tampered, so the automobile 140A will not use this configuration. If these two signatures are equal, it is a reliable configuration and the automobile will configure according this configuration.
Finally, the automobile 140A configuration updates according to the configuration file, in an embodiment.
The automotive server 110 provides configuration updates for a variety of automobiles manufacturers (e.g., Tesla, Chevy, Harley Davidson) and specific models. The automobiles 140A-C can all be associated with the same automotive serve 110 or different ones. In operation, the automotive server 110 domain name and/or IP address is configured in the automobile 140A. The automotive server 110 can sign the configuration, the configuration and signature and certificate can then be combined into the configuration file.
The automobile 140A can be continuously connected to data service using cell data service. Alternatively, the automobile 140A can connect to nearby access points over wireless channels for uploading and downloading data from the data communication network. Each automobile 140A-C has a unique VIN for physical identification. The VIN can also be programmed digitally within the electronics system. Within the VIN, the first character can indicate where the automobile was build, the second and third characters can indicate the manufacturer, the fourth and eighth characters can indicate a portrait of the vehicle brand, engine size and type, the ninth character can indicate a security code, the tenth character can indicate a module year, the eleventh character can indicate which plant assembled the vehicle, and the last six characters can be a serial number of the vehicle. Thus, by parsing the VIN number, many aspects of automobiles can be determined when matching with a correct configuration file.
The automobile account module 210 stores certificates for each individual automobile generated from a unique VIN number portion of a specific automobile along with an IP associated with the specific automobile. This can be set up at manufacture or update later by an owner.
The automotive configuration database 220 stores configuration files and updates to configuration files from the automobile manufacturer server. In one case, automobile manufacturers have a direct relationship and releases updates through the automotive database 220, over trusted connections. In another case, third-party manufacturers can update individual components of configurations across different automobile types and modules, for example, for a braking system in common. In still another case, a third-party service collects or produces configuration updates to the automotive configuration database 220.
The configuration update module 230 receives, in real-time over the data communication network, a request to check for updated configuration files for a specific automobile and a specific automobile type. A checksum of received request is compared against stored configuration file to check for an update. If updated, a signature is generated using the certificate from the unique VIN number portion and the stored configuration file for encrypting the stored configuration file.
The network interface 240 transmits signature and stored configuration file to the specific automobile for local configuration update. A transmitter and antennae can interface with wireless channels while an Ethernet port, for example, can interface with wired channels.
At step 410, automobiles and automotive manufacturers are registered. For automobiles, storing certificates for each individual automobile generated from a unique VIN number portion of a specific automobile along with an IP associated with the specific automobile. For manufacturers, configuration files and updates to configuration files from automobile manufacturer. At step 420, automobile configurations files are securely updated, as described in more detail below in association with
Specifically, at step 510, a request to check for updated configuration files for a specific automobile and a specific automobile type is received. At step 520, a checksum of received request is compared against stored configuration file to check for an update. At step 530, if update, a signature is generated using the certificate from the unique VIN number portion and the stored configuration file for encrypting the stored configuration file. At step 540, signature and stored configuration file are transmitted to the specific automobile for local configuration update.
The computing device 600, of the present embodiment, includes a memory 610, a processor 620, a hard drive 630, and an I/O port 640. Each of the components is coupled for electronic communication via a bus 650. Communication can be digital and/or analog, and use any suitable protocol.
The memory 610 can be a storage device such as HDD, SDD, removable disk (e.g., SD card) and further comprises network access applications 612 and an operating system 614. Network access applications can include 612 a web browser, a mobile access application, an access application that uses networking, a remote access application executing locally, a network protocol access application, a network management access application, a network routing access applications, or the like.
The operating system 614 can be one of the Microsoft Windows® family of operating systems (e.g., Windows 98, 98, Me, Windows NT, Windows 2000, Windows XP, Windows XP x84 Edition, Windows Vista, Windows CE, Windows Mobile, Windows 7 or Windows 8), Linux, HP-UX, UNIX, Sun OS, Solaris, Mac OS X, Alpha OS, AIX, IRIX32, or IRIX84. Other operating systems may be used. Microsoft Windows is a trademark of Microsoft Corporation.
The processor 620 can be a network processor (e.g., optimized for IEEE 802.11), a general-purpose processor, an access application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a reduced instruction set controller (RISC) processor, an integrated circuit, or the like. Qualcomm Atheros, Broadcom Corporation, and Marvell Semiconductors manufacture processors that are optimized for IEEE 802.11 devices. The processor 620 can be single core, multiple core, or include more than one processing elements. The processor 620 can be disposed on silicon or any other suitable material. The processor 620 can receive and execute instructions and data stored in the memory 610 or the hard drive 630.
The storage device 630 can be any non-volatile type of storage such as a magnetic disc, EEPROM, Flash, or the like. The storage device 630 stores code and data for access applications.
The I/O port 640 further comprises a user interface 642 and a network interface 644. The user interface 642 can output to a display device and receive input from, for example, a keyboard. The network interface 644 connects to a medium such as Ethernet or Wi-Fi for data input and output. In one embodiment, the network interface 644 includes IEEE 802.11 antennae.
Many of the functionalities described herein can be implemented with computer software, computer hardware, or a combination.
Computer software products (e.g., non-transitory computer products storing source code) may be written in any of various suitable programming languages, such as C, C++, C#, Oracle® Java, Javascript, PHP, Python, Perl, Ruby, AJAX, and Adobe® Flash®. The computer software product may be an independent access point with data input and data display modules. Alternatively, the computer software products may be classes that are instantiated as distributed objects. The computer software products may also be component software such as Java Beans (from Sun Microsystems) or Enterprise Java Beans (EJB from Sun Microsystems).
Furthermore, the computer that is running the previously mentioned computer software may be connected to a network and may interface to other computers using this network. The network may be on an intranet or the Internet, among others. The network may be a wired network (e.g., using copper), telephone network, packet network, an optical network (e.g., using optical fiber), or a wireless network, or any combination of these. For example, data and other information may be passed between the computer and components (or steps) of a system of the invention using a wireless network using a protocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b, 802.11e, 802.11 g, 802.11i, 802.11n, and 802.ac, just to name a few examples). For example, signals from a computer may be transferred, at least in part, wirelessly to components or other computers.
In an embodiment, with a Web browser executing on a computer workstation system, a user accesses a system on the World Wide Web (WWW) through a network such as the Internet. The Web browser is used to download web pages or other content in various formats including HTML, XML, text, PDF, and postscript, and may be used to upload information to other parts of the system. The Web browser may use uniform resource identifiers (URLs) to identify resources on the Web and hypertext transfer protocol (HTTP) in transferring files on the Web.
The phrase network appliance generally refers to a specialized or dedicated device for use on a network in virtual or physical form. Some network appliances are implemented as general-purpose computers with appropriate software configured for the particular functions to be provided by the network appliance; others include custom hardware (e.g., one or more custom Application Specific Integrated Circuits (ASICs)). Examples of functionality that may be provided by a network appliance include, but is not limited to, layer 2/3 routing, content inspection, content filtering, firewall, traffic shaping, application control, Voice over Internet Protocol (VOIP) support, Virtual Private Networking (VPN), IP security (IPSec), Secure Sockets Layer (SSL), antivirus, intrusion detection, intrusion prevention, Web content filtering, spyware prevention and anti-spam. Examples of network appliances include, but are not limited to, network gateways and network security appliances (e.g., FORTIGATE family of network security appliances and FORTICARRIER family of consolidated security appliances), messaging security appliances (e.g., FORTIMAIL family of messaging security appliances), database security and/or compliance appliances (e.g., FORTIDB database security and compliance appliance), web application firewall appliances (e.g., FORTIWEB family of web application firewall appliances), application acceleration appliances, server load balancing appliances (e.g., FORTIBALANCER family of application delivery controllers), vulnerability management appliances (e.g., FORTISCAN family of vulnerability management appliances), configuration, provisioning, update and/or management appliances (e.g., FORTIMANAGER family of management appliances), logging, analyzing and/or reporting appliances (e.g., FORTIANALYZER family of network security reporting appliances), bypass appliances (e.g., FORTIBRIDGE family of bypass appliances), Domain Name Server (DNS) appliances (e.g., FORTIDNS family of DNS appliances), wireless security appliances (e.g., FORTI Wi-Fi family of wireless security gateways), FORIDDOS, wireless access point appliances (e.g., FORTIAP wireless access points), switches (e.g., FORTISWITCH family of switches) and IP-PBX phone system appliances (e.g., FORTIVOICE family of IP-PBX phone systems).
This description of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form described, and many modifications and variations are possible in light of the teaching above. The embodiments were chosen and described in order to best explain the principles of the invention and its practical access applications. This description will enable others skilled in the art to best utilize and practice the invention in various embodiments and with various modifications as are suited to a particular use. The scope of the invention is defined by the following claims.