Source code repair method for malicious code detection

Information security – Monitoring or scanning of software or data including attack... – Intrusion detection

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C726S022000

Reexamination Certificate

active

07640587

ABSTRACT:
A repair mechanism within a code management library system for repairing build code that is infected with malicious code. When a virus pattern is detected in a component of a source code, other components in the source code containing dependencies upon the first component are identified. This identification may be based on rules defined from relationships between the infected component and the other components in the source code. The component and the other components that are identified as having dependencies upon the infected component are retracted from the software product build. The infected component and the other identified components are then replaced with a previous archive of the code build. The software product build of the source code may then be performed.

REFERENCES:
patent: 5542045 (1996-07-01), Levine
patent: 6343376 (2002-01-01), Saxe et al.
patent: 6742006 (2004-05-01), Raduchel et al.
patent: 6792543 (2004-09-01), Pak et al.
patent: 7093239 (2006-08-01), van der Made
patent: 7398553 (2008-07-01), Li
patent: 2002/0116635 (2002-08-01), Sheymov
patent: 2002/0174137 (2002-11-01), Wolff et al.
patent: 2004/0015712 (2004-01-01), Szor
Engler et al., “Bugs as Deviant Behavior: A General Approach to Inferring Errors in Systems Code”, Computer Systems Laboratory, Stanford University, published in SOSP 2001, 2001.
Evans et al., “Improving Security Using Extensible Lightweight Static Analysis”, IEEE Software, 2002 IEEE, Jan./Feb. 2002, pp. 42-51.
“Automated Software Inspection” A New Approach to Increased Software Quality and Productivity, Reasoning Inc., Technical White Paper, 2003.
Kurowsky et al., “Trusting Software: Malicious Code Analyses”, U.S. Army CECOM Software Engineering Center, Fort Monmouth, NJ. , 1999.
“Why Application Security if the New Business Imperative—and How to Achieve It”, Secure Software, Inc., 2004.
“Trust, But Verify: How to Manage Risk in Outsourced Applications”, Security Topics White Paper, Ounce Labs, Inc., 2004.
U.S. Appl. No. 11/093,548, Fox et al., Source Code Management Method for Malicious Code Detection, filed Mar. 29, 2005.
U.S. Appl. No. 11/093,059, Fox et al., Source Code Classification Method for Malicious Code Detection, filed Mar. 29, 2005.

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Source code repair method for malicious code detection does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Source code repair method for malicious code detection, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Source code repair method for malicious code detection will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-4146504

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.