IP Library Granted Patent US 8,782,786
Granted Patent B2
US 8,782,786 · App. 11/694,109 · Granted Jul 15, 2014

Remedial action against malicious code at a client facility

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 8,782,786
App. No.
11/694,109
Granted
Jul 15, 2014
Kind
B2
Abstract

Aspects of this invention may relate to a malicious application remedial action request application where a network site interaction may be requested from a client computing facility; the network site interaction from the client computing facility may be determined to be unacceptable based on an acceptance policy at a gateway facility; access to the network site from the client computing facility may be denied; information relating to the attempted interaction with the network site may be sent from the gateway facility to the client computing facility, wherein the information may indicate that the attempted interaction occurred; and the client computing facility may interpret the information relating to the attempted interaction, determine whether the attempted interaction was the result of an automatically generated request, and take remedial action in the event that the attempted interaction was the result of the automatically generated request.

Claims (26)

1. A method, comprising:

requesting an interaction with a network site from a client computing facility;

determining that the interaction is unacceptable based on an acceptance policy for an enterprise at a gateway facility to the enterprise;

denying access to the network site from the client computing facility;

sending an information file to the client including information relating to the attempted interaction with the network site, wherein the information indicates that the interaction was requested; and

causing the client computing facility, in response to receipt of the information file, to interpret the information relating to the requested interaction, determine whether the requested interaction was the result of an automatically generated request by malicious code, and take remedial action in the event that the attempted interaction was the result of the automatically generated request by malicious code.

2. The method of claim 1 , wherein the acceptance policy comprises an unacceptable network site database.

3. The method of claim 1 , wherein the acceptance policy comprises an acceptable network site database.

4. The method of claim 1 , wherein the acceptance policy comprises a network site reputation database.

5. The method of claim 1 , wherein the acceptance policy comprises a rule evaluation of the network site interaction acceptability.

6. The method of claim 1 , wherein the acceptance policy is based on a block list.

7. The method of claim 1 , wherein the acceptance policy is based on an acceptance list.

8. The method of claim 1 , wherein the network site interaction is an access request to a network system.

9. The method of claim 1 , wherein the information is stored on the client computing facility.

10. The method of claim 9 , wherein the stored information is parsed by a client computer facility malicious code analysis application using a virus identity file (IDE).

11. The method of claim 10 , wherein the IDE parsed information is used to determine an appropriate action by the client computer facility.

12. The method of claim 1 , wherein the remedial action taken by the client computer facility is a result of a client computing facility resident malicious code detection application accessing information using IDE information.

13. The method of claim 1 , wherein the information comprises data adapted to be interpreted by the client computing facility.

14. The method of claim 1 , wherein the information comprises at least one command to be executed by the client computing facility.

15. The method of claim 1 , wherein the remedial action comprises scanning the client computing facility for malware.

16. The method of claim 1 , wherein the remedial action comprises any action determined by the client computer facility malicious code analysis application interacting with the IDE and the information.

17. The method of claim 1 , further comprising the step of sending an access approval request from the client computing facility to the gateway facility indicating that the requested interaction was user initiated and requesting a policy change to allow the requested interaction.

18. A system, comprising:

a client computing facility associated with an enterprise;

a gateway adapted to provide network access to the client computing facility, the gateway further adapted to receive a network site interaction request from the client computing facility, the gateway implementing an acceptance policy for the enterprise that determines an acceptability of the network site interaction from the client computing facility, and the gateway configured to transmit an information file to the client computing facility when the gateway determines that the attempted interaction with the network site is unacceptable based on an acceptance policy for the enterprise; and

a remedial action facility executing on the client computing facility responsive to the information file by determining whether the attempted interaction was the result of an automatically generated request from malicious code executing on the client, and taking remedial action in the event that the attempted interaction was the result of the automatically generated request.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 053476/0681 Recorded Mar 9, 2021
From: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT
To: SOPHOS LIMITED
Reel/Frame 056469/0815 →
RELEASE OF SECURITY INTEREST Recorded Jul 28, 2020
From: DEUTSCHE BANK AG NEW YORK BRANCH
To: SOPHOS LIMITED
Reel/Frame 053334/0220 →
PATENT SECURITY AGREEMENT FIRST LIEN Recorded Jul 6, 2020
From: SOPHOS LIMITED
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 053124/0350 →
PATENT SECURITY AGREEMENT SECOND LIEN Recorded Jul 6, 2020
From: SOPHOS LIMITED
To: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT
Reel/Frame 053476/0681 →
ASSIGNMENT OF SECURITY INTEREST Recorded Feb 3, 2014
From: JPMORGAN CHASE BANK, N.A.
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
Reel/Frame 032152/0883 →
CHANGE OF NAME Recorded Apr 11, 2013
From: SOPHOS PLC
To: SOPHOS LIMITED
Reel/Frame 030194/0299 →
SECURITY INTEREST Recorded May 11, 2012
From: RBC EUROPE LIMITED, AS EXISTING ADMINISTRATION AGENT AND COLLATERAL AGENT
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 028198/0285 →
SECURITY AGREEMENT Recorded Aug 8, 2011
From: SOPHOS LIMITED F/K/A SOPHOS PLC
To: ROYAL BANK OF CANADA EUROPE LIMITED, AS COLLATERAL AGENT
Reel/Frame 026717/0424 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 28, 2008
From: BACCAS, PAUL; HOWARD, FRASER; SVAJCER, VANJA
To: SOPHOS PLC
Reel/Frame 021166/0329 →