Virtualized trusted storage

Particular embodiments described herein provide for an electronic device that can be configured to receive a request from a process to access data is a system, determine if the data is in a virtualized protected area of memory in the system, and allow access to the data if the data is in the virtualized protected area of memory and the process is a trusted process. The electronic device can also be configured to determine if new data should be protected, store the new data in the virtualized protected area of memory in the system if the new data should be protected, and store the new data in an unprotected area of memory in the system if the new data should not be protected.

TECHNICAL FIELD

This disclosure relates in general to the field of information security, and more particularly, to virtualized trusted storage.

BACKGROUND

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.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Example Embodiments

FIG. 1Ais a simplified block diagram of a communication system100afor virtualized trusted storage, in accordance with an embodiment of the present disclosure. As illustrated inFIG. 1A, an embodiment of communication system100acan include an electronic device102a, cloud services104a, and a server106a. Electronic device102acan include memory110, a processor112, a trusted process114, an untrusted process116, and a security module118. Memory110can include secured storage120and unsecured storage122. Security module118can include a security storage module124. Cloud services104aand server106acan each include a network security module126. Electronic device102a, cloud services104a, and server106amay be in communication using network108.

Turning toFIG. 1B,FIG. 1Bis a simplified block diagram of a communication system100bfor virtualized trusted storage, in accordance with an embodiment of the present disclosure. As illustrated inFIG. 1B, an embodiment of communication system100bcan include cloud services104b, a server106b, one or more trusted electronic devices130, and one or more untrusted electronic devices132. Cloud services104band server106bcan each include network security module126and network memory136. Network security module126can include a network security storage module134. Network memory136can include network secured storage138and network unsecured storage140.

In an example embodiments, communication systems100aand100bcan be configured for virtualized trusted secure storage, in accordance with an embodiment of the present disclosure. Security storage module124can be configured to use a file system driver and a reputation of process (e.g. trusted or untrusted) to dynamically virtualize a file system and secure critical user data. For example, communication systems100aand100bcan be configured to receive a request from a process to access data is a system, determine if the data is in a virtualized protected area of memory in the system (e.g., secured storage120or network secured storage138), allow access to the data is the data is not in the virtualized protected area of memory (e.g., unsecured storage122or network unsecured storage140), and allow access to the data if the data is in the virtualized protected area of memory and the process is a trusted process. For example, security module118or network security module126can be configured to determine if a process is a trusted or untrusted process. Communication systems100aand100bcan also be configured to determine if new data should be protected, store the new data in the virtualized protected area of memory in the system if the new data should be protected, and store the new data in an unprotected area of memory in the system if the new data should not be protected.

Elements ofFIGS. 1A and 1Bmay be coupled to one another through one or more interfaces employing any suitable connections (wired or wireless), which provide viable pathways for network (e.g., network108, etc.) communications. Additionally, any one or more of these elements ofFIGS. 1A and 1Bmay be combined or removed from the architecture based on particular configuration needs. Communication systems100aand100bmay include a configuration capable of transmission control protocol/Internet protocol (TCP/IP) communications for the transmission or reception of packets in a network. Communication system systems100aand100bmay also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol where appropriate and based on particular needs.

For purposes of illustrating certain example techniques of communication systems100aand100b, 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.

Currently, the various concepts around virtualized trusted storage require the application vendor to write specific code or include binaries that are linked to a single secure storage. In addition, some existing solutions are custom coded for a single application (e.g., green border or other browser security solutions). Some current solutions have not been successful in providing security against malicious code or hackers inspecting, modifying, or removing user information and documents. What is needed is a system and method that can help secure data against ransomware, password stealers, or other threats that harvest or modify data on an electronic device. It would be beneficial is the system and method could use virtualized storage to secure trusted data.

A communication system for virtualized trusted storage, as outlined inFIGS. 1A and 1B, can resolve these issues (and others). Communication systems100aand100bmay be configured to virtualize trusted process storage to a secure storage area (secure vault, encrypted file system, cloud storage, etc.). The secure storage area (e.g., secured storage120or network secured storage138) may be virtualized by security storage module124. Untrusted processes storage cannot access the virtualized trusted storage. In an example, file system drivers can redirect traffic to the virtualized trusted storage to make the virtualized trusted storage invisible to an untrusted application or an untrusted user.

