US5867647A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for securing compiled program code
Assignee: McAfee LLC
•
Filing: 1996-02-09
•
Granted: 1999-02-02
•
Expires: 2016-02-09
Abstract
Abstract A system and method of providing increased security for compiled program code. Compiled program code is installed in a computer having type enforcement capability. The compiled program code is allowed to execute and type enforcement violations are logged. The execution environment of the compiled program code is then modified to prevent recurrence of the logged type enforcement violations.
Inventors
- 👤 J. Thomas Haigh
- 👤 Andrew W. Jensen
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 15:26
CPC Classifications
H; H04; H04L; H04L63/00; H04L63/02; G; G06; G06F; G06F21/00; G06F21/50; G06F21/52; G06F9/00; G06F9/06; G06F9/46; G06F9/468; H04L63/04; H04L63/0428; H04L63/0435; H04L9/00; H04L9/40; G06F2221/00; G06F2221/21; G06F2221/2101
Claims Analysis
Total Claims: 17
Claim 1
Independent Claim
67 words
A method of providing increased security for compiled program code, comprising the steps of: installing the compiled program code in a computer; executing the compiled program code in the computer; logging type enforcement violations occurring during execution of the compiled program code; and modifying execution of the compiled program code in response to the logged type enforcement violations to prevent recurrence of the logged type enforcement violations.
Claim 2
Independent Claim
67 words
A method of providing increased security for compiled program code, comprising the steps of: installing the compiled program code in a computer; executing the compiled program code in the computer; logging type enforcement violations occurring during execution of the compiled program code; and modifying execution of the compiled program code in response to the logged type enforcement violations to prevent recurrence of the logged type enforcement violations.
Claim 3
Dependent Claim
36 words
The method according to claim 1, wherein the compiled program code executes within an execution environment and wherein the step of modifying execution of the compiled program code comprises the step of changing the execution environment.
Claim 4
Dependent Claim
45 words
The method according to claim 1, wherein the step of modifying execution of the compiled program code comprises the steps of: granting access permissions to processes generating the type enforcement violations; and reexecuting the compiled program code to determine if additional type enforcement violations occur.
Claim 5
Independent Claim
71 words
A method of adding additional levels of security to compiled program code, comprising the steps of: executing the compiled program code within a type enforcement environment, wherein the step of executing the compiled program code includes the step of checking each access by a process for type enforcement violations; and modifying operation of the compiled program code in response to the logged type enforcement violations to eliminate each type enforcement violation.
Claim 6
Independent Claim
71 words
A method of adding additional levels of security to compiled program code, comprising the steps of: executing the compiled program code within a type enforcement environment, wherein the step of executing the compiled program code includes the step of checking each access by a process for type enforcement violations; and modifying operation of the compiled program code in response to the logged type enforcement violations to eliminate each type enforcement violation.
Claim 7
Dependent Claim
32 words
The method according to claim 4, wherein the step of modifying operation of the compiled program code comprises the step of changing the environment within which the compiled program code is executing.
Claim 8
Dependent Claim
48 words
The method according to claim 5, wherein the step of changing the environment includes the steps of: defining a particular user; assigning type enforcement permissions on the access such that the access can only be performed by the particular user; and starting the process as that particular user.
Claim 9
Dependent Claim
29 words
The method according to claim 4, wherein the step of modifying operation of the compiled program code comprises the step of granting appropriate type enforcement permissions to the access.
Claim 10
Dependent Claim
64 words
The method according to claim 7, wherein the step of checking each access includes the step of generating a type enforcement violation when a process tries to access a data object having a type to which the process lacks access permission and wherein the step of granting appropriate type enforcement permissions includes the step of setting data object access permissions to permit the access.
Claim 11
Dependent Claim
68 words
The method according to claim 7, wherein the step of checking each access includes the step of generating a type enforcement violation when a first process tries to initiate a process to process communication to a second process to which the first process lacks access permission and wherein the step of granting appropriate type enforcement permissions includes the step of setting process interaction permissions to permit the communication.
Claim 12
Dependent Claim
64 words
The method according to claim 7, wherein the step of checking each access includes the step of generating a type enforcement violation when a first process tries to initiate a system environment access to which the first process lacks access permission and wherein the step of granting appropriate type enforcement permissions includes the step of setting system environment access permissions to permit the access.
Claim 13
Dependent Claim
87 words
The method according to claim 4, wherein the step of modifying operation of the compiled program code comprises the steps of: dividing the compiled program code into a plurality of processes, wherein the plurality of processes includes a plurality of first processes and a plurality of second processes; assigning the first processes to a first burb; assigning the second processes to a second burb; determining how the first and second processes interact between the first and second burbs; and granting type enforcement permissions to permit necessary interactions.
Claim 14
Dependent Claim
39 words
The method according to claim 11, wherein the step of determining includes the step of generating a type enforcement violation when a process operating in the first burb tries to access a data object assigned to the second burb.
Claim 15
Dependent Claim
46 words
The method according to claim 11, wherein the step of determining includes the step of generating a type enforcement violation when a first process operating in the first burb tries to initiate a process to process communication to a second process assigned to the second burb.
Claim 16
Dependent Claim
66 words
The method according to claim 13, wherein the step of granting appropriate type enforcement permissions includes the steps of: partially binding the first process to the first burb, wherein a partially bound process is a process which can interact with a specific burb without network separation restrictions; and giving the partially bound first process permission to initiate a process to process communication to the second process.
Claim 17
Dependent Claim
43 words
The method according to claim 11, wherein the step of determining includes the step of generating a type enforcement violation when a process operating in the first burb tries to initiate a system environment access to a process assigned to the second burb.
References Cited (Backward Citations)
US4177510A
Cited
US3956615A
Cited
US4104721A
Cited
US4442484A
Cited
US4648031A
Cited
US4870571A
Cited
US4584639A
Cited
US4621321A
Cited
US4701840A
Cited
US4713753A
Cited
US4885789A
Cited
US5093914A
Cited
US5204961A
Cited
US5303303A
Cited
US5153918A
Cited
US5263147A
Cited
US5272754A
Cited
US5228083A
Cited
US5355474A
Cited
US5305385A
Cited
EP0554182A1
Cited
US5276735A
Cited
US5359659A
Cited
US5414833A
Cited
WO1996013113A1
Cited
EP0743777A2
Cited
WO1997013340A1
Cited
WO1997016911A1
Cited
WO1997029413A2
Cited
US5684951A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-02-01 | 2002-08-03 | 2003-02-02 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-02-01 | 2006-08-03 | 2007-02-02 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-02-01 | 2010-08-03 | 2011-02-02 | $7700.00 | Window Closed / Lapsed |