Patent US5918018A successfully refreshed from Google Patents.
US5918018A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for achieving network separation
Assignee: McAfee LLC
•
Filing: 1996-02-09
•
Granted: 1999-06-29
•
Expires: 2016-02-09
Abstract
Abstract A system and method of achieving network separation within a computing system having a plurality of network interfaces. A plurality of burbs or regions is defined, wherein the plurality of burbs includes a first and a second burb and wherein each burb includes a protocol stack. Each of the plurality of network interfaces is assigned to one of the plurality of burbs and more than one network interface can be assigned to a particular burb. Processes are bound to specific burbs when they try to access that burb's protocol stack and communication between processes assigned to different burbs is restricted so that a communication between a process bound to one burb must pass through a proxy before being sent to a different burb.
Inventors
- 👤 Mark P. Gooderum
- 👤 Trinh Q. Vu
- 👤 Glenn Andreas
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-08 05:18
CPC Classifications
H; H04; H04L; H04L63/00; H04L63/02; H04L63/16; H04L63/166
Claims Analysis
Total Claims: 11
Claim 1
Independent Claim
216 words
A method of achieving network separation within a computing system having a plurality of network interfaces, including a first and a second network interface, the method comprising the steps of: defining a plurality of burbs, wherein the plurality of burbs includes a first and a second burb and wherein the first burb includes a fit protocol stack and the second burb includes a second protocol stack separate from the first protocol stack; assigning each of the plurality of network interfaces to one of the plurality of burbs, wherein more than one network interface can be assigned to a particular burb, wherein the step of assigning includes the steps of assigning the first network interface to the first burb and the second network interface to the second burb; binding processes to burbs; and restricting communication between processes bound to different burbs, wherein the of restricting communication between processes includes the steps of: examining a message received by the first network interface; and if the message is to be routed through the second network interface, routing the message up through the first protocol stack to a process bound to the first burb, transferring the message to a process bound to the second burb and routine the message down through the second protocol stack to the second network interface.
Claim 2
Independent Claim
216 words
A method of achieving network separation within a computing system having a plurality of network interfaces, including a first and a second network interface, the method comprising the steps of: defining a plurality of burbs, wherein the plurality of burbs includes a first and a second burb and wherein the first burb includes a fit protocol stack and the second burb includes a second protocol stack separate from the first protocol stack; assigning each of the plurality of network interfaces to one of the plurality of burbs, wherein more than one network interface can be assigned to a particular burb, wherein the step of assigning includes the steps of assigning the first network interface to the first burb and the second network interface to the second burb; binding processes to burbs; and restricting communication between processes bound to different burbs, wherein the of restricting communication between processes includes the steps of: examining a message received by the first network interface; and if the message is to be routed through the second network interface, routing the message up through the first protocol stack to a process bound to the first burb, transferring the message to a process bound to the second burb and routine the message down through the second protocol stack to the second network interface.
Claim 3
Dependent Claim
94 words
The method according to claim 1, wherein the step of restricting communication between processes includes the steps of: preventing a process from accessing burbs other than the burb to which the process is bound; limiting transfer of incoming packets such that incoming packets can only go to processes bound to the burb associated with the network interface the packet arrived on; defining a proxy; and ensuring that data passing from the first network interface to the second network interface must pass through the proxy before moving from the first burb to the second burb.
Claim 4
Dependent Claim
42 words
The method according to claim 1, wherein each burb has its own routing table and wherein the step of restricting communication includes the step of examining an incoming packet to determine if its destination is an address in the burb's routing table.
Claim 5
Dependent Claim
65 words
The method according to claim 1, wherein the step of restricting communication includes the steps of: defining a plurality of types; assigning each data object to one of the plurality of types, wherein the step of assigning data objects includes defining type enforcement rules for accesses by processes to said data objects; and applying a type enforcement check of accesses by processes to data objects.
Claim 6
Dependent Claim
110 words
A secure server, comprising: an operating system kernel; a plurality of network interfaces which communicate with the operating system kernel; and a plurality of burbs, including a first and a second burb; wherein each network interface is assigned to one burb from the plurality of burbs, wherein each burb includes a separate protocol stack for handling communication across the network interface, wherein each protocol stack is associated with only one burb, wherein a first protocol stack is associated with the first burb, and wherein communication from a process bound to the first burb must pass through the first protocol stack to a proxy before being sent to the second burb.
Claim 7
Dependent Claim
110 words
A secure server, comprising: an operating system kernel; a plurality of network interfaces which communicate with the operating system kernel; and a plurality of burbs, including a first and a second burb; wherein each network interface is assigned to one burb from the plurality of burbs, wherein each burb includes a separate protocol stack for handling communication across the network interface, wherein each protocol stack is associated with only one burb, wherein a first protocol stack is associated with the first burb, and wherein communication from a process bound to the first burb must pass through the first protocol stack to a proxy before being sent to the second burb.
Claim 8
Dependent Claim
40 words
The secure server according to claim 5, wherein each burb has its own routing table and wherein each burb further includes means for examining an incoming packet to determine if its destination is an address in the burb's routing table.
Claim 9
Dependent Claim
51 words
The secure server according to claim 5, wherein the operating system kernel includes type enforcing means for applying a type enforcement check of accesses by processes to data objects, wherein the type enforcing means includes type defining means for defining the modes and consequences of accesses by processes to data objects.
Claim 10
Dependent Claim
22 words
The secure server according to claim 5, wherein the operating system further includes a domain interaction table which enforces interactions between processes.
Claim 11
Dependent Claim
50 words
The method according to claim 2, wherein the step of preventing a process from accessing burbs other than the burb to which the process is bound includes the step of limiting each single user process to sending and receiving information from only one burb during the lifetime of that process.
References Cited (Backward Citations)
US4177510A
Cited
US3956615A
Cited
US4104721A
Cited
US4442484A
Cited
US4648031A
Cited
US4870571A
Cited
US4584639A
Cited
US4621321A
Cited
US4701840A
Cited
US4713753A
Cited
US4914568A
Cited
US4885789A
Cited
US5093914A
Cited
US5204961A
Cited
US5303303A
Cited
US5124984A
Cited
US5153918A
Cited
US5263147A
Cited
US5272754A
Cited
US5228083A
Cited
US5355474A
Cited
US5305385A
Cited
EP0554182A1
Cited
US5583940A
Cited
US5333266A
Cited
US5276735A
Cited
US5311593A
Cited
US5644571A
Cited
US5329623A
Cited
US5455828A
Cited
US5586260A
Cited
US5414833A
Cited
US5606668A
Cited
GB2287619A
Cited
US5511122A
Cited
US5530758A
Cited
US5615340A
Cited
US5485460A
Cited
US5604490A
Cited
US5548646A
Cited
WO1996013113A1
Cited
US5623601A
Cited
US5720035A
Cited
US5619648A
Cited
US5550984A
Cited
US5566170A
Cited
WO1996031035A1
Cited
US5699513A
Cited
WO1996035994A1
Cited
EP0743777A2
Cited
US5636371A
Cited
US5706507A
Cited
WO1997013340A1
Cited
US5689566A
Cited
US5671279A
Cited
WO1997026731A1
Cited
WO1997026734A1
Cited
WO1997026735A1
Cited
US5781550A
Cited
WO1997029413A2
Cited
US5684951A
Cited
US5673322A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-06-28 | 2002-12-28 | 2003-06-29 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-06-28 | 2006-12-28 | 2007-06-29 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-06-28 | 2010-12-28 | 2011-06-29 | $7700.00 | Window Closed / Lapsed |