# US 2026/0093812 A1 · Automatically generating a safety environment for analyzing a suspect data file

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

- Number: US 2026/0093812 A1
- Document ID: US20260093812A1
- Status: Published application
- Kind: A1
- Application number: 18/904,626
- Filed: 2024-10-02
- Published: 2026-04-02
- Earliest claimed: 2024-10-02
- Assignees: Lenovo Global Technology (United States) Inc.
- Applicants: Lenovo Global Technology (United States) Inc.
- Inventors: Marco M. Rengan
- Web page: https://patentgrep.com/patent/US20260093812A1

## CPC

- G06F 21/568: {eliminating virus, restoring damaged files}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- 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 method for automatically generating a safety environment upon detection of a suspected malicious data file includes detecting, on a computing device, a suspect data file suspected of including code harmful to the computing device and/or a user and generating, via a request from the user, a safety environment accessible to the computing device. The safety environment is isolated from a user environment of the computing device where effects of accessing the suspect data file in the safety environment are isolated from the user environment of the computing device. The method includes performing one or more computing activities on the suspect data file within the safety environment that are configured to determine whether the suspect data file includes code harmful to the computing device and/or the user. The method includes receiving an exit signal to exit the safety environment and deactivating the safety environment in response to the exit signal.

## Claims

### Claim 1

A method comprising:
detecting, on a computing device, a suspect data file suspected of comprising code harmful to the computing device and/or a user of the computing device;
generating, in response to a request from the user, a safety environment accessible to the computing device, the safety environment isolated from a user environment of the computing device, wherein effects of accessing the suspect data file in the safety environment are isolated from the user environment of the computing device;
performing one or more computing activities on the suspect data file within the safety environment, the one or more computing activities configured to determine whether the suspect data file comprises code harmful to the computing device and/or the user;
receiving an exit signal to exit the safety environment; and
deactivating the safety environment in response to the exit signal.

### Claim 2 (depends on 1)

The method of claim 1, further comprising isolating the suspect data file in the safety environment in response to a user action.

### Claim 3 (depends on 1)

The method of claim 1, wherein the request from the user to start the safety environment comprises receiving an indication of the user one of selecting a soft key on an electronic display of the computing device and pressing a safe environment button, the safe environment button available on a user interface of the computing device and/or on a case of the computing device.

### Claim 4 (depends on 1)

The method of claim 1, wherein receiving the exit signal comprises:
receiving an indication of user input selecting exiting the safety environment, the user input indicating that the suspect data file is performing as expected in response to performing the one or more computing activities on the suspect data file; and/or
receiving an indication from safety analysis software that is operating within the safety environment that the suspect data file is performing as expected in response to performing the one or more computing activities on the suspect data file.

### Claim 5 (depends on 4)

The method of claim 4, wherein the safety analysis software is configured to:
analyze results of performing the one or more computing activities on the suspect data file;
provide the indication that the suspect data file is performing as expected in response to the results being indicative of expected operation; and
in response to the results being indicative of abnormal operation harmful to the computing device and/or the user:
provide a warning that the suspect data file is not performing as expected, the warning provided to the user and/or to a system administrator; and/or
disable further performing of computing activities on the suspect data file.

### Claim 6 (depends on 4)

The method of claim 4, wherein the safety analysis software is configured to:
analyze the suspect data file to determine harmful impacts of the suspect data file to the computing device and/or to the user prior to the performing the one or more computing activities on the suspect data file; and
in response to the analysis of the suspect data file indicating potential harm to the computing device and/or the user:
provide a warning that the suspect data file is harmful to the computing device and/or the user, the warning provided to the user and/or to a system administrator; and/or
disable further performing of computing activities on the suspect data file.

### Claim 7 (depends on 1)

The method of claim 1, wherein the safety environment comprises a virtual machine (“VM”) that is operated on one of the computing device and a separate computing device accessible to the computing device, wherein the VM prevents actions resulting from the performing of the one or more computing activities from affecting the computing device and/or another user environment of the computing device.

### Claim 8 (depends on 1)

The method of claim 1, wherein the safety environment executes on a separate computing device, wherein the separate computing device prevents actions resulting from the performing of the one or more computing activities from affecting the computing device and/or other computing devices.

### Claim 9 (depends on 1)