Communication systems100aand100bmay be configured to use security storage module124and/or a filter driver to redirect input/output (I/O) from trusted processes (e.g. trusted process114) to secured storage (e.g., secured storage120) and I/O from untrusted processes (e.g., untrusted process116) to unsecured storage (e.g., unsecured storage122). Untrusted processes do not get access to the secured storage and will get an untrusted view of the location. Trusted processes get full access to and a trusted view of the secured storage and unsecured storage.

The secured storage can be implemented in a variety of ways. For example, in an enterprise space, secured storage could be a cloud vault. In a consumer space, the secured storage could be a secured vault or locally encrypted virtual file system. A policy on minimum reputation can be set for access to the secured storage. In one example, the reputation of a process can be determined by security module118or network security module126. The secured storage can also be protected by the file type trying to access the secured storage or on a per application type basis. The virtualization of the secured storage can be applied to execute on system locations (e.g. My Documents), on specific folders, or for specific applications. The system can mark individual files as important and only to be accessed by trusted applications and add the important file to secure storage. In addition, files can be removed from secure storage or added to the secured storage based on a user configuration. For example, a user may set a configuration where all applications should be able to access a specific file, only trusted applications should be able to access the specific file, only trusted applications of a specific type should be able to access the specific file, etc. Establishing the reputation of a process may be done using cloud services, local certifications, whitelists, etc.

