# US 2018/0324195 A1 · Automated Runtime Detection Of Malware

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

- Number: US 2018/0324195 A1
- Document ID: US20180324195A1
- Status: Published application
- Kind: A1
- Application number: 16/040,021
- Filed: 2018-07-19
- Published: 2018-11-08
- Earliest claimed: 2013-09-12
- Assignees: Virsec Systems, Inc.
- Applicants: Virsec Systems, Inc.
- Inventors: Satya V. Gupta; Raymond F. DeMeo
- Web page: https://patentgrep.com/patent/US20180324195A1

## CPC

- H04L 63/1416: {Event detection, e.g. attack signature detection}
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- 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

One example method and correspond apparatus extracts a model of a computer application during load time and stores the model of the computer application in a database. This example method and corresponding apparatus also inserts instructions into the computer application to collect data at runtime. This example method and corresponding apparatus then analyzes the data collected at runtime against the stored model of the computer application to detect one or more security events and tracks the one or more security events using a state machine.

## Claims

### Claim 1

A computer-implemented method comprising:
prior to executing a module of a computer application, verifying integrity of the module by:
computing a checksum of the module;
comparing the computed checksum against a valid checksum stored in memory for the module; and
generating at least one security event if the computed checksum does not match the valid checksum, the at least one security event triggering at least one remedial action related to the computer application.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
if the computed checksum does match the valid checksum:
extracting code sections of the module during load time;
analyzing data collected at runtime against the extracted code sections; and
generating one or more security events based on the analysis, the one or more security events triggering one or more remedial actions related to the computer application.

### Claim 3 (depends on 2)

The method of claim 2, wherein a remedial action is one of: terminating the computer application, terminating one or more threads of the computer application, unbinding or releasing a socket on one or more threads of the computer application, unblocking sockets associate with a server socket of the computer application, generating notifications to a user, and ignoring a security event.

### Claim 4 (depends on 2)

The method of claim 2, wherein a security event is processed in one of: monitor mode, paranoid mode, or learning mode, and wherein each mode provides different processing of the security event.

### Claim 5 (depends on 4)

The method of claim 4, wherein in the monitor mode:
generating a notification to a user in response to the security event; and
triggering the one or more remedial actions by the user.

### Claim 6 (depends on 4)

The method of claim 4, wherein in the paranoid mode:
automatically triggering the one or more remedial actions in response to the security event.

### Claim 7 (depends on 4)

The method of claim 4, wherein in learning mode:
collecting information associated with the security event; and
based on the collected information, building criteria for automatically generating future security events and triggering remedial actions in response to the future security events.

### Claim 8 (depends on 1)

The method of claim 1, wherein the verifying of integrity occurs as the module is being loaded into memory.

### Claim 9 (depends on 1)

The method of claim 1, wherein the computing of the checksum is performed by a checksum verification service.

### Claim 10 (depends on 1)

The method of claim 1, wherein the comparing of the computed checksum determines whether the module is corrupted with malware prior to being loaded to memory.

### Claim 11

A computer system comprising:
prior to executing a module of a computer application, verifying integrity of the module by:
a client configured to:
compute a checksum of the module; and
compare the computed checksum against a valid checksum stored in memory for the module; and
an analysis engine configured to:
generate at least one security event if the computed checksum does not match the valid checksum, the at least one security event triggering at least one remedial action related to the computer application.

### Claim 12 (depends on 11)

The system of claim 11, wherein:
the client further configured to:
if the computed checksum does match the valid checksum, extract code sections of the module during load time; and
the analysis engine further configured to:
analyze data collected at runtime against the extracted code sections; and
generate one or more security events based on the analysis, the one or more security events triggering one or more remedial actions related to the computer application.

### Claim 13 (depends on 12)

The system of claim 12, wherein a remedial action is one of: terminating the computer application, terminating one or more threads of the computer application, unbinding or releasing a socket on one or more threads of the computer application, unblocking sockets associate with a server socket of the computer application, generating notifications to a user, and ignoring a security event.

### Claim 14 (depends on 12)

The system of claim 12, wherein the analysis engine is configured to process a security event in one of: monitor mode, paranoid mode, or learning mode, and wherein each mode provides different processing of the security event.

### Claim 15 (depends on 14)

The system of claim 14, wherein in the monitor mode, the analysis engine is configured to:
generate a notification to a user in response to the security event; and
trigger the one or more remedial actions by the user.

### Claim 16 (depends on 14)

The system of claim 14, wherein in the paranoid mode, the analysis engine is configured to:
automatically trigger the one or more remedial actions in response to the security event.

### Claim 17 (depends on 14)

The system of claim 14, wherein in learning mode, the analysis engine is configured to:
collect information associated with the security event; and
based on the collected information, build criteria for automatically generating future security events triggering remedial actions in response to the future security events.

### Claim 18 (depends on 11)

The system of claim 11, wherein the verifying of integrity occurs as the module is being loaded into memory.

### Claim 19 (depends on 11)

The system of claim 11, wherein the computing of the checksum is performed by a checksum verification service.

### Claim 20 (depends on 11)

The system of claim 11, wherein the comparing of the computed checksum determines whether the module is corrupted with malware prior to being loaded to memory.
