# US 2021/0344513 A1 · Method and system for handling dynamic cybersecurity posture of a v2x entity

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

- Number: US 2021/0344513 A1
- Document ID: US20210344513A1
- Status: Published application
- Kind: A1
- Application number: 16/861,936
- Filed: 2020-04-29
- Published: 2021-11-04
- Earliest claimed: 2020-04-29
- Assignees: BlackBerry Limited
- Applicants: BlackBerry Limited
- Inventors: Nicholas James Russell; Stephen John Barrett; Michaela Vanderveen
- Web page: https://patentgrep.com/patent/US20210344513A1

## CPC

- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/3247: {involving digital signatures}
- H04L 63/105: {Multiple levels of security}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W 12/08: Access security
- H04W 12/12: Detection or prevention of fraud
- 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 2209/42: Anonymization, e.g. involving pseudonyms
- H04L 2209/80: Wireless
- H04L 2209/84: Vehicles
- 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 method at a network element, the method including receiving at least one message at the network element, the at least one message being one or both of: an update status information message from an updates server; and an anomaly detection status information message from anomaly detection server; determining, based on the receiving the at least one message, a dynamic cybersecurity posture indication for an intelligent transportation system entity; and providing the dynamic cybersecurity posture indication for the intelligent transportation system entity to an Enrolment Authority, wherein the dynamic cybersecurity posture indication can be included in a certificate relating to the intelligent transportation system entity.

## Claims

### Claim 1

A method at a network element, the method comprising:
receiving at least one message at the network element, the at least one message being one or both of:
an update status information message from an updates server; and
an anomaly detection status information message from an anomaly detection server;
determining, based on the receiving the at least one message, a dynamic cybersecurity posture indication for an intelligent transportation system entity; and
providing the dynamic cybersecurity posture indication for the intelligent transportation system entity to an Enrolment Authority,
wherein the dynamic cybersecurity posture indication can be included in a certificate relating to the intelligent transportation system entity.

### Claim 2 (depends on 1)

The method of claim 1, wherein the receiving the at least one message is based on a status request being sent to at least one of the updates server and the anomaly detection server.

### Claim 3 (depends on 1)

The method of claim 1, wherein the network entity further:
receives a cybersecurity posture determination request from the Enrolment Authority, the cybersecurity posture determination request containing cybersecurity data about the intelligent transportation system entity; and
using the cybersecurity data about the intelligent transportation system entity when determining the dynamic cybersecurity posture indication for the intelligent transportation system entity.

### Claim 4 (depends on 1)

The method of claim 1, wherein the dynamic cybersecurity posture indication is one of:
a dynamic cybersecurity posture information;
an indication that no dynamic cybersecurity posture information can be provided;
an indication that a dynamic cybersecurity posture is too low for the intelligent transportation system.

### Claim 5 (depends on 4)

The method of claim 4, wherein the dynamic cybersecurity posture information is one or more of: a timestamp field providing information on when the intelligent transportation system entity was last audited as being cybersecure; a timestamp field providing information a last connection date to the updates server; a timestamp field providing information on when the intelligent transportation system entity last connected to an anomaly detection server; an indication of known vulnerabilities that the intelligent transportation system entity has mitigated against; a cybersecurity posture level; a hardware version or build for the intelligent transportation system entity; a software version or build for the intelligent transportation system entity; a cybersecurity posture score; and a vulnerability score.

### Claim 6 (depends on 4)

The method of claim 4, wherein the indication that no dynamic cybersecurity posture information can be provided comprises an information element or a field within an information element.

### Claim 7 (depends on 4)

The method of claim 4, wherein the indication that a dynamic cybersecurity posture is too low for the intelligent transportation system comprises an information element or a field within an information element.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
receiving an information message at the network element, the information message being from one of the updates server and the anomaly detection server indicating that an event has occurred for the intelligent transportation system entity; and
based on the receiving the information message, sending a Certificate revocation list addition request to a certificate authority for the intelligent transportation system entity.

