US2020410069A1PendingUtilityA1

Proactive security system based on code polymorphism

45
Assignee: KAMELEONSEC LTDPriority: Oct 15, 2018Filed: Sep 10, 2020Published: Dec 31, 2020
Est. expiryOct 15, 2038(~12.3 yrs left)· nominal 20-yr term from priority
G06F 2221/033G06F 21/14G06F 21/602G06F 21/54G06F 21/554
45
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A method, and processor for securing a host platform of a computing device are presented. The method includes generating, by a security processor, a first graph based on at least a portion of executable code, wherein the executable code is executed by a main processor of the host platform; generating a metadata file based on the generated first graph; polymorphing the executable code based on the generated metadata file; generating a second graph based on the polymorphed code; creating slices of the polymorphed code; executing at least one slices of the created slices by the security processor, wherein the security processor is apart from the main processor; polymorphing the at least one of executed slice; and pairing the least polymorphed slice with the polymorphed code.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method for securing a host platform of a computing device, comprising:
 generating, by a security processor, a first graph based on at least a portion of executable code, wherein the executable code is executed by a main processor of the host platform;   generating a metadata file based on the generated first graph;   polymorphing the executable code based on the generated metadata file;   generating a second graph based on the polymorphed code;   creating slices of the polymorphed code;   executing at least one slices of the created slices by the security processor, wherein the security processor is apart from the main processor;   polymorphing the at least one of executed slice; and   pairing the least polymorphed slice with the polymorphed code.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.