# US 2019/0173819 A1 · Determining authenticity of reported user action in cybersecurity risk assessment

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

- Number: US 2019/0173819 A1
- Document ID: US20190173819A1
- Status: Published application
- Kind: A1
- Application number: 16/266,467
- Filed: 2019-02-04
- Published: 2019-06-06
- Earliest claimed: 2017-05-26
- Assignees: Wombat Security Technologies, Inc.
- Applicants: Wombat Security Technologies, Inc.
- Inventors: Kurt Wescoe; Trevor T. Hawthorn; Alan Himler; Patrick H. Veverka; John T. Campbell; Dustin D. Brungart; Norman Sadeh-Koniecpol
- Web page: https://patentgrep.com/patent/US20190173819A1

## CPC

- H04L 51/212: using filtering or selective blocking
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- H04L 63/1433: {Vulnerability analysis}
- G06F 21/562: {Static detection}
- H04L 63/14: {for detecting or protecting against malicious traffic}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- 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)

## Abstract

An electronic device will identify an electronic message received by a messaging client that is associated with a first recipient, and it will analyze the electronic message to determine whether the electronic message is a simulated malicious message. Upon determining that electronic message is a simulated malicious message, the device will identify an actuatable element in the electronic message. The actuatable element will include a service address. The device will modify the electronic message by appending a user identifier of the first recipient to the service address of the actuatable element. Then, when the actutable element is actuated, the system may determine whether the first recipient actuated the actuatable element or an alternate recipient did so based on whether the user identifier of the first recipient is still appended (or is the only user identifier appended) to the actuatable element.

## Claims

### Claim 1

A method of verifying authenticity of a user-reported action in a cybersecurity testing campaign, the method comprising:
by a message origination server, executing programming instructions that cause the message origination server to:
generate a simulated malicious message that includes an actuatable element, wherein the actuatable element includes a service address, and
send the simulated malicious message to an account of an intended recipient; and
by a cybersecurity analyzer server, executing programming instructions that cause the cybersecurity analyzer server to:
receive a service request for the service address,
determine that the service request includes a user identifier,
determine whether the user identifier of the service request is a user identifier of the intended recipient, and
if the user identifier of the service request is the user identifier of the intended recipient, generate a record indicating that the intended recipient actuated the actuatable element, otherwise determine that the simulated malicious message was forwarded to an alternate recipient and not generate a record indicating that the intended recipient actuated the actuatable element.

### Claim 2 (depends on 1)

The method of claim 1, wherein generating the simulated malicious message that includes the actuatable element includes:
generating the simulated malicious message so that the actuatable element includes a personalized service address; and
storing the personalized service address in a data store in association with the intended recipient.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
receiving a service call at the service address,
and wherein determining whether the user identifier of the service request is a user identifier of the intended recipient comprises, by the cybersecurity analyzer server checking the data set to identify whether the intended recipient actuated the actuatable element.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining whether the service request includes an authentication token; and
only generating the record indicating that intended recipient actuated the actuatable element if the service request includes the authentication token and the authentication token has a verifiable value, otherwise determining that the simulated malicious message was intercepted and not generating a record indicating that intended recipient actuated the actuatable element.

### Claim 5 (depends on 1)

The method of claim 1 wherein the message origination server and the cybersecurity analyzer server comprise elements of a common system.

### Claim 6 (depends on 1)

The method of claim 1, further comprising, by the cybersecurity analyzer server:
if the user identifier is associated with the intended recipient, causing a training action of a first type to be delivered to the intended recipient, wherein the first type is a type that is directed to training the intended recipient to avoid falling victim to malicious messages; and
if the actuation was by the alternate recipient, causing a training action of a second type to be delivered to the intended recipient, wherein the second type is directed to training the intended recipient to avoid forwarding malicious messages.

### Claim 7 (depends on 1)

The method of claim 1 further comprising, by the message origination server when generating the simulated malicious message:
including, in a header field of a header section of the simulated malicious message:
a key, and
a value that satisfies a first trusted sender rule.

### Claim 8

A messaging system comprising:
a message origination server;
computer-readable programming instructions that are configured to cause the message origination server to:
generate a simulated malicious message that includes an actuatable element, wherein the actuatable element includes a service address, and
send the simulated malicious message to an account of an intended recipient; and
a cybersecurity analyzer server; and
computer-readable programming instructions that are configured to cause the cybersecurity analyzer server to:
receive a service request for the service address,
determine that the service request includes a user identifier,
determine whether the user identifier of the service request is a user identifier of the intended recipient, and
if the user identifier of the service request is the user identifier of the intended recipient, generate a record indicating that intended recipient actuated the actuatable element, otherwise determine that the simulated malicious message was forwarded to an alternate recipient and not generate a record indicating that the intended recipient actuated the actuatable element.

### Claim 9 (depends on 8)

The system of claim 8, wherein the instructions to generate the simulated malicious message that includes the actuatable element comprise instructions to:
generate the simulated malicious message so that the actuatable element includes a personalized service address; and
store the personalized service address in a data store in association with the intended recipient.

### Claim 10 (depends on 8)

The system of claim 8, further comprising a data store, and wherein:
the instructions to determine whether the user identifier of the service request is a user identifier of the intended recipient comprises instructions configured to cause the cybersecurity analyzer server to, in response to receipt of a service call at the service address, check the data set to identify whether the intended recipient actuated the actuatable element.

### Claim 11 (depends on 8)

The system of claim 8, further comprising additional programming instructions that are configured to cause the cybersecurity analyzer server to:
determine whether the service request includes an authentication token; and
only generate the record indicating that intended recipient actuated the actuatable element if the service request includes the authentication token and the authentication token has a verifiable value, otherwise determine that the simulated malicious message was intercepted and not generating a record indicating that intended recipient actuated the actuatable element.

### Claim 12 (depends on 8)

The system of claim 8 wherein the message origination server and the cybersecurity analyzer server comprise elements of a common system.

### Claim 13 (depends on 8)

The system of claim 8, further comprising additional computer-readable programming instructions that are configured to cause the cybersecurity analyzer server to:
if the user identifier is associated with the intended recipient, cause a training action of a first type to be delivered to the intended recipient, wherein the first type is a type that is directed to training the intended recipient to avoid falling victim to malicious messages; and
if the actuation was by the alternate recipient, cause a training action of a second type to be delivered to the intended recipient, wherein the second type is directed to training the intended recipient to avoid forwarding malicious messages.

### Claim 14 (depends on 8)

The system of claim 8, further comprising additional computer-readable programming instructions that are configured to cause the message origination server to, when generating the simulated malicious message:
include, in a header field of a header section of the simulated malicious message:
a key, and
a value that satisfies a first trusted sender rule.
