# US 2020/0394297 A1 · Securely and efficiently providing user notifications about security actions

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

- Number: US 2020/0394297 A1
- Document ID: US20200394297A1
- Status: Published application
- Kind: A1
- Application number: 17/008,038
- Filed: 2020-08-31
- Published: 2020-12-17
- Earliest claimed: 2018-04-11
- Assignees: CrowdStrike, Inc.
- Applicants: CrowdStrike, Inc.
- Inventors: Ion-Alexandru Ionescu
- Web page: https://patentgrep.com/patent/US20200394297A1

## CPC

- G06F 21/554: {involving event detection and direct action}
- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 21/33: using certificates
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A security agent executing in kernel mode may receive a request from the anti-malware component executing with low privileges in user mode, and, in response, the security agent may perform a security action with respect to a malicious file detected on the computing device. The security agent may then assist the anti-malware component in providing a user notification about the security action by obtaining, on behalf of the anti-malware component, a user token associated with the user session in which the malicious file was detected. The anti-malware component can use the obtained user token to request a pointer to a Component Object Model (COM) interface for outputting the notification in context of the appropriate user session, which allows for securely and efficiently providing the user notification.

## Claims

### Claim 1

A method comprising:
performing, by a software security agent executing in kernel mode of a computing device, a security action with respect to a malicious data object or a malicious activity detected on the computing device;
requesting, by one or more user mode components, a pointer to one or more Component Object Model (COM) interfaces; and
outputting, via an output device of the computing device, and using the pointer to the one or more COM interfaces, a notification to indicate that the security action was performed.

### Claim 2 (depends on 1)

The method of claim 1, further comprising providing, by the software security agent, a token to the one or more user mode components, the token associated with a user session in which the malicious data object or the malicious activity was detected, wherein the requesting of the pointer to the one or more COM interfaces is based at least in part on the token.

### Claim 3 (depends on 2)

The method of claim 2, further comprising, prior to the providing of the token to the one or more user mode components:
determining, by the software security agent, a user account name or identifier (ID);
calling, by the software security agent, an authentication function using the user account name or ID; and
receiving, by the software security agent, the token returned by the authentication function.

### Claim 4 (depends on 1)

The method of claim 1, wherein the notification is output in context of a user session in which the malicious data object or the malicious activity was detected.

### Claim 5 (depends on 1)

The method of claim 1, wherein the outputting comprises calling a method of the one or more COM interfaces.

### Claim 6 (depends on 1)

The method of claim 1, wherein the requesting of the pointer to the one or more COM interfaces further comprises using, by the one or more user mode components, a moniker that specifies a session identifier (ID) of a user session in which the malicious data object or the malicious activity was detected.

### Claim 7 (depends on 1)

The method of claim 1, wherein the malicious data object comprises a malicious file, or wherein the malicious activity is performed based on data contained within a file.

### Claim 8

A computing device comprising:
an output device;
a processor; and
memory storing computer-executable instructions that, when executed by the processor, cause the processor to:
execute a software security agent in kernel mode of the computing device to perform a security action with respect to a malicious data object or a malicious activity detected on the computing device;
execute one or more user mode components to request a pointer to one or more Component Object Model (COM) interfaces; and
output a notification via the output device and using the pointer to the one or more COM interfaces, the notification indicating that the security action was performed.

### Claim 9 (depends on 8)

The computing device of claim 8, wherein the computer-executable instructions, when executed by the processor, further cause the processor to execute the software security agent to provide a token to the one or more user mode components, the token associated with a user session in which the malicious data object or the malicious activity was detected, wherein the pointer to the one or more COM interfaces is requested based at least in part on the token.

### Claim 10 (depends on 8)

The computing device of claim 8, wherein requesting the pointer to the one or more COM interfaces comprises using, by the one or more user mode components, a moniker that specifies a session identifier (ID) of a user session in which the malicious data object or the malicious activity was detected.

### Claim 11 (depends on 8)

The computing device of claim 8, wherein the computer-executable instructions, when executed by the processor, further cause the processor to execute the software security agent to:
determine a user account name or identifier (ID);
call an authentication function using the user account name or ID;
receive a token returned by the authentication function; and
provide the token to the one or more user mode components,
wherein the pointer to the one or more COM interfaces is requested based at least in part on the token.

### Claim 12 (depends on 8)

The computing device of claim 8, wherein the notification is output in context of a user session in which the malicious data object or the malicious activity was detected.

### Claim 13 (depends on 8)

The computing device of claim 8, wherein the malicious data object comprises a malicious file, or wherein the malicious activity is performed based on data contained within a file.

### Claim 14

A non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors of a computing device, cause the computing device to:
execute a software security agent in kernel mode of the computing device to perform a security action with respect to a malicious data object or a malicious activity detected on the computing device;
execute one or more user mode components to request a pointer to one or more Component Object Model (COM) interfaces; and
output a notification via an output device of the computing device and using the pointer to the one or more COM interfaces, the notification indicating that the security action was performed.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the computer-executable instructions, when executed by the one or more processors, further cause the computing device to execute the software security agent to:
determine a user account name or identifier (ID) of a user who is currently logged into a user session in which the malicious data object or the malicious activity was detected;
obtain a token based at least in part on the user account name or ID; and
provide the token to the one or more user mode components,
wherein the pointer to the one or more COM interfaces is requested based at least in part on the token.

### Claim 16 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein requesting the pointer to the one or more COM interfaces comprises using, by the one or more user mode components, a moniker that specifies a session identifier (ID) of a user session in which the malicious data object or the malicious activity was detected.

### Claim 17 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein outputting the notification comprises calling a method of the one or more COM interfaces.

### Claim 18 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the notification is output in context of a user session in which the malicious data object or the malicious activity was detected.

### Claim 19 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the computer-executable instructions, when executed by the one or more processors, further cause the computing device to execute the software security agent to:
determine a user account name or identifier (ID);
call an authentication function using the user account name or ID;
receive a token returned by the authentication function; and
provide the token to the one or more user mode components,
wherein the pointer to the one or more COM interfaces is requested based at least in part on the token.

### Claim 20 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the malicious data object comprises a malicious file, or wherein the malicious activity is performed based on data contained within a file.
