Control the installation of unauthorized drivers on your computer system
By intercepting file opening requests in the server kernel processing system and using the whitelist mechanism to block unauthorized operations, the security threat of malicious drivers and whitelist modification in the data center is solved, and effective protection of data and whitelists is achieved.
Patent Information
- Application Number
- CN201980065838.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-10-08
- Filing Date
- 2019-09-24
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-09-24
AI Technical Summary
There are security threats for malicious drivers and whitelist modifications in the data center, and the existing technology is difficult to effectively prevent the installation of malicious code and the tampering of whitelists.
Intercept file opening requests in the server kernel processing system, determine whether the target file is an authorized driver file through the whitelisting mechanism, and store whitelists in the protected volume to prevent unauthorized file opening operations.
It effectively prevents malicious driver installation and whitelist tampering, significantly enhances the security of the data center, and ensures data and whitelist protection.
Smart Images

Figure CN112805700B_ABST
Abstract
Description
Background Art
[0001] Computer systems are currently in widespread use. Some of these computer systems include data centers.
[0002] Data centers consist of large groups of networked computer servers that can be used in a variety of different ways. Businesses or other organizations often use them to store, process, and disseminate large amounts of information.
[0003] Some data centers also host or serve applications such as email applications, instant messaging applications, e-commerce transactions, and a variety of other applications. Similarly, some data centers can store and provide websites for users who visit the data center.
[0004] It is not uncommon for multiple different organizations to use resources on a single data center. Such a data center may include a large number of different servers that provide the desired access.
[0005] Data security of data in a data center is widely considered an important feature. Different degrees of security can be achieved by using various forms of data encryption and various forms of authentication.
[0006] The above discussion is provided for general background information only and is not intended to be used as an aid in determining the scope of the claimed subject matter. Summary of the invention
[0007] The server kernel processing system receives an input / output (I / O) request from a user mode computing environment. The I / O request is analyzed to determine whether it is a file open request. If so, the target analysis logic determines whether the file open request is for a driver file or for a file in a protected volume storing a driver whitelist file. If the file open request is for a file stored in a protected volume, the request is blocked. If the file open request is for a driver file, the driver whitelist file is checked to determine whether the target driver is on the whitelist. If not, the file open request is also blocked.
[0008] This Summary is provided to introduce some concepts in a simplified form that are further described in the Detailed Description below. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the Background. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1 is a block diagram of an example of a computing system architecture.
[0010] Figure 2is shown in more detail Figure 1 A block diagram of one example of portions of a computing system architecture is shown.
[0011] Figure 3 is shown in more detail Figure 1 A block diagram of another example of portions of a computing system architecture is shown.
[0012] Figure 4 is a flow chart illustrating one example of the operation of a server core processing system in processing input / output (I / O) requests.
[0013] Figure 5 It shows the deployment of cloud computing architecture Figure 1 A block diagram of the architecture shown.
[0014] Figure 6 is a block diagram illustrating one example of a computing environment that may be used in accordance with the architecture shown in the previous figures. DETAILED DESCRIPTION
[0015] Figure 1 is a block diagram of one example of a computing system architecture 100. Architecture 100 illustrates a data center computing system 102 that may be accessed over a network 112 by a plurality of users 104-106 using user devices 108-110. Figure 1 Also shown is that an administrator or engineer 114 can access data center computing system 102 using administrator / engineer device 116. Administrator / engineer 114 can access computing system 102 directly as shown by arrow 118, or through network 112 as shown by arrow 120.
[0016] exist Figure 1 In the illustrated example, user devices 108-110 are shown generating user interfaces 122-124 for interaction by users 104-106, respectively. Users 104-106 interact with their respective user interfaces 122-124 to control and manipulate corresponding user devices 108-110 and portions of data center computing system 102.
[0017] Similarly, device 116 is shown generating interface 126 for interaction by user 114. User 114 illustratively interacts with interface 126 to control and manipulate device 116 and certain portions of data center computing system 102. Users 104-106 illustratively access resources provided by data center computing system 102, such as data storage, hosted services, and other resources.
[0018] The network 112 may be any of a variety of different types of networks. For example, it may be a wide area network, a local area network, a near field communication network, a cellular network, or any of a variety of other networks or network combinations.
[0019] Administrator / engineer 114 illustratively performs administrative or engineering operations on data center computing system 102. Thus, user 114 may access certain portions of data center computing system 102 to perform maintenance operations, deploy code to fix bugs, deploy new features, or perform other operations. To do so, user 114 is often provided with authentication information or security credentials that allow him or her to access portions of computing system 102 that would otherwise be inaccessible.
[0020] Figure 1 As shown, in one example, data center computing system 102 illustratively includes front-end functionality 130, server system 132, data storage system 134, and it may include a variety of other data center functionality 136. Server system 132 includes a plurality of different server machines 138-140. Data storage system 134 illustratively includes a plurality of different data storage devices 142-144.
[0021] Briefly, in operation, the front-end function 130 illustratively receives requests from various users 104-106 using resources and services hosted by the data center computing system 102, and provides these requests to the server system 132. The server machines 138-140 illustratively process the requests so that the users 104-106 can manipulate or access data stored in the data storage system 134 and, in particular, on the different data storage devices 142-144. The results of the requests received by the front-end function 130 may be returned to the front-end function 130 by the server system 132. The front-end function 130 may then return the results of the requested operation to the user who requested it.
[0022] There are many different types of security systems or techniques that may be deployed to protect data and other items in the data center computing system 102. For example, users 104-106 may be required to provide authentication information in order to access different information. Similarly, administrator / engineer user 114 may be required to provide certain security credentials. In addition, in the event that user 114 wishes to deploy code on the data center computing system 102, user 114 may be required to sign, authenticate, or verify the code before the code can be deployed to the data center computing system 102.
[0023] As an example, a user 104 may provide an input / output (I / O) request to perform certain operations on data stored in a data storage device 142. An engineering user 114 may deploy a piece of code to a kernel of a server machine 138 that is intended to perform the operation when the I / O request is executed. In one example, the logic deployed by the engineering user 114 may perform management operations on the I / O request, such as creating a file, opening a file or document, closing a file, deleting a file, enumerating files, reading and writing file data, and the like.
[0024] As a specific example, where the data in the data storage devices 142-144 is arranged according to file systems and directories, the code deployed by the user 114 to help manage I / O operations can be referred to as a filter driver. The filter driver is attached to a memory volume or file system and is loaded into the driver stack corresponding to the volume or file system. When an I / O request is received for the volume or file system, the filter driver is forwarded to the correct file system or volume by the I / O management logic.
[0025] The driver stack attached to the file system or volume includes drivers loaded for the corresponding file system or volume, and I / O requests are provided to the drivers in the driver stack. These drivers may include filter drivers that can modify the behavior of the file system to which they are attached when responding to I / O requests. Filter drivers are kernel mode components, which means that they are executed by the kernel computing system for a specific server machine. The kernel computing system executes a kernel program as part of the operating system, which manages I / O requests from client mode components (such as applications). The kernel is loaded when the computing system starts and can manage the remaining startup operations.
[0026] It should be understood that although some examples are described herein with respect to the information in the data storage devices 142-144 being arranged as files in a file system hierarchy or directory, this need not be the case. On the contrary, they may also be stored in other ways. Similarly, although some parts of this specification continue with respect to file system drivers, driver stacks, etc., these do not need to be used either. In other examples, instead of a file system driver (or filter driver) in a driver stack corresponding to a file system, the operation may be performed by data access code resident in a data access system, which receives an I / O request from a user mode component and processes it in the kernel of a server machine without using a "driver," "filter driver," etc. On the contrary, the code is executed only as a separate component in a data access system. Different types of examples will be described herein. They are only considered as examples, without limiting the scope of this discussion.
[0027] Regardless of the specific configuration of architecture 100, an administrative or engineering user 114 may wish to perform malicious operations on a data center computing system 102. Because user 114 has credentials to sign or otherwise authenticate a driver or other data access logic on data center computing system 102, user 114 may, in some cases, deploy a malicious driver or another piece of malicious data access code to data center computing system 102. Computing system 102 may not recognize it as malicious code because it may contain the appropriate signature or other authentication information.
[0028] Therefore, as described below, the present specification describes a server kernel processing system in the kernel of the server machine 138-140 that reduces the likelihood of this happening. In order to deploy or install a piece of code (whether a driver or another piece of data access code) on the data center computing system 102, the code is provided as a file, and the file must be opened before the file is deployed or installed. Therefore, in one example, as described below, the present specification modifies the kernel of the server machine 138-140 so that they include a system that intercepts all file open calls and determines whether the file open call points to a driver file. If so, the identity of the driver file is compared to a whitelist mechanism (e.g., a whitelist file) that contains entries that identify authorized driver files. If the target driver file (the driver file to be opened) is not on the whitelist, the file open call is blocked.
[0029] This specification also continues for a system that protects a whitelist in the same manner. The whitelist will be illustratively stored in a protected volume on one of the data storage devices 142-144. Therefore, if a user 114 attempts to modify the whitelist to include an entry for a malicious driver or other file to be installed, the I / O operation will use the whitelist as the target file to be opened. Therefore, this specification provides a system that determines whether to perform a file open operation on a file in a protected volume. If so, the file open operation is blocked again. Therefore, this system protects the data stored in the data storage system 134 from being destroyed by a malicious driver (because the installation of the malicious driver will not be allowed), and it also protects the whitelist in the same manner (because the whitelist will be stored in a protected volume, and at this, no file open operation is performed except for the system itself).
[0030] Figure 2 yes Figure 1 A more detailed block diagram of an example of a portion of the computing system architecture 100 is shown. Some items related to Figure 1 are similar and are similarly numbered. Figure 2In the example shown, the application or other user mode logic 150 resides in a user mode computing environment 152 (which may be in one of the user devices 108-110 or in another location). The application / other user mode logic 150 generates I / O requests 154 that are provided to the server machine 138 via the front end functionality 130. Figure 2 In the example shown, the server machine 138 includes a server core processing system 156 and may include a variety of other server functions. The server core processing system 156 processes the I / O request 154 and, if authorized, accesses data on one of the data storage devices 142. As shown in block 158, the data may be stored in a file system or in another data volume. The data to be accessed may include a whitelist file 160, a driver file 162, or a variety of other information 164.
[0031] exist Figure 2 In the example shown, the server kernel processing system 156 illustratively includes one or more processors 166, data access logic 168, I / O manager logic 170, and may include a variety of other kernel functions 172. The data access logic 168 may include I / O call type identifier logic 174, call interception logic 176, target analysis logic 178, call blocking logic 180, and may include a variety of other data access functions 182. In the example shown, the call interception logic 176 includes target file type identifier logic 184, target volume identifier logic 186, and may include other items 188. The target analysis logic 178 may include driver / whitelist comparison and protection logic 190, target volume analysis logic 192, and may include other items 194.
[0032] In operation, the application / logic 150 may generate an I / O request 154 as a file open request, a file write request, a read request, a file create request, a file delete request, or a variety of other requests that may be issued to access information on the data storage device 142. It should be noted that all of these requests and other requests are aggregated into a file open request, so the protection discussed herein applies to all of these file I / O operations (or requests). The front-end function 130 illustratively discloses an interface for receiving the request 154 and provides the request to the I / O manager logic 170. There may be various different instances of the data access logic 168 on the server machine 138. The I / O manager logic 170 routes the I / O request 154 to an appropriate set of data access logic 168 for processing. When the data access logic 168 receives the I / O request 154, the I / O call type identifier logic 174 identifies the type of call (or I / O request) being made. For example, as described above, it may be a file open request, a create request, a read request, a write request, etc.
[0033] In one example, if the I / O request is a file open request to open a target file, the target file type identifier logic 184 determines which file type the target is. As an example, the file can be a driver file (or similar file). The target volume identifier logic 186 also identifies the target volume (or storage location) where the target file is located.
[0034] The target analysis logic 178 then analyzes the target to be accessed to determine whether the file open call should be blocked. For example, if the target file has been identified as a driver file by logic 184, the driver / white list comparison and protection logic 190 accesses the white list 160, which contains a list of all authorized drivers that are authorized to be installed on the data center (or at least on the server machine 138). If the target file (e.g., the target driver file to be opened) is identified as an authorized driver file on the white list 160, the target analysis logic 178 generates an authorization output indicating that the driver is authorized, and the target driver file 162 can be opened.
[0035] However, if the comparison and protection logic 190 determines that the target driver file is not identified as an authorized driver file on the whitelist 160, it generates an unauthorized output indicating this, and the I / O operation (or file open call) is blocked by the call blocking logic 180. The logic 180 may return a message to the calling user mode component. It may provide a message to a security engineer or other person, or may also perform other actions.
[0036] In this way, if the engineering user 114 obtains a valid signature on a malicious driver, the corresponding driver file must be opened when attempting to install the driver. However, if the corresponding driver file is not authorized (because it is not identified on the white list 160), the file open call to open the target driver file will be blocked and it will not be opened. Therefore, it cannot be installed. This prevents malicious activities that the driver file would otherwise perform.
[0037] However, the engineering user 114 may wish to access the whitelist 160 to add an entry identifying a malicious driver file in order to bypass the security performed by the data access logic 168. Therefore, if the target file type identifier logic 184 determines that the target file of the file open request is not a driver file, the target volume identifier logic 186 identifies the storage volume (or memory location) where the target file is stored. In one example, the whitelist 160 will be stored in a protected volume (or in multiple protected memory locations).
[0038] The target volume analysis logic 192 then determines whether the location of the file to be opened is stored in a protected volume (or multiple protected memory locations). If the target file is within the multiple protected locations (which will include the white list 160), the logic 192 provides an output indicating this to the call blocking logic 180, and the call blocking logic 180 blocks the I / O request (or file open call). In this way, the engineering user 114 is prohibited from modifying the white list 160 to include the identifier of the malicious driver that the user 114 attempted to install. Therefore, the same mechanism (data access logic 168) can prevent both the installation of malicious drivers and access to the white list 160.
[0039] Figure 3 is a block diagram illustrating another example of architecture 100. Some items related to Figure 1 and Figure 2 are similar and are similarly numbered. Figure 3 In the example shown, data is stored in data storage devices 142-144 in various file systems. Thus, data storage device 142 is shown as storing a file system / volume containing a whitelist. This is indicated by box 200. It may also store other items 202. Data storage device 144 is shown as storing a file system / volume containing one or more driver files. This is indicated by box 204. Device 144 may also store other items 206.
[0040] exist Figure 3In the example shown, data access logic 168 includes a file system / volume driver stack 208 and a storage driver stack for a target file system / volume that is the target of I / O request 154. The storage driver stack for the target file system or volume is indicated by box 210.
[0041] There may be multiple different driver stacks attached to different file systems or volumes. Thus, when an I / O request 154 is received, the I / O manager logic 170 identifies the specific file system or volume that is the subject of the I / O request and forwards the I / O request to the driver stack attached to that file system or volume. Figure 3 In the example shown, the I / O manager logic 170 forwards the I / O request 154 to the file system / volume driver stack 208. The driver stack 208 can include a variety of different drivers. Some file system drivers or driver logic are indicated by box 212. It can also include a filter driver that modifies the I / O request or performs processing on the received I / O request. In some cases, a filter driver logic is shared between different filter drivers. In this case, the filter manager logic 214 can support multiple different mini filter drivers 216-218. The logic 214 includes the common functions of the mini filter drivers supported by the filter manager logic 214. The mini filter drivers 216-218 themselves include additional logic to perform different filtering steps. The location of the filter driver (e.g., the mini filter driver 216-218 in other file system drivers 212 in the driver stack 208) can be specified, or can be determined based on the order in which the drivers are loaded.
[0042] The file system / volume driver stack 208 receives the I / O request and passes it to the filter manager logic 214. The filter manager logic 214 illustratively receives the I / O request and provides the I / O request in an order determined by its order in the stack 208 for operation by the mini-filter drivers 216-218. Once the mini-filter drivers 216-218 attached to the filter manager logic 214 have acted on the I / O request 154, the results can be provided to the other file system driver logic 212. The resulting I / O request (after all filter drivers and mini-filter drivers in the stack 208 have acted on it) is then provided to the storage driver stack for the specific data storage device 142-144 where the target file is located. For example, if the I / O request is to operate on a file within the data storage device 142, the I / O request is provided from the driver stack 208 to the storage driver stack for the storage device 142. This is an example only.
[0043] exist Figure 3 In the example shown, a minifilter driver 216 is provided to determine whether the I / O request 154 is a file open request for a driver file. If so, the minifilter driver 216 accesses the whitelist in the data storage device 142 to determine whether the target driver file is authenticated by the whitelist. If not, the minifilter driver 216 prevents the file open request (I / O request 154) from being executed. However, if the target driver file is on the whitelist, the minifilter driver 216 provides an authorization output indicating that the operation can be performed.
[0044] Then, the minifilter driver 218 (if the minifilter driver 216 determines that the target file is not a driver file) determines whether the target file (which is the subject of the I / O request 154) resides in a protected volume. If so, the minifilter driver 218 prevents the I / O request from being executed. It should also be noted that a single minifilter driver can also perform several of these operations. For example, a single minifilter driver can check to see if the target is a driver file and whether the target resides in a protected volume. This is just one example.
[0045] In this way, the minifilter driver 216 ensures that users cannot install malicious drivers. Similarly, the minifilter driver 218 ensures that users cannot modify the whitelist.
[0046] Figure 4 FIG. 1 is a diagram illustrating the operation of data access logic 168 in determining whether I / O request 154 attempts to open a driver file. Figure 3 and Figure 4 154) in which the driver file is not identified on the whitelist or the I / O request 154 attempts to open a file in a protected volume (e.g., attempts to open and modify the whitelist). First, assume that the server kernel is running in the server kernel processing system 156. This is Figure 4 It is also assumed that the kernel also has data access logic. This is indicated by box 252. In one example, the data access logic can be similar to Figure 2 , where it can access data stored in a flat file system, or access data based on a hierarchical directory, or access data in other ways. In another example, the data access logic 168 can be similar to Figure 3154 and modify the operation of the kernel in response to different I / O requests. The driver stack may include a filter driver, a mini filter driver, or a variety of other drivers. This is indicated by box 254.
[0047] The data access logic may also take a variety of other forms. This is indicated by block 256. Figure 2 and Figure 3 Those shown are shown for exemplary purposes only.
[0048] The data access logic 168 then receives the I / O request 154 from the user mode computing environment 152. Figure 4 The I / O request 154 may come from an application or other user mode logic 150. Receiving an I / O request 154 from a user mode application is indicated by block 260. Receiving an I / O request 154 from other user mode logic is indicated by block 262.
[0049] Once an I / O request 154 is received, the data access logic 168 determines the type of I / O request. Figure 2 In the I / O call type identifier logic 174, the I / O request is determined whether the I / O request is a file open request, a file open / write request, etc. Figure 3 In the example of FIG. 1 , a minifilter driver 216-218 or other file system driver may make this determination. The type of I / O request 154 is identified by Figure 4 , as indicated by block 264 in the flowchart of FIG.
[0050] If the request is not a file open request, then as shown in block 266, the data access logic 168 performs any other operations on the I / O request and then passes it to the data storage device so that it can be executed. Figure 4 268 in the flowchart of FIG.
[0051] However, if it is determined at block 266 that the I / O request 154 is a file open request, the data access logic 168 determines whether the target file (as the target of the file open request) is a driver file. Figure 4 270 in the flowchart of FIG.
[0052] If it is determined at block 270 that the target file (of the file open request) is indeed a driver file, then the data access logic 168 accesses a whitelist that includes entries identifying driver files that are authorized on the server machine. The access whitelist mechanism is provided by Figure 4, as indicated by block 272 in the flowchart of . In one example, the target file type identifier logic 184 identifies the target file (to see if it is a driver), and the driver / whitelist comparison and protection logic 190 determines whether the target driver file is identified on the whitelist. In another example, the minifilter drivers 216-218 identify the type of the target file to determine if it is a driver, and if so, access the whitelist to determine whether the target driver file is identified on the whitelist.
[0053] If it is determined at box 274 that the target driver file is not on the whitelist, the data access logic 168 blocks the file open request so that the request cannot be executed. This is indicated by box 276. In this way, if a secret user attempts to install a malicious driver, the action will be blocked.
[0054] If it is determined at block 274 that the target driver file that is the subject of the file open request is in fact identified as an authorized driver on the whitelist, then the data access logic 168 provides the I / O request 154 to any other processing logic for executing the I / O request 154. Execution of the file open request (after determining that the target driver file is on the whitelist) is performed at block 274. Figure 4 This is indicated in block 278 of the flowchart of FIG.
[0055] Returning to block 270, if it is determined that the target file is not a driver file, the data access logic 168 determines whether the target file is in a protected volume (or multiple protected memory locations) on the data storage device 142-144. For example, a malicious user may attempt to modify a whitelist stored in a protected volume. Determining whether the target file is a driver whitelist file in a protected volume is performed by Figure 4 If so, the process proceeds to block 276 again, where the I / O request 154 is blocked so that the file in the protected volume cannot be opened and / or otherwise modified.
[0056] If it is determined at box 280 that the target file is not a driver whitelist file in a protected volume, processing proceeds to box 278, where the data access logic 168 performs any other operations on the I / O request 154 that are needed to execute the I / O request 154 or submit the I / O request 154 for further processing.
[0057] Therefore, it can be seen that the present specification greatly enhances the security of the computing system itself. It intercepts all file open requests for system files and determines whether the target file is a driver. If so, it allows the file open request to proceed only if the whitelist mechanism authorizes the driver. If not, the file open request is blocked. Similarly, even if the file open request does not point to a driver file, the system will determine whether the target file is in a protected volume (e.g., a whitelist). If so, the I / O request will be blocked again, making it impossible to modify the whitelist. By using the same mechanism to protect the system from installing malicious drivers and modifying the whitelist, the mechanism is not only effective, but also provides a significantly enhanced level of security.
[0058] It should be noted that various systems, components and / or logic have been described in the above-discussed parts herein. It should be understood that such systems, components and / or logic may include hardware items (such as processors and associated memory or other processing components, some of which are described below) that perform functions associated with these systems, components and / or logic. In addition, as described below, these systems, components and / or logic may include software that is loaded into a memory and subsequently executed by a processor or server or other computing component. These systems, components and / or logic may also include different combinations of hardware, software, firmware, etc., some examples of which are described below. These are only some examples of different structures that may be used to form the above-mentioned systems, components and / or logic. Other structures may also be used.
[0059] This discussion refers to processors and servers. In one embodiment, processors and servers include computer processors with associated memory and timing circuitry not shown separately. They are functional parts of the systems or devices to which they belong and are activated by other components or items in those systems and facilitate their functions.
[0060] In addition, many user interface displays have been discussed. They can take a variety of different forms, and a variety of different user-actuated input mechanisms can be provided thereon. For example, the user-actuated input mechanism can be a text box, a check box, an icon, a link, a drop-down menu, a search box, etc. They can also be actuated in a variety of different ways. For example, a click device (such as a trackball or a mouse) can be used to be actuated. They can be actuated using hardware buttons, switches, joysticks or keyboards, thumb switches or thumb pads, etc. They can also be actuated using virtual keyboards or other virtual actuators. In addition, in the case where the screen displaying them is a touch-sensitive screen, they can be actuated using touch gestures. In addition, in the case where the device displaying them has a voice recognition component, they can be actuated using voice commands.
[0061] A number of data repositories are also discussed. It should be noted that they can each be divided into multiple data repositories. All can be local to the system accessing them, all can be remote, or some can be local and others can be remote. All of these configurations are considered in this article.
[0062] In addition, these figures show multiple blocks with functionality attributed to each block. It should be noted that fewer blocks can be used, so the functionality is performed by fewer components. Likewise, more blocks can be used with functionality distributed between more components.
[0063] Figure 5 yes Figure 1 The block diagram of the architecture 100 shown in FIG. 5 is different in that its elements are arranged in a cloud computing architecture 500. Cloud computing provides computing, software, data access and storage services that do not require end users to understand the physical location or configuration of the system providing the service. In various examples, cloud computing uses appropriate protocols to provide services on wide area networks such as the Internet. For example, a cloud computing provider provides applications through a wide area network and can access them through a web browser or any other computing component. The software or components of the architecture 100 and the corresponding data can be stored on a server at a remote location. The computing resources in a cloud computing environment can be integrated at a remote data center location or can be dispersed. Cloud computing infrastructure can provide services through a shared data center, even if they are only an access point for users. Therefore, the components and functions described herein can be provided from a service provider at a remote location using a cloud computing architecture. Alternatively, they can be provided from a conventional server or installed directly or otherwise on a client device.
[0064] This description is intended to include both public and private cloud computing.Cloud computing (public and private) provides a substantially seamless pool of resources and reduces the need to manage and configure the underlying hardware infrastructure.
[0065] Public clouds are managed by the vendor and typically use the same infrastructure to support multiple consumers. Also, in contrast to private clouds, public clouds free the end user from the burden of managing hardware. Private clouds can be managed by the organization itself, and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installation and repairs.
[0066] exist Figure 5 In the example shown, some items are similar to Figure 1 those shown and are similarly numbered. Figure 4Specifically shown is that the data center computing system 102 can be located in a cloud 502 (which can be public, private, or a combination of some public and other private). Therefore, users 104, 106, 114 use user devices 108, 110, 116 to access these systems through the cloud 502.
[0067] Figure 5 Another example of a cloud architecture is also depicted. Figure 5 It is also contemplated that some elements of the computing system 102 may be located in the cloud 502, while others are not. For example, the data storage devices 142, 144 may be located outside the cloud 502 and accessed through the cloud 502. In another example, the system 132 (or other items) may be outside the cloud 502. Regardless of where they are located, they may be directly accessed by the devices 108, 110, 116 over a network (wide area network or local area network), may be hosted at a remote site by a service, or may be provided as a service through the cloud, or may be accessed through a connection service residing in the cloud. All of these architectures are contemplated herein.
[0068] It should also be noted that the architecture 100 or a portion thereof can be disposed on a variety of different devices. Some of these devices include servers, desktop computers, laptop computers, tablet computers or other mobile devices, such as palmtop computers, mobile phones, smart phones, multimedia players, personal digital assistants, etc.
[0069] Figure 6 is an example of a computing environment in which the architecture 100 or a portion thereof, for example, may be deployed. Figure 6 , an example system for implementing some embodiments includes a general purpose computing device in the form of a computer 810. Components of the computer 810 may include, but are not limited to, a processing unit 820 (which may include a processor or server from the previous figures), a system memory 830, and a system bus 821 that couples various system components including the system memory to the processing unit 820. The system bus 821 may be any of several types of bus structures using any of a variety of bus architectures, including a memory bus or memory controller, a peripheral bus, and a local bus. By way of example and not limitation, such architectures include the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MCA) bus, the Enhanced ISA (EISA) bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus (also known as a mezzanine bus). Reference Figure 1 The memory and programs described can be deployed in Figure 6 in the corresponding part of .
[0070] Computer 810 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computer 810, and includes volatile and non-volatile media, removable and non-removable media. As an example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media is different from (but not including) modulated data signals or carrier waves. It includes hardware storage media, including volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic tape, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by computer 810. Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a transmission mechanism, and includes any information delivery medium. The term "modulated data signal" refers to a signal whose one or more characteristics are set or changed in a manner that can encode information into a signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.
[0071] The system memory 830 includes computer storage media in the form of volatile and / or nonvolatile memory, such as read-only memory (ROM) 831 and random access memory (RAM) 832. A basic input / output system 833 (BIOS), containing the basic routines that help transfer information between elements within the computer 810, such as during startup, is typically stored in ROM 831. RAM 832 typically contains data and / or program modules that are immediately accessible and / or currently being operated on by the processing unit 820. By way of example and not limitation, Figure 6 Operating system 834 , application programs 835 , other program modules 836 , and program data 837 are shown.
[0072] The computer 810 may also include other removable / non-removable volatile / non-volatile computer storage media. For example only, Figure 6A hard disk drive 841 that reads or writes to non-removable non-volatile magnetic media, and an optical disk drive 855 that reads or writes to a removable non-volatile optical disk 856 (such as a CD ROM or other optical media) are shown. Other removable / non-removable volatile / non-volatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tapes, solid-state RAM, solid-state ROM, etc. The hard disk drive 841 is typically connected to the system bus 821 via a non-removable memory interface such as interface 840, and the optical disk drive 855 is typically connected to the system bus 821 via a removable memory interface such as interface 850.
[0073] Alternatively or additionally, the functions described herein may be performed at least in part by one or more hardware logic components. For example, and not limitation, illustrative types of hardware logic components that may be used include field programmable gate arrays (FPGAs), program-specific integrated circuits (ASICs), program-specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), and the like.
[0074] The above discussion and Figure 6 The drives and their associated computer storage media shown in FIG. 8 provide storage of computer readable instructions, data structures, program modules and other data for the computer 810. Figure 6 844, application programs 845, other program modules 846, and program data 847. Note that these components may be the same as or different from operating system 834, application programs 835, other program modules 836, and program data 837. Operating system 844, application programs 845, other program modules 846, and program data 847 are given different numbers here to illustrate that they are at least different copies.
[0075] A user can enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861 (such as a mouse, trackball, or touch pad). Other input devices (not shown) may include a joystick, a game controller, a satellite dish, a scanner, or the like. These and other input devices are typically connected to the processing unit 820 through a user input interface 860 coupled to the system bus, but may be connected through other interfaces and bus structures such as a parallel port, a game port, or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 via an interface such as a video interface 890. In addition to the display, the computer may also include other peripheral output devices such as speakers 897 and a printer 896, which may be connected through an output peripheral interface 895.
[0076] The computer 810 operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a handheld device, a server, a router, a network computer, a peer device, or other public network node, and typically includes many or all of the elements described above with respect to the computer 810. Figure 6 The logical connections shown include a local area network (LAN) 871 and a wide area network (WAN) 873, but other networks may also be included. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
[0077] When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860 or other appropriate mechanism. In a network environment, program modules depicted with respect to the computer 810 or portions thereof may be stored in the remote memory storage device. By way of example and not limitation, Figure 6 Remote application programs 885 are shown residing on remote computer 880. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
[0078] Example 1 is a computing system comprising:
[0079] data access logic in the server kernel that receives a request to perform an operation on data stored on the data storage device;
[0080] call interception logic in the server kernel that intercepts the request before it is executed and, if the request is a file open request to open a target file, determines whether the target file is a driver file, and if the target file is not a driver file, identifies a storage location where the target file is stored;
[0081] target analysis logic in the server kernel that determines if the target file is a driver file, whether the driver file is authorized by a whitelist file, and if the target file is not a driver file, whether the storage location is in a protected location that includes the whitelist file; and
[0082] Blocking logic is invoked that blocks the request from being executed if the target file is a driver file that is not authorized by the whitelist file, and blocks the request from being executed if the target file is not a driver file but is stored in the protected location.
[0083] Example 2 is a computing system according to any or all of the previous examples, further comprising:
[0084] Call type identifier logic in the server kernel, which is configured to identify whether the request is the file open request to open the target file.
[0085] Example 3 is a computing system according to any or all of the previous examples, wherein the call interception logic comprises:
[0086] The target file type identifier logic is configured to identify the type of the target file to determine whether the target file is a driver file.
[0087] Example 4 is a computing system according to any or all of the previous examples, wherein the call interception logic comprises:
[0088] A target volume identifier logic is configured to identify the storage location where the target file is stored.
[0089] Example 5 is a computing system according to any or all of the previous examples, wherein the target analysis logic comprises:
[0090] and driver / whitelist comparison and protection logic configured to, if the target file type identifier logic identifies the target file as a driver file, access the whitelist file and compare a driver file identifier identifying the driver file with an entry in the whitelist file to determine whether the driver file identifier is identified by an entry in the whitelist file, and, if the driver file identifier is identified by an entry in the whitelist file, generate an authorization output indicating that the driver file is authorized by the whitelist file.
[0091] Example 6 is a computing system according to any or all of the previous examples, wherein the target analysis logic comprises:
[0092] and target volume analysis logic configured to, if the target file type identifier logic does not identify the target file as a driver file, compare the storage location of the target file to a series of storage locations that include a protected volume to determine whether the storage location of the target file is in the protected volume, and to generate an authorization output indicating that the target file is not stored in the protected volume if the storage location of the target file is not in the protected volume.
[0093] Example 7 is a computing system according to any or all of the previous examples, wherein the request is to access a file in a file system having an attached driver stack of a loaded filter driver loaded into the server kernel for execution by the server kernel.
[0094] Example 8 is the computing system of any or all of the previous examples, wherein the call interception logic comprises a filter driver in the driver stack attached to the file system.
[0095] Example 9 is the computing system of any or all of the previous examples, wherein the call target analysis logic comprises a filter driver in the driver stack that is attached to the file system.
[0096] Example 10 is the computing system of any or all of the previous examples, wherein the call blocking logic comprises a filter driver in the driver stack attached to the file system.
[0097] Example 11 is a computer-implemented method comprising:
[0098] receiving, in a server kernel, a request to perform an operation on data stored on a data storage device;
[0099] Before the request is executed, determining whether the request is a file open request to open a target file;
[0100] If the request is a file open request to open a target file, determining whether the target file is a driver file;
[0101] If the target file is not a driver file, identifying a storage location where the target file is stored;
[0102] If the target file is a driver file, determining whether the driver file is authorized by a whitelist file;
[0103] If the target file is not a driver file, determining whether the storage location is in a protected location including the whitelist file;
[0104] If the target file is a driver file not authorized by the whitelist file, preventing the request from being executed; and
[0105] If the target file is not a driver file but is stored in the protected location, the request is prevented from being executed.
[0106] Example 12 is a computer-implemented method according to any or all of the previous examples, further comprising:
[0107] In the server kernel, it is identified whether the request is the file open request to open the target file.
[0108] Example 13 is a computer-implemented method according to any or all of the previous examples, wherein determining whether the driver file is authorized by a whitelist file comprises:
[0109] If the target file is a driver file, accessing the whitelist file;
[0110] comparing a driver file identifier identifying the driver file with an entry in the whitelist file to determine whether the driver file identifier is identified by an entry in the whitelist file; and
[0111] If the driver file identifier is identified by an entry in the whitelist file, an authorization output is generated indicating that the driver file is authorized by the whitelist file.
[0112] Example 14 is a computer-implemented method according to any or all of the previous examples, wherein determining whether the storage location is among protected locations including the whitelist file comprises:
[0113] If the target file is not identified as a driver file, comparing the storage location of the target file with a series of storage locations including a protected volume to determine whether the storage location of the target file is in the protected volume; and
[0114] If the storage location of the target file is not in the protected volume, an authorization output is generated indicating that the target file is not stored in the protected volume.
[0115] Example 15 is a computer-implemented method according to any or all of the previous examples, wherein the request is to access a file in a file system having an attached driver stack of a loaded filter driver loaded into the server kernel for execution by the server kernel.
[0116] Example 16 is a computing system according to any or all of the previous examples, wherein determining whether the target file is a driver file comprises:
[0117] providing the request to a filter driver in the driver stack that is attached to the file system; and
[0118] The filter driver is executed.
[0119] Example 17 is a computer-implemented method according to any or all of the previous examples, wherein identifying a storage location where the target file is stored, determining whether the driver file is authorized by a whitelist file, and determining whether the storage location is included in a protected location including the whitelist file:
[0120] providing the request to a filter driver in the driver stack that is attached to the file system; and
[0121] The filter driver is executed.
[0122] Example 18 is a computing system comprising:
[0123] data access logic in the server kernel that receives a request to perform an operation on data stored on the data storage device;
[0124] call type identifier logic in the server kernel configured to identify whether the request is a file open request to open the target file;
[0125] target file type identifier logic configured to intercept the request before the request is executed if the request is a file open request and identify the type of the target file to determine whether the target file is a driver file;
[0126] a target volume identifier logic configured to identify a storage location where the target file is stored;
[0127] target analysis logic in the server kernel that determines if the target file is a driver file, whether the driver file is authorized by a whitelist file, and if the target file is not a driver file, whether the storage location is in a protected location that includes the whitelist file; and
[0128] Blocking logic is invoked that blocks the request from being executed if the target file is a driver file that is not authorized by the whitelist file, and blocks the request from being executed if the target file is not a driver file but is stored in the protected location.
[0129] Example 19 is a computing system according to any or all of the previous examples, wherein the target analysis logic comprises:
[0130] and driver / whitelist comparison and protection logic configured to, if the target file type identifier logic identifies the target file as a driver file, access the whitelist file and compare a driver file identifier identifying the driver file with an entry in the whitelist file to determine whether the driver file identifier is identified by an entry in the whitelist file, and, if the driver file identifier is identified by an entry in the whitelist file, generate an authorization output indicating that the driver file is authorized by the whitelist file.
[0131] Example 20 is a computing system according to any or all of the previous examples, wherein the target analysis logic comprises:
[0132] and target volume analysis logic configured to, if the target file type identifier logic does not identify the target file as a driver file, compare the storage location of the target file to a series of storage locations that include a protected volume to determine whether the storage location of the target file is in the protected volume, and to generate an authorization output indicating that the target file is not stored in the protected volume if the storage location of the target file is not in the protected volume.
[0133] It should also be noted that the different examples described herein can be combined in different ways. That is, parts of one or more examples can be combined with parts of one or more other examples. All of these are contemplated herein.
[0134] Although the subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1. A computing system comprising: at least one processor; as well as A memory storing instructions, the instructions being executable by the at least one processor, wherein the instructions provide in the server kernel: data access logic configured to receive a request to perform an operation on data stored on a data storage device; Call interception logic, which is configured as: intercepting the request before the request is executed; as well as based on a determination that the request is a file open request to open a target file and a determination that the target file is not a driver file, and if the target file is not a driver file, identifying a storage location where the target file is stored, the driver file storing code configured to deploy a driver on the computing system; Target analysis logic, which is configured as: determining that the storage location is in a protected location including a whitelist file, the whitelist file storing a set of entries identifying a set of authorized driver files; as well as Blocking logic is invoked that is configured to block the request from being executed based on a determination that the storage location is in the protected location.
2. The computing system of claim 1 , wherein the instructions provide, in the server kernel: A type identifier logic is called, which is configured to identify whether the request is the file open request to open the target file.
3. The computing system of claim 2, wherein the call interception logic comprises: The target file type identifier logic is configured to identify a type of the target file and determine whether the target file is a driver file based on the identified type.
4. The computing system of claim 3, wherein the call interception logic comprises: A target volume identifier logic is configured to identify the storage location where the target file is stored.
5. The computing system of claim 4, wherein the target analysis logic comprises: and a driver / whitelist comparison and protection logic configured to access the whitelist file and compare a driver file identifier identifying the driver file with the set of entries in the whitelist file to determine whether the driver file identifier is identified by an entry in the whitelist file, and to generate an authorization output indicating that the driver file is authorized by the whitelist file.
6. The computing system of claim 5, wherein the target analysis logic comprises: The target volume analysis logic is configured to compare the storage location of the target file with a series of storage locations comprising a protected volume and determine that the storage location of the target file is within the protected volume based on the comparison.
7. The computing system of claim 6, wherein the request is to access a file in a file system having an attached driver stack of a loaded filter driver loaded into and executed by the server kernel.
8. The computing system of claim 7, wherein at least one of the call interception logic, the target analysis logic, or the call blocking logic comprises a filter driver in the driver stack that is attached to the file system.
9. The computing system of claim 7, wherein The target analysis logic is configured to: Based on a determination that the target file is a driver file storing code configured to deploy a driver on the computing system, comparing the driver file to the set of entries in the whitelist file, and determining, based on the comparing, that the driver file is not authorized by the whitelist file; and The call blocking logic is configured to: The request is prevented from being executed based on the determination that the driver file is not authorized.
10. The computing system of claim 1, wherein The request includes a request for a file; The data access logic is configured to receive a second request to perform an operation on data stored on the data storage device; The call interception logic is configured as follows: intercepting the second request before the second request is executed; based on a determination that the second request is a file open request to open a second target file, determining that the second target file is a driver file storing code configured to deploy a driver on the computing system; The target analysis logic is configured as comparing the driver file to the set of entries in the whitelist file, and determining, based on the comparing, that the driver file is not authorized by the whitelist file; The call blocking logic is configured to block the second request from being executed based on the determination that the driver file is not authorized by the whitelist file.
11. A method performed by a server kernel, the method comprising: receiving a request to perform an operation on data stored on a data storage device; Before the request is executed, identifying the request as a file open request to open a target file, and determining that the target file is not a driver file, the driver file storing code configured to deploy a driver on a computing system; Identify the storage location where the target file is stored; determining that the storage location is in a protected location including a whitelist file, the whitelist file storing a set of entries identifying a set of authorized driver files; as well as Based on a determination that the storage location is in the protected location, the request is prevented from being executed.
12. The method of claim 11, wherein the request comprises a first request, and the method further comprises: receiving a second request to perform an operation on data stored on the data storage device; intercepting the second request before the second request is executed; Based on determining that the second request is a file open request to open a second target file, determining that the second target file is a driver file storing code configured to deploy a driver on the computing system; comparing the driver file to the set of entries in the whitelist file; determining, based on the comparing, that the driver file is not authorized by the whitelist file; as well as Based on the determination that the driver file is not authorized by the whitelist file, the second request is prevented from being executed.
13. The method of claim 12, wherein determining that the driver file is not authorized by the whitelist file comprises: A driver file identifier identifying the driver file is compared to an entry in the whitelist file to determine whether the driver file identifier is identified by an entry in the whitelist file.
14. The method of claim 11, wherein determining that the storage location is in a protected location that includes the whitelist file comprises: comparing the storage location of the target file to a series of storage locations comprising a protected volume; as well as The storage location of the target file is determined in the protected volume based on the comparison.
15. The method of claim 14, wherein the request is to access a file in a file system having an attached driver stack of a loaded filter driver loaded into the server kernel for execution by the server kernel.
16. The method of claim 15, wherein determining whether the target file is a driver file comprises: providing the request to a filter driver in the driver stack attached to the file system; as well as The filter driver is executed.
17. The method of claim 15, wherein identifying a storage location where the target file is stored, determining whether the driver file is authorized by a whitelist file, and determining whether the storage location is in a protected location that includes the whitelist file comprises: providing the request to a filter driver in the driver stack attached to the file system; as well as The filter driver is executed.
18. A computing system comprising: at least one processor; as well as A memory storing instructions, the instructions being executable by the at least one processor, wherein the instructions provide a server kernel, the server kernel being configured to: receiving a request to perform an operation on data stored on a data storage device; Based on determining that the request is a file open request to open a target file, intercepting the request before the request is executed; Determine whether the target file is a driver file based on the type of the identifier of the target file; Identify the storage location where the target file is stored; Based on the determination that the target file is a driver file, determining whether the driver file is authorized by a whitelist file, the whitelist file storing a set of entries identifying a set of authorized driver files, and preventing the request from being executed based on the determination that the driver file is not authorized by the whitelist file; Based on a determination that the target file is not a driver file, and based on a determination that the storage location is within a protected location that includes the whitelist file, the request is prevented from being executed.
19. The computing system of claim 18, wherein the server core is configured to: The whitelist file is accessed and a driver file identifier identifying the driver file is compared to an entry in the whitelist file to determine whether the driver file identifier is identified by an entry in the whitelist file, and an authorization output is generated indicating that the driver file is authorized by the whitelist file.
20. The computing system of claim 18, wherein the server core is configured to: The storage location of the target file is compared to a series of storage locations comprising a protected volume to determine whether the storage location of the target file is in the protected volume, and an authorization output is generated indicating that the target file is not stored in the protected volume.
