IP Library Granted Patent US 9,813,298
Granted Patent B2
US 9,813,298 · App. 15/284,084 · Granted Nov 7, 2017

Applying policies to subnets

Inventor: Paul Michael Martini (San Diego, CA)
Assignee: iboss, Inc.
H04L41/0893H04L41/50H04L43/065H04L43/08H04L45/06H04L45/22H04L47/2408H04L67/1021H04L67/2814
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,813,298
App. No.
15/284,084
Granted
Nov 7, 2017
Kind
B2
Abstract

Associations are maintained among a plurality of subnets, policies, and client types. Each subnet has an associated client type and policy. For a particular client device, (i) a client type of the particular client device, and (ii) a client type associated with the subnet on which the particular client device is hosted is determined. For the particular client device, (i) the determined client type of the particular client device with (ii) the determined client type associated with the subnet on which the particular client device is hosted is compared. Responsive to a determination that the client type of the particular client device matches the client type associated with the subnet that hosts the particular client device, a policy is applied to the particular client device.

Claims (52)

1. A method performed by a data apparatus, the method comprising:

maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types, wherein each subnet has an associated client type and an associated policy;

maintaining, for a particular client device, a log of traffic of the particular client device;

examining the log of traffic of the particular client device to determine a client type of the particular client device;

comparing, for the particular client device, (i) the determined client type of the particular client device with (ii) a client type associated with the subnet on which the particular client device is hosted determined from a configuration of at least the network or the subnets of the network or both; and

responsive to a determination that the client type of the particular client device does not match the client type associated with the subnet that hosts the particular client device, applying, to the particular client device, a corrective action, wherein the corrective action comprises maintaining the particular client device on a subnet of the network.

2. The method of claim 1 , wherein the corrective action further comprises one of the group consisting of generating an alert that identifies the particular client device, redirecting a request from the particular client device to a webpage, and blocking access to the subnet.

3. The method of claim 1 , wherein maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types comprises maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types and a plurality of parameters, wherein each client type has an associated parameter; and

wherein determining, for a particular client device, (i) a client type of the particular client device, and (ii) a client type associated with the subnet on which the particular client device is hosted comprises:

passively monitoring network traffic of the client devices;

examining a parameter of the passively monitored network traffic; and

comparing the parameter of the passively monitored network traffic with the associated parameters of the client types of the maintained associations.

4. The method of claim 3 , wherein the parameter of the passively monitored network traffic is a User-Agent header.

5. The method of claim 1 , wherein examining the log of traffic of the particular client device is performed on a regular basis.

6. The method of claim 5 , wherein the regular basis is time based.

7. The method of claim 5 , wherein the regular basis is event based.

8. The method of claim 5 , wherein the regular basis is based on system resources.

9. The method of claim 1 , wherein:

the network includes a first subnet and a second subnet;

stationary clients are associated with the first subnet;

bring-your-own-device clients are associated with the second subnet; and

a more restrictive policy is associated with the second subnet and a less restrictive policy is associated with the first subnet.

10. A non-transitory computer storage media encoded with computer program instructions that, when executed by one or more processors, cause a computer device to perform operation comprising:

maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types, wherein each subnet has an associated client type and an associated policy;

maintaining, for a particular client device, a log of traffic of the particular client device;

examining the log of traffic of the particular client device to determine a client type of the particular client device;

comparing, for the particular client device, (i) the determined client type of the particular client device with (ii) a client type associated with the subnet on which the particular client device is hosted determined from a configuration of at least the network or the subnets of the network or both; and

responsive to a determination that the client type of the particular client device does not match the client type associated with the subnet that hosts the particular client device, applying, to the particular client device, a corrective action, wherein the corrective action comprises maintaining the particular client device on a subnet of the network.

11. The computer storage media of claim 10 , wherein the corrective action further comprises one of the group consisting of generating an alert that identifies the particular client device, redirecting a request from the particular client device to a webpage, and blocking access to the subnet.

12. The computer storage media of claim 10 , wherein maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types comprises maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types and a plurality of parameters, wherein each client type has an associated parameter; and

wherein determining, for a particular client device, (i) a client type of the particular client device, and (ii) a client type associated with the subnet on which the particular client device is hosted comprises:

passively monitoring network traffic of the client devices;

examining a parameter of the passively monitored network traffic; and

comparing the parameter of the passively monitored network traffic with the associated parameters of the client types of the maintained associations.

13. The computer storage media of claim 10 , wherein examining the log of traffic of the particular client device is performed on a regular basis.

14. The computer storage media of claim 13 , wherein the regular basis is at least one of the group consisting of time based, event based, and based on system resources.

15. A system comprising:

one or more processors configured to execute computer program instructions; and

computer storage media encoded with computer program instructions that, when executed by one or more processors, cause a computer device to perform operation comprising:

maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types, wherein each subnet has an associated client type and an associated policy;

maintaining, for a particular client device, a log of traffic of the particular client device;

examining the log of traffic of the particular client device to determine a client type of the particular client device;

comparing, for the particular client device, (i) the determined client type of the particular client device with (ii) a client type associated with the subnet on which the particular client device is hosted determined from a configuration of at least the network or the subnets of the network or both; and

responsive to a determination that the client type of the particular client device does not match the client type associated with the subnet that hosts the particular client device, applying, to the particular client device, a corrective action, wherein the corrective action comprises maintaining the particular client device on a subnet of the network.

16. The system of claim 15 , wherein the corrective action further comprises one of the group consisting of generating an alert that identifies the particular client device, redirecting a request from the particular client device to a webpage, and blocking access to the subnet.

17. The system of claim 15 , wherein maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types comprises maintaining associations among a plurality of subnets of a network, a plurality of policies, and a plurality of client types and a plurality of parameters, wherein each client type has an associated parameter; and

wherein determining, for a particular client device, (i) a client type of the particular client device, and (ii) a client type associated with the subnet on which the particular client device is hosted comprises:

passively monitoring network traffic of the client devices;

examining a parameter of the passively monitored network traffic; and

comparing the parameter of the passively monitored network traffic with the associated parameters of the client types of the maintained associations.

18. The system of claim 15 , wherein examining the log of traffic of the particular client device is performed on a regular basis.

19. The system of claim 18 , wherein the regular basis is at least one of the group consisting of time based, event based, and based on system resources.

Assignments (6)
SUPPLEMENTAL INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 28, 2023
From: IBOSS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 066158/0266 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 28, 2023
From: IBOSS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 066158/0219 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY Recorded Dec 12, 2023
From: SILICON VALLEY BANK, A DIVISION OF FIRST-CITIZENS BANK TRUST COMPANY
To: IBOSS, INC.
Reel/Frame 066140/0480 →
SECURITY INTEREST Recorded Sep 19, 2022
From: IBOSS, INC.
To: SILICON VALLEY BANK
Reel/Frame 061463/0331 →
SECURITY INTEREST Recorded Dec 16, 2020
From: IBOSS, INC.
To: SILICON VALLEY BANK
Reel/Frame 054789/0680 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 8, 2017
From: MARTINI, PAUL MICHAEL
To: IBOSS, INC.
Reel/Frame 041510/0300 →
Continuity (4)
Continuation 15019727 · Feb 9, 2016
Continuation 14659357 · Mar 16, 2015
Continuation 14199616 · Mar 6, 2014
Related Publication 20170041193A1 · Feb 9, 2017