Patent Application
20160381051
This disclosure relates in general to the field of information security, and more particularly, to the detection of malware.
The field of network security has become increasingly important in today's society. The Internet has enabled interconnection of different computer networks all over the world. In particular, the Internet provides a medium for exchanging data between different users connected to different computer networks via various types of client devices. While the use of the Internet has transformed business and personal communications, it has also been used as a vehicle for malicious operators to gain unauthorized access to computers and computer networks and for intentional or inadvertent disclosure of sensitive information.
Malicious software (“malware”) that infects a host computer may be able to perform any number of malicious actions, such as stealing sensitive information from a business or individual associated with the host computer, propagating to other host computers, and/or assisting with distributed denial of service attacks, sending out spam or malicious emails from the host computer, etc. Hence, significant administrative challenges remain for protecting computers and computer networks from malicious and inadvertent exploitation by malicious software and devices.
To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
The FIGURES of the drawings are not necessarily drawn to scale, as their dimensions can be varied considerably without departing from the scope of the present disclosure.
In example embodiments, communication system 100 can be configured to monitor threads of a process and determine if a thread is trying to lookup a function that the process should already know. Generally, code that is a part of legitimate software or a legitimate application does not need to look for common functions to interact with the operating system because the common functions are available in published libraries and linked against export libraries and a dynamic link library (DLL) loader can resolve addresses automatically. However, malicious code often does not know the location of various function calls and the malicious code must first find the functions before it can execute. By marking certain files and regions related to system functions unreadable, the system can analyze what is reading the files and regions to locate the system function and make a determination if the code is trusted or malicious.
Elements of
For purposes of illustrating certain example techniques of communication system 100, it is important to understand the communications that may be traversing the network environment. The following foundational information may be viewed as a basis from which the present disclosure may be properly explained.
Malicious code 138 may be malware or malicious software that infects a host computer (e.g., electronic device 102) to perform any number of malicious actions, such as stealing sensitive information from a business or individual associated with the host computer, propagating to other host computers, and/or assisting with distributed denial of service attacks, sending out spam or malicious emails from the host computer, etc. One common malware feature is to use shellcode to exploit a vulnerability in software running on a machine. Shellcode is a piece of code used as the payload in the exploitation of the software vulnerability. It is called “shellcode” because it typically starts a command shell from which the attacker can control the compromised machine. Before the shellcode can effectively infect a machine, it needs to find OS functions or routines (e.g., LoadLibrary, CreateFile, etc.) to execute its payload. In order to find OS routines, the shell code can call GetProcAddress or parse portable executable (PE) headers to find and interpret DLLs' import and export tables. What is needed is a security solution that provides a system and method to detect the shellcode and identify malicious activity.
A communication system for the detection of malware, as outlined in
For example, system process monitoring module 128 can be configured to analyze code (e.g., from application 120) that is looking up OS functions (e.g., OS functions 122) and OS variables (e.g., OS variables 124). In a shared library of the system (e.g., shared library 126), only the structures that indicate where to find the OS functions or OS variables are made unreadable as there is no benefit in making the code unreadable. Areas of memory that may be protected and marked unreadable can include the import and export tables, DLL, PE files, etc.
Turning to the infrastructure of
In communication system 100, network traffic, which is inclusive of packets, frames, signals, data, etc., can be sent and received according to any suitable communication messaging protocols. Suitable communication messaging protocols can include a multi-layered scheme such as Open Systems Interconnection (OSI) model, or any derivations or variants thereof (e.g., Transmission Control Protocol/Internet Protocol (TCP/IP), user datagram protocol/IP (UDP/IP)). Additionally, radio signal communications over a cellular network may also be provided in communication system 100. Suitable interfaces and infrastructure may be provided to enable communication with the cellular network.
The term “packet” as used herein, refers to a unit of data that can be routed between a source node and a destination node on a packet switched network. A packet includes a source network address and a destination network address. These network addresses can be Internet Protocol (IP) addresses in a TCP/IP messaging protocol. The term “data” as used herein, refers to any type of binary, numeric, voice, video, textual, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another in electronic devices and/or networks. Additionally, messages, requests, responses, and queries are forms of network traffic, and therefore, may comprise packets, frames, signals, data, etc.
In an example implementation, electronic device 102, cloud services 104, and server 106 are network elements, which are meant to encompass network appliances, servers, routers, switches, gateways, bridges, load balancers, processors, modules, or any other suitable device, component, element, or object operable to exchange information in a network environment. Network elements may include any suitable hardware, software, components, modules, or objects that facilitate the operations thereof, as well as suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.
In regards to the internal structure associated with communication system 100, each of electronic device 102, cloud services 104, and server 106 can include memory elements for storing information to be used in the operations outlined herein. Each of electronic device 102, cloud services 104, and server 106 may keep information in any suitable memory element (e.g., random access memory (RAM), read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), application specific integrated circuit (ASIC), etc.), software, hardware, firmware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element. Moreover, the information being used, tracked, sent, or received in communication system 100 could be provided in any database, register, queue, table, cache, control list, or other storage structure, all of which can be referenced at any suitable timeframe. Any such storage options may also be included within the broad term ‘memory element’ as used herein.
In certain example implementations, the functions outlined herein may be implemented by logic encoded in one or more tangible media (e.g., embedded logic provided in an ASIC, digital signal processor (DSP) instructions, software (potentially inclusive of object code and source code) to be executed by a processor, or other similar machine, etc.), which may be inclusive of non-transitory computer-readable media. In some of these instances, memory elements can store data used for the operations described herein. This includes the memory elements being able to store software, logic, code, or processor instructions that are executed to carry out the activities described herein.
In an example implementation, network elements of communication system 100, such as electronic device 102, cloud services 104, and server 106 may include software modules (e.g., security module 118, system process monitoring module 128, and network security module 134) to achieve, or to foster, operations as outlined herein. These modules may be suitably combined in any appropriate manner, which may be based on particular configuration and/or provisioning needs. In example embodiments, such operations may be carried out by hardware, implemented externally to these elements, or included in some other network device to achieve the intended functionality. Furthermore, the modules can be implemented as software, hardware, firmware, or any suitable combination thereof. These elements may also include software (or reciprocating software) that can coordinate with other network elements in order to achieve the operations, as outlined herein.
Additionally, each of electronic device 102, cloud services 104, and server 106 may include a processor that can execute software or an algorithm to perform activities as discussed herein. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein. In one example, the processors could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an EPROM, an EEPROM) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof. Any of the potential processing elements, modules, and machines described herein should be construed as being encompassed within the broad term ‘processor.’
Electronic device 102 can be a network element and includes, for example, desktop computers, laptop computers, mobile devices, personal digital assistants, smartphones, tablets, or other similar devices. Cloud services 104 is configured to provide cloud services to electronic device 102. Cloud services may generally be defined as the use of computing resources that are delivered as a service over a network, such as the Internet. Typically, compute, storage, and network resources are offered in a cloud infrastructure, effectively shifting the workload from a local network to the cloud network. Server 106 can be a network element such as a server or virtual server and can be associated with clients, customers, endpoints, or end users wishing to initiate a communication in communication system 100 via some network (e.g., network 108). The term ‘server’ is inclusive of devices used to serve the requests of clients and/or perform some computational task on behalf of clients within communication system 100. Although security module 118 is represented in
Turning to
If application is malicious or includes malicious code 138, before shellcode 146 can effectively infect a machine, it needs to find operating system functions or routines (e.g., example LoadLibrary, CreateFile, etc.) to execute its payload. In order to find OS routines, the shell code can call GetProcAddress 148 or parse to look for PE headers from PE files 144 to find and interpret DLLs' or import and export tables 142. For example, when DLL 140 exports some functions to a process, the information about the start of the function can be found as well as the name of the function. The name of the function can be stored in import and export tables 142 which are pointed to by well know structures at the beginning of DLL 140. Whitelist 122 can include entries of known clean or trusted applications, code, strings, etc. and can be used to reduce false positives. Blacklist 124 can include entries of known malicious or untrusted applications, code, strings, etc.
Turning to
Turning to
As illustrated in
Processors 570 and 580 may also each include integrated memory controller logic (MC) 572 and 582 to communicate with memory elements 532 and 534. Memory elements 532 and/or 534 may store various data used by processors 570 and 580. In alternative embodiments, memory controller logic 572 and 582 may be discreet logic separate from processors 570 and 580.
Processors 570 and 580 may be any type of processor and may exchange data via a point-to-point (PtP) interface 550 using point-to-point interface circuits 578 and 588, respectively. Processors 570 and 580 may each exchange data with a chipset 590 via individual point-to-point interfaces 552 and 554 using point-to-point interface circuits 576, 586, 594, and 598. Chipset 590 may also exchange data with a high-performance graphics circuit 538 via a high-performance graphics interface 539, using an interface circuit 592, which could be a PtP interface circuit. In alternative embodiments, any or all of the PtP links illustrated in
Chipset 590 may be in communication with a bus 520 via an interface circuit 596. Bus 520 may have one or more devices that communicate over it, such as a bus bridge 518 and I/O devices 516. Via a bus 510, bus bridge 518 may be in communication with other devices such as a keyboard/mouse 512 (or other input devices such as a touch screen, trackball, etc.), communication devices 526 (such as modems, network interface devices, or other types of communication devices that may communicate through a computer network 560), audio I/O devices 514, and/or a data storage device 528. Data storage device 528 may store code 530, which may be executed by processors 570 and/or 580. In alternative embodiments, any portions of the bus architectures could be implemented with one or more PtP links.
The computer system depicted in
Turning to
In this example of
ARM ecosystem SOC 600 may also include a subscriber identity module (SIM) I/F 630, a boot read-only memory (ROM) 635, a synchronous dynamic random access memory (SDRAM) controller 640, a flash controller 645, a serial peripheral interface (SPI) master 650, a suitable power control 655, a dynamic RAM (DRAM) 660, and flash 665. In addition, one or more example embodiments include one or more communication capabilities, interfaces, and features such as instances of Bluetooth™ 670, a 3G modem 675, a global positioning system (GPS) 680, and an 802.11 Wi-Fi 685.
In operation, the example of
Processor core 700 can also include execution logic 714 having a set of execution units 716-1 through 716-N. Some embodiments may include a number of execution units dedicated to specific functions or sets of functions. Other embodiments may include only one execution unit or one execution unit that can perform a particular function. Execution logic 714 performs the operations specified by code instructions.
After completion of execution of the operations specified by the code instructions, back-end logic 718 can retire the instructions of code 704. In one embodiment, processor core 700 allows out of order execution but requires in order retirement of instructions. Retirement logic 720 may take a variety of known forms (e.g., re-order buffers or the like). In this manner, processor core 700 is transformed during execution of code 704, at least in terms of the output generated by the decoder, hardware registers and tables utilized by register renaming logic 710, and any registers (not shown) modified by execution logic 714.
Although not illustrated in
Note that with the examples provided herein, interaction may be described in terms of two, three, or more network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that communication system 100 and its teachings are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of communication system 100 as potentially applied to a myriad of other architectures.
It is also important to note that the operations in the preceding flow diagrams (i.e.,
Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. Moreover, certain components may be combined, separated, eliminated, or added based on particular needs and implementations. Additionally, although communication system 100 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture, protocols, and/or processes that achieve the intended functionality of communication system 100
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.
Example C1 is at least one machine readable medium having one or more instructions that when executed by at least one processor, cause the at least one processor to monitor a process, determine if the process is parsing to look for one or more system functions, and flag the process if the process is parsing to look for one or more system functions.
In Example C2, the subject matter of Example C1 can optionally include where the process is determined to be parsing to look for one or more system functions if the process parses portable executable headers to find and interpret dynamic link library tables.
In Example C3, the subject matter of any one of Examples C1-C2 can optionally include where the process is determined to be parsing to look for one or more system functions if the process calls GetProcAddress.
In Example C4, the subject matter of any one of Examples C1-C3 can optionally include where the process includes shellcode.
In Example C5, the subject matter of any one of Examples C1-C4 can optionally include where the one or more instructions that when executed by the at least one processor, further cause the at least one processor to analyze the process for malware.
In Example C6, the subject matter of any one of Example C1-C5 can optionally include where the one or more instructions that when executed by the at least one processor, further cause the at least one processor to remove the flag if the process is found in a whitelist.
In Example A1, an apparatus can include a system process monitoring module. The system process monitoring module can be configured to monitor a process, determine if the process is parsing to look for one or more system functions, and flag the process if the process is parsing to look for one or more system functions.
In Example, A2, the subject matter of Example A1 can optionally include where the process is determined to be parsing to look for one or more system functions if the process parses portable executable headers to find and interpret dynamic link library tables.
In Example A3, the subject matter of any one of Examples A1-A2 can optionally include where the process is determined to be parsing to look for one or more system functions if the process calls GetProcAddress.
In Example A4, the subject matter of any one of Examples A1-A3 can optionally include where the process includes shellcode.
In Example A5, the subject matter of any one of Examples A1-A4 can optionally include where the system process monitoring module is further configured to analyze the process for malware.
In Example A6, the subject matter of any one of Examples A1-A5 can optionally include where the system process monitoring module is further configured to remove the flag if the process is found in a whitelist.
Example M1 is a method including monitoring a process, determining if the process is parsing to look for one or more system functions, and flagging the process if the process is parsing to look for one or more system functions.
In Example M2, the subject matter of Example M1 can optionally include where the process is determined to be parsing to look for one or more system functions if the process parses portable executable headers to find and interpret dynamic link library tables.
In Example M3, the subject matter of any one of the Examples M1-M2 can optionally include where the process is determined to be parsing to look for one or more system functions if the process calls GetProcAddress.
In Example M4, the subject matter of any one of the Examples M1-M3 can optionally include where the process includes shellcode.
In Example M5, the subject matter of any one of the Examples M1-M4 can optionally include analyzing the process for malware.
Example S1 is a system for detecting malware, the system can include a system process monitoring module. The system process monitoring module can be configured for monitoring a process, determining if the process is parsing to look for one or more system functions, and flagging the process if the process is parsing to look for one or more system functions.
In Example S2, the subject matter of Example S1 can optionally include where the process is determined to be parsing to look for one or more system functions if the process parses portable executable headers to find and interpret dynamic link library tables.
In Example S2, the subject matter of any one of Examples S1 and S2 can include where the process is determined to be parsing to look for one or more system functions if the process calls GetProcAddress.
Example X1 is a machine-readable storage medium including machine-readable instructions to implement a method or realize an apparatus as in any one of the Examples A1-A6, or M1-M5. Example Y1 is an apparatus comprising means for performing of any of the Example methods M1-M5. In Example Y2, the subject matter of Example Y1 can optionally include the means for performing the method comprising a processor and a memory. In Example Y3, the subject matter of Example Y2 can optionally include the memory comprising machine-readable instructions.
