IP Library Granted Patent US 9,792,444
Granted Patent B2
US 9,792,444 · App. 15/063,312 · Granted Oct 17, 2017

Inoculator and antibody for computer security

Inventors: Michael Gregory Hoglund (Monte Sereno, CA); Shawn Michael Bracken (Pinole, CA)
Assignee: CounterTack, Inc.
G06F21/577G06F21/568G06F21/57
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,792,444
App. No.
15/063,312
Granted
Oct 17, 2017
Kind
B2
Abstract

In an embodiment of the invention, a method includes: determining, in a computer, an area where an undesired computer program will reside; and providing a data object in the area, so that the data object is an antibody that provides security to the computer and immunity against the undesired program. Another embodiment of the invention also provides an apparatus (or system) that can be configured to perform at least some of the above functionalities.

Claims (39)

1. A method performed by a first computing device, the method comprising:

determining, in a second computing device that is distinct and separate from the first computing device, a location where an undesired computer program is configured to reside upon installation on the second computing device; and

providing, to the second computing device, a data object to occupy the determined installation location of the undesired computer program in the second computing device to prevent the undesired computer program from being installed in the determined installation location in the second computing device.

2. The method of claim 1 , further comprising:

providing a null configuration object in a second location in the second computing device, wherein the null configuration object is associated with the data object.

3. The method of claim 1 , further comprising:

preventing a deletion or modification of the data object.

4. The method of claim 3 , wherein preventing the deletion or modification of the data object comprises:

setting a security permission for the data object.

5. The method of claim 3 , wherein preventing the deletion or modification of the data object comprises:

setting the data object to have an object type that differs from the undesired program.

6. The method of claim 5 , wherein preventing the deletion or modification of the data object comprises:

placing a second data object in the data object.

7. The method of claim 1 , wherein the location comprises a memory space and/or a file system location.

8. The method of claim 1 , wherein the data object has the same name as the undesired computer program.

9. A first computing device, comprising:

one or more processors; and

memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for:

determining, in a second computing device that is distinct and separate from the first computing device, a location where an undesired computer program is configured to reside upon installation on the second computing device; and

providing, to the second computing device, a data object to occupy the determined installation location of the undesired computer program in the second computing device to prevent the undesired computer program from being installed in the determined installation location on the second computing device.

10. The first computing device of claim 9 , wherein the one or more programs include instructions for:

providing a null configuration object in a second location in the second computing device, wherein the null configuration object is associated with the data object.

11. The first computing device of claim 9 , wherein the location comprises a memory space and/or a file system location.

12. The first computing device of claim 9 , wherein the data object has the same name as the undesired computer program.

13. A non-transitory computer readable storage medium storing one or more programs for execution by one or more processors of a first computing device, the one or more programs including instructions for:

determining, in a second computing device that is distinct and separate from the first computing device, a location where an undesired computer program is configured to reside upon installation on the second computing device; and

providing, to the second computing device, a data object to occupy the determined installation location of the undesired computer program in the second computing device to prevent the undesired computer program from being installed in the determined installation location on the second computing device.

14. The computer readable storage medium of claim 13 , wherein the one or more programs include instructions for:

providing a null configuration object in a second location in the second computing device, wherein the null configuration object is associated with the data object.

15. The computer readable storage medium of claim 13 , wherein the one or more programs include instructions for:

preventing a deletion or modification of the data object.

16. The computer readable storage medium of claim 15 , wherein preventing the deletion or modification of the data object comprises:

setting a security permission for the data object.

17. The computer readable storage medium of claim 15 , wherein preventing the deletion or modification of the data object comprises:

setting the data object to have an object type that differs from the undesired program.

18. The computer readable storage medium of claim 17 , wherein preventing the deletion or modification of the data object comprises:

placing a second data object in the data object.

19. The computer readable storage medium of claim 13 , wherein the location comprises a memory space and/or a file system location.

20. The computer readable storage medium of claim 13 , wherein the data object has the same name as the undesired computer program.

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBERS DATA PREVIOUSLY RECORDED AT REEL: 70134 FRAME: 0413. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY TEREST . Recorded Feb 14, 2025
From: GOSECURE, INC.
To: COMERICA BANK
Reel/Frame 070235/0936 →
SECURITY INTEREST Recorded Feb 6, 2025
From: GOSECURE, INC.
To: COMERICA BANK
Reel/Frame 070134/0413 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 15, 2023
From: HBGARY, INC.
To: COUNTERTACK, INC.
Reel/Frame 065889/0820 →
CHANGE OF NAME Recorded Dec 15, 2023
From: COUNTERTACK, INC.
To: GOSECURE, INC.
Reel/Frame 066046/0923 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 15, 2023
From: HBGARY, INC.
To: COUNTERTACK, INC.
Reel/Frame 065889/0860 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 15, 2023
From: HOGLUND, MICHAEL GREGORY; BRACKEN, SHAWN MICHAEL
To: HBGARY, INC.
Reel/Frame 065889/0750 →
CHANGE OF NAME Recorded Sep 28, 2023
From: COUNTERTACK, INC.
To: GOSECURE, INC.
Reel/Frame 065082/0434 →
RELEASE OF SECURITY INTEREST Recorded May 29, 2018
From: PACIFIC WESTERN BANK
To: COUNTERTACK INC.
Reel/Frame 045923/0804 →
SECURITY INTEREST Recorded Nov 21, 2016
From: COUNTERTACK INC.
To: PACIFIC WESTERN BANK
Reel/Frame 040384/0329 →
Continuity (3)
Continuation 13200504 · Sep 23, 2011
Provisional Application 61456192 · Nov 1, 2010
Related Publication 20160292424A1 · Oct 6, 2016