# US 2022/0366032 A1 · System and method for controlling access to an in-vehicle communication network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0366032 A1
- Document ID: US20220366032A1
- Status: Published application
- Kind: A1
- Application number: 17/869,792
- Filed: 2022-07-21
- Published: 2022-11-17
- Earliest claimed: 2015-09-25
- Assignees: Argus Cyber Securlty Ltd.
- Applicants: Argus Cyber Securlty Ltd.
- Inventors: Ofer BEN-NOON; Yaron Galula; Oron Lavi
- Web page: https://patentgrep.com/patent/US20220366032A1

## CPC

- G06F 21/35: communicating wirelessly
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- H04W 12/069: using certificates or pre-shared keys
- G06F 21/1014: {to tokens}
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 2212/178: Electronic token or RFID
- G06F 2221/2137: Time limited access, e.g. to a computer or data
- H04L 2209/84: Vehicles
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A system or method may include an in-vehicle network including an interface port for connecting an external device to the in-vehicle network; and a security unit connected to the in-vehicle network, the security unit adapted to enable an external device to communicate with the in-vehicle network, over the interface port, based on a security token received from the external device. A system or method may, based on a token, prevent an external device from at least one of: communicating with a selected set of components on in an in-vehicle network, communicating with a selected set of network segments in the in-vehicle network and performing a selected set of operations.

## Claims

### Claim 1

A system comprising:
an in-vehicle communication network included in a vehicle and electrically connected to a physical interface port for connecting an external device to the in-vehicle communication network, wherein the external device is adapted to physically connect to the physical interface port and to exchange data with the in-vehicle communication network, via the physical interface port; and
a security unit including a memory and a controller physically installed between the physical interface and the in-vehicle communication network and adapted, based on a security code received from the external device, to:
select at least one of: a set of components connected to the in-vehicle communication network, and a set of segments of the in-vehicle communication network; and
prevent the external device from communicating with at least one of: the selected set of components and the selected set of segments,
wherein the security code is generated based on an interaction with a user.

### Claim 2 (depends on 1)

The system of claim 1, wherein the security unit is adapted to validate the security code based on a unique attribute of the vehicle.

### Claim 3 (depends on 1)

The system of claim 1, comprising a server, wherein the server is adapted to:
receive information recorded by the security unit; and
perform at least one of:
generate a history log of maintenance service of the vehicle,
identify unauthorized access to the in-vehicle network,
identify malicious activity on the in-vehicle network, and
generate insights based on the recorded data.

### Claim 4 (depends on 1)

The system of claim 1, wherein the security unit is adapted to:
share a secret with a generator of the security code; and
validate the security code based on the shared secret.

### Claim 5 (depends on 1)

The system of claim 1, wherein the security unit is adapted to use the same security code a predefined number of times.

### Claim 6 (depends on 1)

The system of claim 1, wherein the security unit is adapted to prevent communication over the interface port based on at least one of: a predefined time interval and an event.

### Claim 7 (depends on 1)

The system of claim 1, wherein the security code is provided to the security unit by one of: a hardware component directly connected to the interface port and an external network.

### Claim 8 (depends on 1)

The system of claim 1 wherein the security code is a vehicle-specific code generated or provided by one of: a user associated with the vehicle and a server.

### Claim 9 (depends on 1)

The system of claim 1 wherein the security code includes at least two of:
a unique identification of the security code, an identification of the vehicle, a duration value, a reuse value, an identification of an event, an identification of nodes connected to the in-vehicle network, an indication of an operation, a context, and vehicle-specific identification.

### Claim 10 (depends on 1)

The system of claim 1, wherein the security unit is adapted to prevent communication over the interface port based on a context of the vehicle.

### Claim 11 (depends on 1)

The system of claim 1 wherein the security code is a vehicle-specific code generated based on an attribute of the vehicle, and wherein the vehicle-specific code is validated, by the security unit, based on the attribute of the vehicle.

### Claim 12 (depends on 1)

The system of claim 1, wherein the security unit is adapted to record information related to a communication with the external device.

### Claim 13

A method comprising:
receiving, by a security unit including a memory and a controller, from an external device, a code including digital information, wherein the security unit is physically installed between the physical interface and an in-vehicle communication network included in a vehicle, and wherein the external device is adapted to exchange data with the in-vehicle communication network, via a physical interface port;
selecting, by the security unit and based the digital information, at least one of: a set of components connected to the in-vehicle communication network, and a set of segments of the in-vehicle communication network; and
preventing the external device from communicating with at least one of: the selected set of components and the selected set of segments,
wherein the security code is generated based on an interaction with a user.

### Claim 14 (depends on 13)

The method of claim 13, comprising recording information related to a communication with the external device.

### Claim 15 (depends on 13)

The method of claim 13, comprising validating the security code, by the security unit, based on a unique attribute of the vehicle.

### Claim 16 (depends on 13)

The method of claim 13, comprising:
receiving, by a server, information recorded by the security unit; and
performing, by the server, at least one of:
generating a history log of maintenance service of the vehicle,
identifying unauthorized access to the in-vehicle network,
identifying malicious activity on the in-vehicle network, and
generating insights based on the recorded data.

### Claim 17 (depends on 13)

The method of claim 13, comprising reusing the same security code according to one of:
a predefined number of time, a predefined time interval and an event.

### Claim 18 (depends on 13)

The method of claim 13, comprising preventing communication over the interface port based on a context of the vehicle.

### Claim 19 (depends on 13)

The method of claim 13, comprising validating the security code based on cryptographic material associated with the security code.

### Claim 20 (depends on 13)

The method of claim 13, wherein the security code includes at least two of:
a unique identification of the security code, an identification of the vehicle, a duration value, a reuse value, an identification of an event, an identification of nodes connected to the in-vehicle network, an indication of an operation, a context, and vehicle-specific identification.
