# US 2020/0351260 A1 · Method and system for application authenticity attestation

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

- Number: US 2020/0351260 A1
- Document ID: US20200351260A1
- Status: Published application
- Kind: A1
- Application number: 16/400,691
- Filed: 2019-05-01
- Published: 2020-11-05
- Earliest claimed: 2019-05-01
- Assignees: BlackBerry Limited
- Applicants: BlackBerry Limited
- Inventors: Johnathan White; Amit Ghosh
- Web page: https://patentgrep.com/patent/US20200351260A1

## CPC

- G06F 21/44: Program or device authentication
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- G06F 21/445: {by mutual authentication, e.g. between devices or programs}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0869: {involving random numbers or seeds}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3271: {using challenge-response}
- H04W 12/06: Authentication
- H04W 12/10: Integrity
- H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications
- G06F 2221/033: Test or assess software
- G06F 2221/2103: Challenge-response
- 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 method at a network element for attestation of applications, the method including sending a challenge to an application at an electronic device; receiving a response from the electronic device; processing the response; and upon determining that the response is invalid based on the processing, taking an enforcement action against the application.

## Claims

### Claim 1

A method at a network element for attestation of applications, the method comprising:
sending a challenge to an application at an electronic device;
receiving a response from the electronic device;
processing the response; and
upon determining that the response is invalid based on the processing, taking an enforcement action against the application.

### Claim 2 (depends on 1)

The method of claim 1, wherein the challenge includes a nonce, and wherein the response from the electronic device includes a hash of the nonce with a plurality of identifiers stored at the electronic device.

### Claim 3 (depends on 2)

The method of claim 2, wherein the processing comprises obtaining at least one of the identifiers from a trusted network server to recompute the hash and compare the hash in the response with the recomputed hash.

### Claim 4 (depends on 3)

The method of claim 3, wherein the plurality of identifiers includes a team identifier stored in an operating system of the electronic device and obtainable from the network server.

### Claim 5 (depends on 4)

The method of claim 4, wherein the processing further comprises:
receiving, in the response, a device check token;
adding authentication information to the device check token;
sending the device check token with the added authentication information to a device check server; and
receiving a response from the device check server to indicate whether the device check token is valid.

### Claim 6 (depends on 1)

The method of claim 1, wherein the enforcement action comprises at least one of: reporting the failure; blocking the application from accessing network resources; instructing the electronic device to wipe the application; instructing the electronic device to prompt a user to perform an action on the application; and instruct the electronic device to block running of the application.

### Claim 7 (depends on 1)

The method of claim 1, wherein the sending the challenge is performed on activation of the application.

### Claim 8 (depends on 1)

The method of claim 1, wherein the sending the challenge is performed at a configurable challenge frequency.

### Claim 9 (depends on 1)

The method of claim 1, further comprising, prior to receiving the response:
setting a grace period within a response is expected; and
taking the enforcement action when the response is not received with the grace period.

### Claim 10

A network element configured for attestation of applications, the network element comprising:
a processor; and
a communications subsystem,
wherein the network element is configured to:
send a challenge to an application at an electronic device;
receive a response from the electronic device;
process the response; and
upon determining that the response is invalid based on the processing, take an enforcement action against the application.

### Claim 11 (depends on 10)

The network element of claim 10, wherein the challenge includes a nonce, and wherein the response from the electronic device includes a hash of the nonce with a plurality of identifiers stored at the electronic device.

### Claim 12 (depends on 10)

The network element of claim 10, wherein the network element is configured to process by obtaining at least one of the identifiers from a trusted network server to recompute the hash and compare the hash in the response with the recomputed hash.

### Claim 13 (depends on 12)

The network element of claim 12, wherein the plurality of identifiers includes a team identifier stored in an operating system of the electronic device and obtainable from the network server.

### Claim 14 (depends on 13)

The network element of claim 13, wherein the network element is further configured to process by:
receiving, in the response, a device check token;
adding authentication information to the device check token;
sending the device check token with the added authentication information to a device check server; and
receiving a response from the device check server to indicate whether the device check token is valid.

### Claim 15 (depends on 10)

The network element of claim 10, wherein the enforcement action comprises at least one of: reporting the failure; blocking the application from accessing network resources; instructing the electronic device to wipe the application; instructing the electronic device to prompt a user to perform an action on the application; and instruct the electronic device to block running of the application.

### Claim 16 (depends on 10)

The network element of claim 10, wherein the network element is configured to send the challenge on activation of the application.

### Claim 17 (depends on 10)

The network element of claim 10, wherein the network element if configured to send the challenge at a configurable challenge frequency.

### Claim 18 (depends on 10)

The network element of claim 10, wherein the network element is further configured to, prior to receiving the response:
set a grace period within a response is expected; and
take the enforcement action when the response is not received with the grace period.

### Claim 19

A computer readable medium for storing instruction code, which, when executed by a processor of a network element configured for attestation of applications cause the network element to:
send a challenge to an application at an electronic device;
receive a response from the electronic device;
process the response; and
upon determining that the response is invalid based on the processing, take an enforcement action against the application.
