# US 2019/0245867 A1 · Automotive ecu controller and data network having security features for protection from malware transmission

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

- Number: US 2019/0245867 A1
- Document ID: US20190245867A1
- Status: Published application
- Kind: A1
- Application number: 16/385,446
- Filed: 2019-04-16
- Published: 2019-08-08
- Earliest claimed: 2017-01-03
- Assignees: Karamba Security Ltd.
- Applicants: Karamba Security Ltd.
- Inventors: Tal Efraim Ben David; Assaf Harel; Amiram Dotan; David Barzilai
- Web page: https://patentgrep.com/patent/US20190245867A1

## CPC

- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- G06F 21/55: Detecting local intrusion or implementing counter-measures
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/105: {Multiple levels of security}
- H04L 63/14: {for detecting or protecting against malicious traffic}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04W 12/12: Detection or prevention of fraud
- H04W 12/128: Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware
- 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
- H04L 2012/40215: {Controller Area Network CAN}
- H04L 2012/40273: {the transportation system being a vehicle}
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

In one implementation, a method for providing security on controllers includes detecting, by a given controller, an attempted security attack on the given controller; in response to detecting the attempted attack, entering a safe mode of operation for the given controller in which at least one process performed by the given controller is restricted such that the at least one process is performed only when a current context of the controller matches a permitted context that is associated with the given controller; in response to detecting the attempted attack, transmitting a safe mode alert to one or more other controllers; and for at least one of the one or more other controllers, in response to receiving the safe mode alert, entering a safe mode of operation for the other controller.

## Claims

### Claim at position 1

1-19. (canceled)

### Claim 20

A security-enabled, self-aware ECU in a vehicle, comprising:
at least one processor configured to execute ECU software and security software; and
at least one memory storing the ECU software and the security software, wherein the security software includes instructions for performing operations including:
determining a current context of the ECU;
analyzing data communications received at the ECU, the analyzing including a determination of whether the data communications are permitted within the current context;
determining, based on the analyzed data communications, whether the ECU software is experiencing an external-based attack; and
reporting, to a resource external to the ECU, an indication that the ECU is experiencing the external-based attack.

### Claim 21 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the external-based attack is associated with a buffer space overflow event.

### Claim 22 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the external-based attack is associated with malware.

### Claim 23 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the reporting includes providing trace information associated with the external-based attack.

### Claim 24 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the reporting includes providing information identifying a code portion associated with the external-based attack.

### Claim 25 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the reporting includes providing a copy of malware associated with the external-based attack.

### Claim 26 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the reporting includes providing information identifying the current context of the ECU.

### Claim 27 (depends on 26)

The security-enabled, self-aware ECU of claim 26, wherein the current context of the ECU includes geographical location data.

### Claim 28 (depends on 26)

The security-enabled, self-aware ECU of claim 26, wherein the current context of the ECU includes data indicating a current operational state of the ECU.

### Claim 29 (depends on 20)

The security-enabled, self-aware ECU of claim 20, wherein the ECU is configured to perform the reporting to a reporting queue associated with the resource external to the ECU.

### Claim 30

A computer-implemented method for a security-enabled, self-aware ECU in a vehicle to determine and report its own security status, the method comprising:
executing ECU software locally on the ECU; and
executing security software locally on the ECU, the security software being configured to perform operations including:
determining a current context of the ECU;
analyzing data communications received at the ECU, the analyzing including a determination of whether the data communications are permitted within the current context;
determining, based on the analyzed data communications, whether the ECU software is experiencing an external-based attack; and
reporting, to a resource external to the ECU, an indication that the ECU is experiencing the external-based attack.

### Claim 31 (depends on 30)

The computer-implemented method of claim 30, wherein the external-based attack is associated with a buffer space overflow event.

### Claim 32 (depends on 30)

The computer-implemented method of claim 30, wherein the external-based attack is associated with malware.

### Claim 33 (depends on 30)

The computer-implemented method of claim 30, wherein the reporting includes providing trace information associated with the external-based attack.

### Claim 34 (depends on 30)

The computer-implemented method of claim 30, wherein the reporting includes providing information identifying a code portion associated with the external-based attack.

### Claim 35 (depends on 30)

The computer-implemented method of claim 30, wherein the reporting includes providing a copy of malware associated with the external-based attack.

### Claim 36 (depends on 30)

The computer-implemented method of claim 30, wherein the reporting includes providing information identifying the current context of the ECU.

### Claim 37 (depends on 36)

The computer-implemented method of claim 36, wherein the current context of the ECU includes geographical location data.

### Claim 38 (depends on 36)

The computer-implemented method of claim 36, wherein the current context of the ECU includes data indicating a current operational state of the ECU.

### Claim 39 (depends on 30)

The computer-implemented method of claim 30, wherein the ECU is configured to perform the reporting to a reporting queue associated with the resource external to the ECU.