### Claim 9 (depends on 8)

The method of claim 8, wherein the network entity, prior to sending the certificate revocation list addition request, determines one or more identifiers for the intelligent transportation system entity based on a client identifier received in the information message.

### Claim 10 (depends on 9)

The method of claim 9, wherein the one or more identifiers is a canonical identifier for the intelligent transportation system entity.

### Claim 11

A network element comprising:
a processor; and
a communications subsystem,
wherein the network element is configured to:
receive at least one message at the network element, the at least one message being one or both of:
an update status information message from an updates server; and
an anomaly detection status information message from anomaly detection server;
determine, based on the receipt the at least one message, a dynamic cybersecurity posture indication for an intelligent transportation system entity; and
provide the dynamic cybersecurity posture indication for the intelligent transportation system entity to an Enrolment Authority,
wherein the dynamic cybersecurity posture indication can be included in a certificate relating to the intelligent transportation system entity.

### Claim 12 (depends on 11)

The network element of claim 11, wherein the network element is configured to receive the at least one message based on a status request being sent to at least one of the updates server and the anomaly detection server.

### Claim 13 (depends on 11)

The network element of claim 11, wherein the network entity is further configured to:
receive a cybersecurity posture determination request from the Enrolment Authority, the cybersecurity posture determination request containing cybersecurity data about the intelligent transportation system entity; and
use the cybersecurity data about the intelligent transportation system entity when determining the dynamic cybersecurity posture indication for the intelligent transportation system entity.

### Claim 14 (depends on 11)

The network element of claim 11, wherein the dynamic cybersecurity posture indication is one of:
a dynamic cybersecurity posture information;
an indication that no dynamic cybersecurity posture information can be provided;
an indication that a dynamic cybersecurity posture is too low for the intelligent transportation system.

### Claim 15 (depends on 14)

The network element of claim 14, wherein the dynamic cybersecurity posture information is one or more of: a timestamp field providing information on when the intelligent transportation system entity was last audited as being cybersecure; a timestamp field providing information a last connection date to the updates server; a timestamp field providing information on when the intelligent transportation system entity last connected to an anomaly detection server; an indication of known vulnerabilities that the intelligent transportation system entity has mitigated against; a cybersecurity posture level; a hardware version or build for the intelligent transportation system entity; a software version or build for the intelligent transportation system entity; a cybersecurity posture score; and a vulnerability score.

### Claim 16 (depends on 14)

The network element of claim 14, wherein the indication that no dynamic cybersecurity posture information can be provided comprises an information element or a field within an information element.

### Claim 17 (depends on 14)

The network element of claim 14, wherein the indication that a dynamic cybersecurity posture is too low for the intelligent transportation system comprises an information element or a field within an information element.

### Claim 18 (depends on 11)

The network element of claim 11, wherein the network element is further configured to:
receive an information message at the network element, the information message being from one of the updates server and the anomaly detection server indicating that an event has occurred for the intelligent transportation system entity; and
based on the receipt of the information message, send a Certificate revocation list addition request to a certificate authority for the intelligent transportation system entity.

### Claim 19 (depends on 18)

The network element of claim 18, wherein the network entity, prior to sending the certificate revocation list addition request, is configured to determine one or more identifiers for the intelligent transportation system entity based on a client identifier received in the information message.

### Claim 20 (depends on 19)

The network element of claim 19, wherein the one or more identifiers is a canonical identifier for the intelligent transportation system entity.

### Claim 21

A computer readable medium for storing instruction code which, when executed by a processor of a network element cause the network element to:
receive at least one message at the network element, the at least one message being one or both of:
an update status information message from an updates server; and
an anomaly detection status information message from anomaly detection server;
determine, based on the receipt the at least one message, a dynamic cybersecurity posture indication for an intelligent transportation system entity; and
provide the dynamic cybersecurity posture indication for the intelligent transportation system entity to an Enrolment Authority,
wherein the dynamic cybersecurity posture indication can be included in a certificate relating to the intelligent transportation system entity.