The method of claim 1, wherein the safety environment enables one or more actions unavailable to the user in the safety environment prior to generating the safety environment, the one or more actions comprising administrative actions available to a system administrator.

### Claim 10 (depends on 1)

The method of claim 1, wherein the performing of the one or more computing activities on the suspect data file comprises receiving user input indicating the one or more computing activities to be performed and further user input indicating whether results of the performing of the one or more computing activities represent expected results.

### Claim 11 (depends on 1)

The method of claim 1, wherein the receiving of the exit signal comprises receiving a command in response to an interactive query resulting from the performing of the computing activities on the suspect data file.

### Claim 12 (depends on 1)

The method of claim 1, wherein the receiving of the exit signal comprises expiration of a timer related to inactivity in the safety environment, the expiration of the timer causing the exit signal.

### Claim 13 (depends on 1)

The method of claim 1, wherein the detecting of the suspect data file comprises receiving a communication from the user that the suspect data file is suspected of comprising code harmful to the computing device and/or a user.

### Claim 14

An apparatus comprising:
a processor; and
non-transitory computer readable storage media storing code, the code being executable by the processor to perform operations comprising:
detecting, on a computing device, a suspect data file suspected of comprising code harmful to the computing device and/or a user of the computing device;
generating, in response to a request from the user, a safety environment accessible to the computing device, the safety environment isolated from a user environment of the computing device, wherein effects of accessing the suspect data file in the safety environment are isolated from the user environment of the computing device;
performing one or more computing activities on the suspect data file within the safety environment, the one or more computing activities configured to determine whether the suspect data file comprises code harmful to the computing device and/or the user;
receiving an exit signal to exit the safety environment; and
deactivating the safety environment in response to the exit signal.

### Claim 15 (depends on 14)

The apparatus of claim 14, wherein the computer readable storage media stores further code executable by the processor to perform further operations comprising:
receiving an indication of user input selecting exiting the safety environment, the user input indicating that the suspect data file is performing as expected in response to performing the one or more computing activities on the suspect data file; and/or
receiving an indication from safety analysis software that is operating within the safety environment that the suspect data file is performing as expected in response to performing the one or more computing activities on the suspect data file.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the safety analysis software is configured to:
analyze results of performing the one or more computing activities on the suspect data file;
provide the indication that the suspect data file is performing as expected in response to the results being indicative of expected operation; and
in response to the results being indicative of abnormal operation harmful to the computing device and/or the user:
provide a warning that the suspect data file is not performing as expected, the warning provided to the user and/or to a system administrator; and/or
disable further performing of computing activities on the suspect data file.

### Claim 17 (depends on 15)

The apparatus of claim 15, wherein the safety analysis software is configured to:
analyze the suspect data file to determine harmful impacts of the suspect data file to the computing device and/or to the user prior to the performing the one or more computing activities on the suspect data file; and
in response to the analysis of the suspect data file indicating potential harm to the computing device and/or the user:
provide a warning that the suspect data file is harmful to the computing device and/or the user, the warning provided to the user and/or to a system administrator; and/or
disable further performing of computing activities on the suspect data file.

### Claim 18 (depends on 14)

The apparatus of claim 14, wherein the safety environment comprises a virtual machine (“VM”) that is operated on one of the computing device and a separate computing device accessible to the computing device, wherein the VM prevents actions resulting from the performing of the one or more computing activities from affecting the computing device and/or another user environment of the computing device.

### Claim 19 (depends on 14)

The apparatus of claim 14, wherein the receiving of the exit signal comprises receiving a command in response to an interactive query resulting from the performing of the computing activities on the suspect data file.

### Claim 20

A system comprising:
a computing device comprising a processor and non-transitory computer readable storage media storing code, the code being executable by the processor to perform operations comprising:
detecting, on the computing device, a suspect data file suspected of comprising code harmful to the computing device and/or a user of the computing device;
generating, in response to a request from the user, a safety environment accessible to the computing device, the safety environment isolated from a user environment of the computing device, wherein effects of accessing the suspect data file in the safety environment are isolated from the user environment of the computing device;
performing one or more computing activities on the suspect data file within the safety environment, the one or more computing activities configured to determine whether the suspect data file comprises code harmful to the computing device and/or the user;
receiving an exit signal to exit the safety environment; and
deactivating the safety environment in response to the exit signal.