Turning to the infrastructure ofFIGS. 1A and 1B, communication systems100aand100bin accordance with an example embodiment is shown. Generally, communication systems100aand100bcan be implemented in any type or topology of networks. Network108represents a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate through communication systems100aand100b. Network108offers a communicative interface between nodes, and may be configured as any local area network (LAN), virtual local area network (VLAN), wide area network (WAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Extranet, virtual private network (VPN), and any other appropriate architecture or system that facilitates communications in a network environment, or any suitable combination thereof, including wired and/or wireless communication.

In communication systems100aand100b, 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 systems100aand100b. 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 device102a, cloud services104aand104b, server106aand106b, one or more trusted electronic devices130, and one or more untrusted electronic devices132are 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 systems100aand100b, each of electronic device102a, cloud services104aand104b, server106aand106b, one or more trusted electronic devices130, and one or more untrusted electronic devices132can include memory elements for storing information to be used in the operations outlined herein. Each of electronic device102a, cloud services104aand104b, server106aand106b, one or more trusted electronic devices130, and one or more untrusted electronic devices132may 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 systems100aand100bcould 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 systems100aand100b, such as electronic device102a, cloud services104a104b, and server106aand106b, may include software modules (e.g., security module118, security storage module124, network security module126, and network security storage module134) 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 device102a, cloud services104aand104b, server106aand106b, one or more trusted electronic devices130, and one or more untrusted electronic devices132may 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 device102acan be a network element and include, for example, desktop computers, laptop computers, mobile devices, personal digital assistants, smartphones, tablets, or other similar devices. Cloud services104ais configured to provide cloud services to electronic device102a. Cloud services104bis configured to provide cloud services to one or more trusted electronic devices130and one or more untrusted electronic devices132. 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. Server106aand106bcan 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 system100aand100bvia some network (e.g., network108). 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 systems100aand100b. Although security module118is represented inFIG. 1Aas being located in electronic device102a, this is for illustrative purposes only. Security module118could be combined or separated in any suitable configuration. Furthermore, security module118could be integrated with or distributed in another network accessible by electronic device102asuch as cloud services104aor server106a.

Turning toFIG. 2,FIG. 2is a simplified block diagram of a portion of a communication system100afor virtualized trusted secure storage, in accordance with an embodiment of the present disclosure.FIG. 2illustrates an embodiment of an electronic device102b. Electronic device102bcan include memory110, processor112, trusted process114, untrusted process116, security module118, and a filter driver128.

Security storage module124can be configured to use filter driver128to redirect I/O from trusted process114to secured storage120and I/O from untrusted processes116to unsecured storage122. Untrusted processes do not get access to the secured storage and will get an untrusted view of the location. Trusted processes get full access to and a trusted view of the secured storage and unsecured storage.

Turning toFIG. 3A,FIG. 3Ais a simplified block diagram of a portion of a communication system for virtualized trusted storage, in accordance with an embodiment of the present disclosure. As illustrated inFIG. 3A, the virtualization of the secured storage can be applied to execute on system locations such as My Documents. My Documents is the commonly recognized name of a special folder in Microsoft Windows® that is allocated to help users store their personal data files. When a trusted user, trusted process114, or some other trusted application, accesses a My Documents folder, a secured view142or access of the My Documents folder can include both unsecured files144and secured files146.

Turning toFIG. 3B,FIG. 3Bis a simplified block diagram of a portion of a communication system for virtualized trusted storage, in accordance with an embodiment of the present disclosure. As illustrated inFIG. 3B, when an untrusted trusted user, untrusted process untrusted process116, or some other untrusted application, accesses the My Documents folder, an unsecured view148or access of the My Documents folder can include only unsecured files144. Because the user, process, or other application is not trusted, secured files146are not available.

Turning toFIG. 4,FIG. 4is an example flowchart illustrating possible operations of a flow400that may be associated with virtualized secure storage, in accordance with an embodiment. In an embodiment, one or more operations of flow400may be performed by security module118, security storage module124, network security module126, and network security storage module134. At402, data is to be stored in a system. At404, the system determines if access to the data is be restricted. For example, the data may be from a trusted application, a user may set a configuration where access to the data is restricted, etc. If the access to the data should be restricted, then the data is stored in secured storage, as in406. If the data should not be restricted, then the data is stored in unsecured storage, as in408.

Turning toFIG. 5,FIG. 5is an example flowchart illustrating possible operations of a flow500that may be associated with virtualized secure storage, in accordance with an embodiment. In an embodiment, one or more operations of flow500may be performed by security module118, security storage module124, network security module126, and network security storage module134. At502, access to data is requested by an application. At504, the system determines if the data is in a secured storage location. If the data is not in a secured storage location, then access to the data is allowed, as in506. If the data is in a secured storage location, then the system determines if the application is a trusted application, as in508. If the application is a trusted application, then access to the data is allowed, as in506. If the application is not a trusted application, then access to the data is not allowed, as in510.

FIG. 6illustrates a computing system600that is arranged in a point-to-point (PtP) configuration according to an embodiment. In particular,FIG. 6shows a system where processors, memory, and input/output devices are interconnected by a number of point-to-point interfaces. Generally, one or more of the network elements of communication systems100aand100bmay be configured in the same or similar manner as computing system600.

As illustrated inFIG. 6, system600may include several processors, of which only two, processors670and680, are shown for clarity. While two processors670and680are shown, it is to be understood that an embodiment of system600may also include only one such processor. Processors670and680may each include a set of cores (i.e., processor cores674A and674B and processor cores684A and684B) to execute multiple threads of a program. The cores may be configured to execute instruction code in a manner similar to that discussed above with reference toFIGS. 1-5. Each processor670,680may include at least one shared cache671,681. Shared caches671,681may store data (e.g., instructions) that are utilized by one or more components of processors670,680, such as processor cores674and684.

Processors670and680may also each include integrated memory controller logic (MC)672and682to communicate with memory elements632and634. Memory elements632and/or634may store various data used by processors670and680. In alternative embodiments, memory controller logic672and682may be discrete logic separate from processors670and680.

Processors670and680may be any type of processor and may exchange data via a point-to-point (PtP) interface650using point-to-point interface circuits678and688, respectively. Processors670and680may each exchange data with a chipset690via individual point-to-point interfaces652and654using point-to-point interface circuits676,686,694, and698. Chipset690may also exchange data with a high-performance graphics circuit638via a high-performance graphics interface639, using an interface circuit692, which could be a PtP interface circuit. In alternative embodiments, any or all of the PtP links illustrated inFIG. 6could be implemented as a multi-drop bus rather than a PtP link.

Chipset690may be in communication with a bus620via an interface circuit696. Bus620may have one or more devices that communicate over it, such as a bus bridge618and I/O devices616. Via a bus610, bus bridge618may be in communication with other devices such as a keyboard/mouse612(or other input devices such as a touch screen, trackball, etc.), communication devices626(such as modems, network interface devices, or other types of communication devices that may communicate through a computer network660), audio I/O devices614, and/or a data storage device628. Data storage device628may store code630, which may be executed by processors670and/or680. In alternative embodiments, any portions of the bus architectures could be implemented with one or more PtP links.

The computer system depicted inFIG. 6is a schematic illustration of an embodiment of a computing system that may be utilized to implement various embodiments discussed herein. It will be appreciated that various components of the system depicted inFIG. 6may be combined in a system-on-a-chip (SoC) architecture or in any other suitable configuration. For example, embodiments disclosed herein can be incorporated into systems including mobile devices such as smart cellular telephones, tablet computers, personal digital assistants, portable gaming devices, etc. It will be appreciated that these mobile devices may be provided with SoC architectures in at least some embodiments.

Turning toFIG. 7,FIG. 7is a simplified block diagram associated with an example ARM ecosystem SOC700of the present disclosure. At least one example implementation of the present disclosure can include the virtualized trusted storage features discussed herein and an ARM component. For example, the example ofFIG. 7can be associated with any ARM core (e.g., A-7, A-15, etc.). Further, the architecture can be part of any type of tablet, smartphone (inclusive of Android™ phones, iPhones™), iPad™, Google Nexus™, Microsoft Surfacer™, personal computer, server, video processing components, laptop computer (inclusive of any type of notebook), Ultrabook™ system, any type of touch-enabled input device, etc.

In this example ofFIG. 7, ARM ecosystem SOC700may include multiple cores706-707, an L2 cache control708, a bus interface unit709, an L2 cache710, a graphics processing unit (GPU)715, an interconnect702, a video codec720, and a liquid crystal display (LCD) I/F725, which may be associated with mobile industry processor interface (MIPI)/high-definition multimedia interface (HDMI) links that couple to an LCD.

ARM ecosystem SOC700may also include a subscriber identity module (SIM) I/F730, a boot read-only memory (ROM)735, a synchronous dynamic random access memory (SDRAM) controller740, a flash controller745, a serial peripheral interface (SPI) master750, a suitable power control755, a dynamic RAM (DRAM)760, and flash765. In addition, one or more embodiments include one or more communication capabilities, interfaces, and features such as instances of Bluetooth™770, a 3G modem775, a global positioning system (GPS)780, and an 802.11 Wi-Fi785.

In operation, the example ofFIG. 7can offer processing capabilities, along with relatively low power consumption to enable computing of various types (e.g., mobile computing, high-end digital home, servers, wireless infrastructure, etc.). In addition, such an architecture can enable any number of software applications (e.g., Android™, Adobe® Flash® Player, Java Platform Standard Edition (Java SE), JavaFX, Linux, Microsoft Windows Embedded, Symbian and Ubuntu, etc.). In at least one example embodiment, the core processor may implement an out-of-order superscalar pipeline with a coupled low-latency level-2 cache.

FIG. 8illustrates a processor core800according to an embodiment. Processor core800may be the core for any type of processor, such as a micro-processor, an embedded processor, a digital signal processor (DSP), a network processor, or other device to execute code. Although only one processor core800is illustrated inFIG. 8, a processor may alternatively include more than one of the processor core800illustrated inFIG. 8. For example, processor core800represents one example embodiment of processors cores674a,674b,684a, and684bshown and described with reference to processors670and680ofFIG. 6. Processor core800may be a single-threaded core or, for at least one embodiment, processor core800may be multithreaded in that it may include more than one hardware thread context (or “logical processor”) per core.

FIG. 8also illustrates a memory802coupled to processor core800in accordance with an embodiment. Memory802may be any of a wide variety of memories (including various layers of memory hierarchy) as are known or otherwise available to those of skill in the art. Memory802may include code804, which may be one or more instructions, to be executed by processor core800. Processor core800can follow a program sequence of instructions indicated by code804. Each instruction enters a front-end logic806and is processed by one or more decoders808. The decoder may generate, as its output, a micro operation such as a fixed width micro operation in a predefined format, or may generate other instructions, microinstructions, or control signals that reflect the original code instruction. Front-end logic806also includes register renaming logic810and scheduling logic812, which generally allocate resources and queue the operation corresponding to the instruction for execution.

Processor core800can also include execution logic814having a set of execution units816-1through816-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 logic814performs the operations specified by code instructions.

After completion of execution of the operations specified by the code instructions, back-end logic818can retire the instructions of code804. In one embodiment, processor core800allows out of order execution but requires in order retirement of instructions. Retirement logic820may take a variety of known forms (e.g., re-order buffers or the like). In this manner, processor core800is transformed during execution of code804, at least in terms of the output generated by the decoder, hardware registers and tables utilized by register renaming logic810, and any registers (not shown) modified by execution logic814.

Although not illustrated inFIG. 8, a processor may include other elements on a chip with processor core800, at least some of which were shown and described herein with reference toFIG. 6. For example, as shown inFIG. 6, a processor may include memory control logic along with processor core800. The processor may include I/O control logic and/or may include I/O control logic integrated with memory control logic.

It is also important to note that the operations in the preceding flow diagrams (i.e.,FIGS. 4 and 5) illustrate only some of the possible correlating scenarios and patterns that may be executed by, or within, communication systems100aand100b. Some of these operations may be deleted or removed where appropriate, or these operations may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by communication systems100aand100bin that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure.

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 systems100aand100bhas 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 systems100aand100b.

Other Notes and Examples

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 processor to receive a request from a process to access data is a system, determine if the data is in a virtualized protected area of memory in the system, and allow access to the data if the data is in the virtualized protected area of memory and the process is a trusted process.

In Example C2, the subject matter of Example C1 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 determine if new data should be protected, store the new data in the virtualized protected area of memory in the system if the new data should be protected, and store the new data in an unprotected area of memory in the system if the new data should not be protected.

In Example C3, the subject matter of any one of Examples C1-C2 can optionally include where the device characteristics are at least partially based on other device characteristics of similar devices.

In Example C4, the subject matter of any one of Examples C1-C3 can optionally include where the virtualized protected area of memory is a secured vault or a locally encrypted virtual file system.

In Example C5, the subject matter of any one of Examples C1-C4 can optionally include where the virtualized protected area of memory is a cloud vault.

In Example C6, the subject matter of any one of Example C1-C5 can optionally include where a filter driver controls input and output access to the virtualized protected area of memory.

In Example A1, an electronic device can include a security storage module, where the security storage module is configured to receive a request from a process to access data is a system, determine if the data is in a virtualized protected area of memory in the system, and allow access to the data if the data is in the virtualized protected area of memory and the process is a trusted process.

In Example, A2, the subject matter of Example A-1 can optionally include where the security storage module is further configured to determine if new data should be protected, store the new data in the virtualized protected area of memory in the system if the new data should be protected, and store the new data in an unprotected area of memory in the system if the new data should not be protected.

In Example A3, the subject matter of any one of Examples A1-A2 can optionally include where the virtualized protected area of memory is a secured vault or a locally encrypted virtual file system.

In Example A4, the subject matter of any one of Examples A1-A3 can optionally include where the virtualized protected area of memory is a cloud vault.

In Example A5, the subject matter of any one of Examples A1-A4 can optionally include where a filter driver controls input and output access to the virtualized protected area of memory.

Example M1 is a method including receiving a request from a process to access data is a system, determining if the data is in a virtualized protected area of memory in the system, and allowing access to the data if the data is in the virtualized protected area of memory and the process is a trusted process.

In Example M2, the subject matter of Example M1 can optionally include determining if new data should be protected, storing the new data in the virtualized protected area of memory in the system if the new data should be protected, and storing the new data in an unprotected area of memory in the system if the new data should not be protected.

In Example M3, the subject matter of any one of the Examples M1-M2 can optionally include where the virtualized protected area of memory is a secured vault or a locally encrypted virtual file system.

In Example M4, the subject matter of any one of the Examples M1-M3 can optionally include where the virtualized protected area of memory is a cloud vault.

In Example M5, the subject matter of any one of the Examples M1-M4 can optionally include denying access to the data if the data is in the virtualized protected area of memory and the process is an untrusted process.

In Example M6, the subject matter of any one of the Examples M1-M5 can optionally include where a filter driver controls input and output access to the virtualized protected area of memory.

Example S1 is a system for virtualized trusted secure storage, the system including a security storage module configured to receive a request from a process to access data is a system, determine if the data is in a virtualized protected area of memory in the system, and allow access to the data if the data is in the virtualized protected area of memory and the process is a trusted process.

In Example S2, the subject matter of Example S1 can optionally include where system is further configured to determine if new data should be protected, store the new data in the virtualized protected area of memory in the system if the new data should be protected, and store the new data in an unprotected area of memory in the system if the new data should not be protected.

In Example S3, the subject matter of any one of the Examples S1-S2 can optionally include where the virtualized protected area of memory is a secured vault or a locally encrypted virtual file system.

In Example S4, the subject matter of any one of the Examples S1-S3 can optionally include where the virtualized protected area of memory is a cloud vault.

In Example S5, the subject matter of any one of the Examples S1-S4 can optionally include a filter driver controls input and output access to the virtualized protected area of memory.

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-A5, or M1-M6. Example Y1 is an apparatus comprising means for performing of any of the Example methods M1-M6. 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.