# US 2021/0084057 A1 · System and method for a vendor risk management platform

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

- Number: US 2021/0084057 A1
- Document ID: US20210084057A1
- Status: Published application
- Kind: A1
- Application number: 16/620,443
- Filed: 2018-06-06
- Published: 2021-03-18
- Earliest claimed: 2017-06-07
- Assignees: Bank of Montreal
- Applicants: Bank of Montreal
- Inventors: Rajneesh CHHABRA
- Web page: https://patentgrep.com/patent/US20210084057A1

## CPC

- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06N 20/00: Machine learning
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 63/1433: {Vulnerability analysis}
- 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)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A risk management platform may have a risk management server and a client portal. The client portal can be configured to: receive security data relating to a client system; anonymize the security data; and transmit the security data to the risk management server along with a unique key linked the client system. The security data the risk management server can be configured to: identify the client system using the unique key; generate a score as a security assessment of the client system using a plurality of rules to evaluate the security data; detect a security threat relevant to the client system by processing real-time data feeds; generate an alert for the security threat to the client system; monitor the client portal for a response to the alert by the client system; and update the score in response to the alert or the response.

## Claims

### Claim at position 1

1-68. (canceled)

### Claim 69

A method comprising:
assigning, by a server, a unique token to each of a plurality of client system to anonymize an identification of each client system and storing a link between each unique token and a corresponding client system;
receiving, by the server, an electronic file uploaded from a client device of a client system and associated with the unique token of that client system;
generating, by the server, a unique key for the received electronic file;
storing, by the server in a data repository, the electronic file corresponding to the unique key;
deleting, by the server, identification data associated with the client system within the electronic file;
display, by the server, the electronic file without identification data;
generating, by the server, a score associated with the unique token and representing a security assessment of the client system based at least in part on the electronic file;
in response to a confirmation inputted to the server regarding the security assessment, deleting, by the server, the electronic file associated with the unique key within the data repository; and
continuously monitoring, by the server, each client system and when a security threat is detected,
sending, the server, an alert to each client system; and
updating, by the server, the score representing the security assessment.

### Claim 70 (depends on 69)

The method of claim 69, further comprising:
displaying, by the server, a dashboard comprising updated score associated with each client system, wherein each score corresponds to the unique token of each respective client system.

### Claim 71 (depends on 69)

The method of claim 69, further comprising:
identifying, by the server, a plurality of keywords within the electronic file;
for each keyword, determining, by the server, one or more parameters applicable to the keyword; and
generating, by the server, the updated score based at least in part on a value for each of the one or more parameters.

### Claim 72 (depends on 71)

The method of claim 71, wherein the keyword corresponds to a password, and the one or more parameters applicable to the keyword comprise at least one of length, capital, letter, number, and character.

### Claim 73 (depends on 69)

The method of claim 69, further comprising:
transmitting, by the server, an alert to the client system; and
updating, by the server, the score based on a response time to the alert from the client system.

### Claim 74 (depends on 73)

The method of claim 73, wherein a response to the alert received from the client system indicates an action taken by the client system.

### Claim 75 (depends on 74)

The method of claim 74, wherein the action comprises at least one of: network discovery, penetration test, vulnerability test, hardware update, and software update.

### Claim 76 (depends on 69)

The method of claim 69, wherein the server deletes metadata associated with the electronic file.

### Claim 77 (depends on 69)

The method of claim 69, wherein the server determines the score based on a response to one or more questions displayed on at least one electronic device of the client system.

### Claim 78 (depends on 69)

The method of claim 69, wherein the server executes a machine learning model to analyze the electronic file and generate the score.

### Claim 79

A computer system comprising:
a plurality of client systems connected to a server;
a data repository accessible to the server, wherein the server is configured to:
assign a unique token to each of a plurality of client system to anonymize an identification of each client system and storing a link between each unique token and a corresponding client system;
receive an electronic file uploaded from a client device of a client system and associated with the unique token of that client system;
generate a unique key for the received electronic file;
store, in a data repository, the electronic file corresponding to the unique key;
delete identification data associated with the client system within the electronic file;
display the electronic file without identification data;
generate a score associated with the unique token and representing a security assessment of the client system based at least in part on the electronic file;
in response to a confirmation inputted to the server regarding the security assessment, delete the electronic file associated with the unique key within the data repository; and
continuously monitor each client system and when a security threat is detected,
send an alert to each client system; and
update the score representing the security assessment.

### Claim 80 (depends on 79)

The computer system of claim 79, wherein the server is further configured to:
display a dashboard comprising updated score associated with each client system, wherein each score corresponds to the unique token of each respective client system.

### Claim 81 (depends on 79)

The computer system of claim 79, wherein the server is further configured to:
identify a plurality of keywords within the electronic file;
for each keyword, determine one or more parameters applicable to the keyword; and
generate the updated score based at least in part on a value for each of the one or more parameters.

### Claim 82 (depends on 81)

The computer system of claim 81, wherein the keyword corresponds to a password, and the one or more parameters applicable to the keyword comprise at least one of length, capital, letter, number, and character.

### Claim 83 (depends on 79)

The computer system of claim 79, wherein the server is further configured to:
transmit an alert to the client system; and
update the score based on a response time to the alert from the client system.

### Claim 84 (depends on 83)

The computer system of claim 83, wherein a response to the alert received from the client system indicates an action taken by the client system.

### Claim 85 (depends on 84)

The computer system of claim 84, wherein the action comprises at least one of: network discovery, penetration test, vulnerability test, hardware update, and software update.

### Claim 86 (depends on 79)

The computer system of claim 79, wherein the server deletes metadata associated with the electronic file.

### Claim 87 (depends on 79)

The computer system of claim 79, wherein the server determines the score based on a response to one or more questions displayed on at least one electronic device of the client system.

### Claim 88 (depends on 79)

The computer system of claim 79, wherein the server executes a machine learning model to analyze the electronic file and generate the score.
