Patent Description:
The instant disclosure, therefore, identifies and addresses a need for systems and methods for controlling access to a peripheral device.

<CIT> relates to an "out-of-band" mechanism to remove the physical controls for activating input peripherals from a portable device operating system and instead controlled by a separate peripheral control domain, isolated from the operating system domain by a machine virtualization/isolation technology. No additional hardware may be required. An adjunct I/O virtualization mechanism may also be included to abstract the guarded input peripheral interfaces, such that all attempts to turn them on from within the operating system are automatically redirected by the I/O virtualization mechanism to the peripheral control domain. The peripheral control domain may then conduct a policy-driven decision process to either allow, disallow, or request manual/explicit authorization of an access attempts. Physical access may be performed within the peripheral control domain. Because the access control and physical activation of input peripherals occur out-of-band from the operating system, these security-critical operations may be immune to vulnerabilities in the portable operating system.

As will be described in greater detail below, the instant disclosure describes various systems and methods for controlling access to a peripheral device.

In one example, a method for controlling access to a peripheral device may include receiving an input/output request related to a process attempting to access the peripheral device. The method can also include determining an access state for the process indicative of whether the process will be allowed to gain access to the peripheral device. The access state can be based on a context property of the process. The method can further include responding to the input/output request with initiation of a virtual peripheral output from a virtual peripheral device if the access state is indicative of the process not being allowed access to the peripheral device. In some embodiments, the determining of the access state can include evaluating the context property based on a predefined rule indicative of whether the process should be allowed access to the peripheral device.

In some embodiments, the determining of the access state can include evaluating the context property based on a predefined rule indicative of whether the process should be allowed access to the peripheral device.

In some embodiments, the determining of the access state can include receiving, by the one or more computing devices from a user, an indication of whether the process should be allowed access to the peripheral device.

In some embodiments, the virtual peripheral output can include information indicative of the access state of the process.

In some embodiments, the virtual peripheral output can include information indicative of whether the process is compatible with the peripheral device.

In some embodiments, the one or more computing devices can respond to subsequent input/output requests from the process with the virtual peripheral output from the virtual peripheral device.

In some embodiments, the one or more computing devices can generate an alert to a user associated with the peripheral device that the process has been denied access to the peripheral device.

In some embodiments, the responding, by the one or more computing devices, to the input/output request can include initiating the virtual peripheral device in response to the determining that the access state is indicative of the process not being allowed access to the peripheral device.

In some embodiments, the initiating of the virtual peripheral device can include emulating a physical peripheral device using at least one video class driver.

In some embodiments, the peripheral device is a webcam, the virtual peripheral device is a virtual webcam, and the virtual peripheral output is a video stream.

In one embodiment, a system for controlling access to a peripheral device may include several modules stored in memory, including a receiving module that receives an input/output request related to a process attempting to access the peripheral device, a determination module that determines an access state for the process indicative of whether the process will be allowed to gain access to the peripheral device, the access state being based on a context property of the process, and a response module that responds to the input/output request with initiation of a virtual peripheral output from a virtual peripheral device if the access state is indicative of the process not being allowed access to the peripheral device. The system may also include at least one physical processor configured to execute the receiving module, the response module, and the response module.

In some embodiments, the determination module can evaluate the context property based on a predefined rule indicative of whether the process should be allowed access to the peripheral device.

In some embodiments, the determination module can receive an indication of whether the process should be allowed access to the peripheral device.

In some embodiments, the response module can respond to subsequent input/output requests from the process with the virtual peripheral output from the virtual peripheral device.

In some embodiments, an alert generation module can generate an alert to a user associated with the peripheral device that the process has been denied access to the peripheral device, and the at least one physical processor can be configured to execute the alert generation module.

In some embodiments, the response module can initiate the virtual peripheral device in response to the determination module determining that the access state is indicative of the process not being allowed access to the peripheral device.

In some embodiments, the response module can emulate a physical peripheral device using at least one video class driver.

In some embodiments, the peripheral device can be a webcam and the virtual peripheral device can be a virtual webcam.

In some examples, the above-described method may be encoded as computer-readable instructions on a non-transitory computer-readable medium. For example, a computer-readable medium may include one or more computer-executable instructions that, when executed by at least one processor of a computing device, may cause the computing device to receive an input/output request related to a process attempting to access the peripheral device, determine an access state for the process indicative of whether the process will be allowed to gain access to the peripheral device, the access state being based on a context property of the process, and respond to the input/output request with initiation of a virtual peripheral output from a virtual peripheral device if the access state is indicative of the process not being allowed access to the peripheral device.

In some embodiments, the determining of the access state can include receiving, from a user, an indication of whether the process should be allowed access to the peripheral device.

In some embodiments, the non-transitory computer-readable medium can further comprise executable instructions that, when executed by the at least one processor of the computing device, cause the computing device to respond to subsequent input/output requests from the process with the virtual peripheral output from the virtual peripheral device.

In some embodiments, the non-transitory computer-readable medium can further comprise executable instructions that, when executed by the at least one processor of the computing device, cause the computing device to generate an alert to a user associated with the peripheral device that the process has been denied access to the peripheral device.

In some embodiments, the responding to the input/output request can include initiating the virtual peripheral device in response to the determining that the access state is indicative of the process not being allowed access to the peripheral device.

In some embodiments, the peripheral device is a webcam, the virtual peripheral device can be a virtual webcam, and the virtual peripheral output can be a video stream.

Features from any of the above-mentioned embodiments may be used in combination with one another in accordance with the general principles described herein. These and other embodiments, features, and advantages will be more fully understood upon reading the following detailed description in conjunction with the accompanying drawings and claims.

Throughout the drawings, identical reference characters and descriptions indicate similar, but not necessarily identical, elements. While the example embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the example embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the instant disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.

The present disclosure is generally directed to systems and methods for controlling access to a peripheral device. As will be explained in greater detail below, by blocking a process from gaining access to a peripheral device by redirecting the process to a virtual version of the peripheral device, the peripheral device will remain secure while the system continues to respond to I/O requests from the process and communicate with the process via the virtual peripheral device. Moreover, by continuing to respond to I/O requests and communicating with the process via the virtual peripheral device, the system is able to provide information to the process related to the denial of access rather than just dropping the I/O request. This is important because when the I/O requests are just dropped, the process can report incorrect information about the lack of access to the peripheral device, which can lead to confusing connection errors and inefficient troubleshooting of the connection error.

The following will provide, with reference to <FIG>, detailed descriptions of example systems for controlling access to a peripheral device. Detailed descriptions of corresponding computer-implemented methods will also be provided in connection with <FIG>. Detailed descriptions of exemplary virtual peripheral devices will be provided in connection with <FIG>. In addition, detailed descriptions of an example computing system and network architecture capable of implementing one or more of the embodiments described herein will be provided in connection with <FIG> and <FIG>, respectively.

<FIG> is a block diagram of an example system <NUM> for controlling access to a peripheral device <NUM> (shown in <FIG>). As illustrated in this figure, example system <NUM> may include one or more modules <NUM> for performing one or more tasks. As will be explained in greater detail below, modules <NUM> may include a Receiving module <NUM>, a Determination module <NUM>, a Response module <NUM>, and an alert module <NUM>. Although illustrated as separate elements, one or more of modules <NUM> in <FIG> may represent portions of a single module or application.

In certain embodiments, one or more of modules <NUM> in <FIG> may represent one or more software applications or programs that, when executed by a computing device, may cause the computing device to perform one or more tasks. For example, and as will be described in greater detail below, one or more of modules <NUM> may represent modules stored and configured to run on one or more computing devices, such as the devices illustrated in <FIG> (e.g., computing device <NUM> and/or server <NUM>). One or more of modules <NUM> in <FIG> may also represent all or portions of one or more special-purpose computers configured to perform one or more tasks.

As illustrated in <FIG>, example system <NUM> may also include one or more memory devices, such as memory <NUM>. Memory <NUM> generally represents any type or form of volatile or non-volatile storage device or medium capable of storing data and/or computer-readable instructions. In one example, memory <NUM> may store, load, and/or maintain one or more of modules <NUM>. Examples of memory <NUM> include, without limitation, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical disk drives, caches, variations or combinations of one or more of the same, and/or any other suitable storage memory.

As illustrated in <FIG>, example system <NUM> may also include one or more physical processors, such as physical processor <NUM>. Physical processor <NUM> generally represents any type or form of hardware-implemented processing unit capable of interpreting and/or executing computer-readable instructions. In one example, physical processor <NUM> may access and/or modify one or more of modules <NUM> stored in memory <NUM>. Additionally or alternatively, physical processor <NUM> may execute one or more of modules <NUM> to facilitate controlling access to a peripheral device <NUM>. Examples of physical processor <NUM> include, without limitation, microprocessors, microcontrollers, Central Processing Units (CPUs), Field-Programmable Gate Arrays (FPGAs) that implement softcore processors, Application-Specific Integrated Circuits (ASICs), portions of one or more of the same, variations or combinations of one or more of the same, and/or any other suitable physical processor.

As illustrated in <FIG>, example system <NUM> may also include one or more data storage devices, such as data storage device <NUM>. Data storage device <NUM> generally represents any type or form of storage device or medium capable of storing data and/or other computer-readable instructions. For example, data storage device <NUM> may be a magnetic disk drive (e.g., a so-called hard drive), a solid-state drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a flash drive, or the like.

In certain embodiments, data storage device <NUM> may be configured to read from and/or write to a removable storage unit configured to store computer software, data, or other computer-readable information. Examples of suitable removable storage units include, without limitation, a floppy disk, a magnetic tape, an optical disk, a flash memory device, or the like. Data storage device <NUM> may also include other similar structures or devices for allowing computer software, data, or other computer-readable instructions to be loaded into system <NUM>. For example, data storage device <NUM> may be configured to read and write software, data, or other computer-readable information. Data storage device <NUM> may also be a part of system <NUM> or may be a separate device accessed through other interface systems.

In certain embodiments, such as the illustrated example in <FIG>, data storage device <NUM> can store data representative of a virtual peripheral device <NUM>, a virtual peripheral output <NUM>, an Input/Output (I/O) Request <NUM>, and an access state <NUM> of a process requesting access to a peripheral device <NUM> as described below.

Example system <NUM> in <FIG> may be implemented in a variety of ways. For example, all or a portion of example system <NUM> may represent portions of example system <NUM> in <FIG>. As shown in <FIG>, system <NUM> may include a computing device <NUM> in communication with a server <NUM> via a network <NUM>. In one example, all or a portion of the functionality of modules <NUM> may be performed by computing device <NUM>, server <NUM>, and/or any other suitable computing system. As will be described in greater detail below, one or more of modules <NUM> from <FIG> may, when executed by at least one processor of computing device <NUM> and/or server <NUM>, enable computing device <NUM> and/or server <NUM> to control access to a peripheral device <NUM>. For example, and as will be described in greater detail below, one or more of modules <NUM> may cause computing device <NUM> and/or server <NUM> to recite steps of method claim using <FIG>.

Computing device <NUM> generally represents any type or form of computing device capable of reading computer-executable instructions. For example, computing device <NUM> may include an endpoint device (e.g., a mobile computing device) running client-side security software. Additional examples of computing device <NUM> include, without limitation, laptops, tablets, desktops, servers, cellular phones, Personal Digital Assistants (PDAs), multimedia players, embedded systems, wearable devices (e.g., smart watches, smart glasses, etc.), smart vehicles, smart packaging (e.g., active or intelligent packaging), gaming consoles, so-called Internet-of-Things devices (e.g., smart appliances, etc.), variations or combinations of one or more of the same, and/or any other suitable computing device.

Server <NUM> generally represents any type or form of computing device that is capable of facilitating access to a remote computing device <NUM>. Additional examples of server <NUM> include, without limitation, security servers, application servers, web servers, storage servers, and/or database servers configured to run certain software applications and/or provide various security, web, storage, and/or database services. Although illustrated as a single entity in <FIG>, server <NUM> may include and/or represent a plurality of servers that work and/or operate in conjunction with one another.

Network <NUM> generally represents any medium or architecture capable of facilitating communication or data transfer. In one example, network <NUM> may facilitate communication between computing device <NUM> and server <NUM>. In this example, network <NUM> may facilitate communication or data transfer using wireless and/or wired connections. Examples of network <NUM> include, without limitation, an intranet, a Wide Area Network (WAN), a Local Area Network (LAN), a Personal Area Network (PAN), the Internet, Power Line Communications (PLC), a cellular network (e.g., a Global System for Mobile Communications (GSM) network), portions of one or more of the same, variations or combinations of one or more of the same, and/or any other suitable network.

<FIG> is a flow diagram of an example computer-implemented method <NUM> for controlling access to a peripheral device <NUM>. The steps shown in <FIG> may be performed by any suitable computer-executable code and/or computing system, including system <NUM> in <FIG>, system <NUM> in <FIG>, and/or variations or combinations of one or more of the same. In one example, each of the steps shown in <FIG> may represent an algorithm whose structure includes and/or is represented by multiple substeps, examples of which will be provided in greater detail below.

As illustrated in <FIG>, at step <NUM> one or more of the systems described herein may receive an I/O request <NUM> related to a process attempting to access a peripheral device <NUM>. For example, receiving module <NUM> may, as part of computing device <NUM> in <FIG>, receive an I/O request invoked by a user mode application seeking access to a peripheral device <NUM>.

The term "I/O request," as used herein, generally refers to a request made in an attempt by an executable file to access a peripheral device <NUM>. Examples of I/O requests include, without limitation, requests from applications for communication with a peripheral device <NUM>. I/O requests can include requests made by user mode applications and, in some cases, passed along by an application programming interface (API) function to a kernel-mode I/O manager. Such I/O requests can include requests that have been modified, encapsulated, or translated by an I/O manager, such as I/O request packets (IRPs), for the peripheral device driver. I/O requests can also include system calls or operation calls to the device driver via a file system.

The systems described herein may perform step <NUM> such that the receiving module <NUM> can receive an I/O request from a requesting process <NUM> in a variety of ways.

In one example, shown in <FIG>, the receiving module <NUM> can implemented in a computing device <NUM> where the receiving module <NUM> is configured to receive IRPs from the requesting process <NUM> via an operating system API <NUM> and an I/O manager <NUM>. In some such embodiments, the requesting process <NUM> initiates an I/O request in user mode and issues the I/O request by calling an appropriate function of the operating system API <NUM>, which in turn passes the I/O request to the kernel-mode I/O manager <NUM>. The I/O manager <NUM> translates the I/O request into an IRP, which is a data structure that describes the I/O request as appropriate for device drivers, and which is passed to the receiving module <NUM>.

In another example, shown in <FIG>, the receiving module <NUM> can implemented in a computing device <NUM> where the receiving module <NUM> is integrated into an I/O manager <NUM> for handling I/O requests from a user mode operating system API <NUM>. In some such embodiments, the requesting process <NUM> initiates an I/O request in user mode and issues the I/O request by calling an appropriate function of the operating system API <NUM>, which in turn passes the I/O request to the kernel-mode I/O manager <NUM> that includes the receiving module <NUM>.

In another example, shown in <FIG>, the receiving module <NUM> can implemented in a computing device <NUM> that lacks an I/O manager, such as a Linux-based device. In some such embodiments, the requesting process <NUM> initiates an I/O request, which the operating system kernel maps to the receiving module <NUM> via the file system <NUM>.

At step <NUM>, one or more of the systems described herein may determine an access state <NUM> for the process <NUM> indicative of whether the process <NUM> will be allowed to gain access to the peripheral device <NUM>, the access state <NUM> being based on a context property <NUM> of the process <NUM>. In some embodiments, the access state <NUM> can be determined by evaluating the context property <NUM> based on a predefined rule or rules indicative of whether the process <NUM> should be allowed access to the peripheral device <NUM>. In some embodiments, the access state <NUM> can be determined based on input from a user having authority to grant or deny access to the peripheral device <NUM>, for example where the input includes an indication of whether the process <NUM> should be allowed access to the peripheral device <NUM>.

For example, determination module <NUM> may determine that the attempted access request is anomalous for the specific entity. As used herein, the term "anomalous" generally refers to actions that satisfy a statistical, analyzed, and/or predicted measure (e.g., threshold level) of abnormality or deviation from a statistical, expected, and/or predicted baseline or normal level. Also, as used herein, the term "context property" generally refers to any attribute of the process <NUM> that a security or prediction analysis may ascertain as relevant to detecting actions that satisfy a statistical, analyzed, and/or predicted measure (e.g., threshold level) of abnormality or deviation from a statistical, expected, and/or predicted baseline or normal level. Moreover, as used herein, the term "access state" generally refers to any value, flat, score, or measurement that indicates whether the process <NUM> is granted or denied access to the peripheral device <NUM>.

Determination module <NUM> may determine that the attempted access request is anomalous in a variety of ways and set an access state <NUM> accordingly. In some examples, determination module <NUM> may determine that the attempted action is anomalous for the specific entity by calculating a degree to which the attempted action is estimated to be anomalous. In further examples, determination module <NUM> may determine that the attempted action is anomalous for the specific entity further by determining that the calculated degree satisfies a threshold. For example, determination module <NUM> may establish or define a level of deviation (e.g., standard deviation) that functions as a threshold for categorizing actions as either routine or anomalous.

In some examples, determination module <NUM> may establish upper and/or lower bounds as defining a normal range for any first-order, second-order, and/or n-order value. These values may include counts (e.g., counts of attempts to access a specific set of files or resources, counts of login attempts, counts of different network devices, and/or counts of commands issued to one or more network or peripheral devices), times of day, days of the week, calendar days, and/or second-order measures of these (e.g., rates in terms of time). Determination module <NUM> may base upper and/or lower bounds on manual settings, administrator settings, predefined values, default values, a statistical analysis of previous behavior by the specific entity, and/or a statistical analysis of previous behavior by one or more other entities (e.g., other entities that are comparable to the specific entity, such as other network devices having the same category, type, brand, and/or functionality, and such as other users having the same or similar role within an organization, level of administrative privilege, location, and/or office).

At step <NUM>, one or more of the systems described herein may respond to the I/O request <NUM> with initiation of a virtual peripheral output <NUM> from a virtual peripheral device <NUM> if the access state <NUM> is indicative of the process <NUM> not being allowed access to the peripheral device <NUM>. In some embodiments, the one or more systems described herein may also respond by generating an alert to a user having authority over the peripheral device that the process <NUM> has been denied access to the peripheral device <NUM>. In some embodiments, the virtual peripheral output <NUM> can include information indicative of the access state <NUM> of the process <NUM>. In some embodiments, the virtual peripheral output <NUM> can include information indicative of whether the process <NUM> is compatible with the peripheral device <NUM>.

As used herein, the term "virtual peripheral device" generally refers to a collection of executable resources (e.g., drivers, methods, functions, and/or procedures) that may be accessed by process, such as process <NUM>, and that emulates the physical peripheral device <NUM>. As also used herein, the term "virtual peripheral output" generally refers to any output signal or message transmitted from the virtual peripheral device <NUM> in a format suitable for emulating output of the physical peripheral device <NUM>.

As used herein, the term "peripheral device" generally refers to any internal or external component of a computer device that may be accessed by a process to receive input from the process and/or send output to the process.

In one example, shown in <FIG>, the virtual peripheral device <NUM> can implemented in a computing device <NUM> where the virtual peripheral device <NUM> is embodied as a virtual webcam <NUM>. The virtual webcam <NUM> is configured to produce video stream packets <NUM> in response to the I/O request <NUM>, and additional subsequent I/O requests <NUM>, from the process <NUM> without dropping any I/O requests <NUM>. The video stream packets <NUM> serve as examples of virtual peripheral output <NUM>. The video stream packets <NUM> may contain a configured message stating that the process <NUM> has been denied access to the actual physical webcam <NUM>. The message can optionally also include additional information about the reason that access has been denied, such as a lack of permission or compatibility errors. The message can then be displayed to the user running the process <NUM> instead of a video stream from the actual webcam <NUM>. In one example, the virtual webcam <NUM> can be implemented using filter drivers that host the virtual webcam based on Microsoft Kernel Stream provider class drivers.

In one example, shown in <FIG>, the virtual peripheral device <NUM> can implemented in a computing device <NUM> where the virtual peripheral device <NUM> is embodied as a virtual audio card <NUM>. The virtual audio card <NUM> is configured to produce audio stream packets <NUM> in response to the I/O request <NUM>, and additional subsequent I/O requests <NUM>, from the process <NUM> without dropping any I/O requests <NUM>. The audio stream packets <NUM> serve as examples of virtual peripheral output <NUM>. The audio stream packets <NUM> may contain a configured message stating that the process <NUM> has been denied access to audio output from the actual audio card <NUM>. The message can optionally also include additional information about the reason that access has been denied, such as a lack of permission or compatibility errors. The message can then be displayed to the user running the process <NUM> instead of an audio stream from the actual audio card <NUM>.

As described above, systems and methods described herein may control access to a computer peripheral device by receiving I/O requests for access to the peripheral device prior to the requests being sent to the device drivers. Systems and methods described herein may determine whether the process seeking access to the peripheral device should be granted such access, for example based on properties of the process and/or input from the peripheral owner or other user having authority over the peripheral device. If it is determined that access should not be granted, the I/O requests is still handled by responding with access to a virtual version of the peripheral device that emulates the requested peripheral device. Also, the process will receive virtual output from the virtual peripheral device in a format it would have expected as output from the requested peripheral device. The virtual peripheral device can continue to respond to subsequent I/O requests from the requesting process with the virtual output. The virtual output can include information suitable for informing a user associated with the process that access to the peripheral device was denied and can include information as to the reason that access was denied. This allows the user associated with the process to understand reasons for the denied access rather than just seeing a connection error as would happen if the I/O requests were simply dropped.

<FIG> is a block diagram of an example computing system <NUM> capable of implementing one or more of the embodiments described and/or illustrated herein. For example, all or a portion of computing system <NUM> may perform and/or be a means for performing, either alone or in combination with other elements, one or more of the steps described herein (such as one or more of the steps illustrated in <FIG>). All or a portion of computing system <NUM> may also perform and/or be a means for performing any other steps, methods, or processes described and/or illustrated herein.

Computing system <NUM> broadly represents any single or multi-processor computing device or system capable of executing computer-readable instructions. Examples of computing system <NUM> include, without limitation, workstations, laptops, client-side terminals, servers, distributed computing systems, handheld devices, or any other computing system or device. In its most basic configuration, computing system <NUM> may include at least one processor <NUM> and a system memory <NUM>.

Processor <NUM> generally represents any type or form of physical processing unit (e.g., a hardware-implemented central processing unit) capable of processing data or interpreting and executing instructions. In certain embodiments, processor <NUM> may receive instructions from a software application or module. These instructions may cause processor <NUM> to perform the functions of one or more of the example embodiments described and/or illustrated herein.

System memory <NUM> generally represents any type or form of volatile or non-volatile storage device or medium capable of storing data and/or other computer-readable instructions. Examples of system memory <NUM> include, without limitation, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, or any other suitable memory device. Although not required, in certain embodiments computing system <NUM> may include both a volatile memory unit (such as, for example, system memory <NUM>) and a non-volatile storage device (such as, for example, primary storage device <NUM>, as described in detail below). In one example, one or more of modules <NUM> from <FIG> may be loaded into system memory <NUM>.

In some examples, system memory <NUM> may store and/or load an operating system <NUM> for execution by processor <NUM>. In one example, operating system <NUM> may include and/or represent software that manages computer hardware and software resources and/or provides common services to computer programs and/or applications on computing system <NUM>. Examples of operating system <NUM> include, without limitation, LINUX, JUNOS, MICROSOFT WINDOWS, WINDOWS MOBILE, MAC OS, APPLE'S IOS, UNIX, GOOGLE CHROME OS, GOOGLE'S ANDROID, SOLARIS, variations of one or more of the same, and/or any other suitable operating system.

In certain embodiments, example computing system <NUM> may also include one or more components or elements in addition to processor <NUM> and system memory <NUM>. For example, as illustrated in <FIG>, computing system <NUM> may include a memory controller <NUM>, an I/O controller <NUM>, and a communication interface <NUM>, each of which may be interconnected via a communication infrastructure <NUM>. Communication infrastructure <NUM> generally represents any type or form of infrastructure capable of facilitating communication between one or more components of a computing device. Examples of communication infrastructure <NUM> include, without limitation, a communication bus (such as an Industry Standard Architecture (ISA), Peripheral Component Interconnect (PCI), PCI Express (PCIe), or similar bus) and a network.

Memory controller <NUM> generally represents any type or form of device capable of handling memory or data or controlling communication between one or more components of computing system <NUM>. For example, in certain embodiments memory controller <NUM> may control communication between processor <NUM>, system memory <NUM>, and I/O controller <NUM> via communication infrastructure <NUM>.

I/O controller <NUM> generally represents any type or form of module capable of coordinating and/or controlling the input and output functions of a computing device. For example, in certain embodiments I/O controller <NUM> may control or facilitate transfer of data between one or more elements of computing system <NUM>, such as processor <NUM>, system memory <NUM>, communication interface <NUM>, display adapter <NUM>, input interface <NUM>, and storage interface <NUM>.

As illustrated in <FIG>, computing system <NUM> may also include at least one display device <NUM> coupled to I/O controller <NUM> via a display adapter <NUM>. Display device <NUM> generally represents any type or form of device capable of visually displaying information forwarded by display adapter <NUM>. Similarly, display adapter <NUM> generally represents any type or form of device configured to forward graphics, text, and other data from communication infrastructure <NUM> (or from a frame buffer, as known in the art) for display on display device <NUM>.

As illustrated in <FIG>, example computing system <NUM> may also include at least one input device <NUM> coupled to I/O controller <NUM> via an input interface <NUM>. Input device <NUM> generally represents any type or form of input device capable of providing input, either computer or human generated, to example computing system <NUM>. Examples of input device <NUM> include, without limitation, a keyboard, a pointing device, a speech recognition device, variations or combinations of one or more of the same, and/or any other input device. The peripheral device <NUM> and examples thereof described herein also serve as examples of the input device <NUM>.

Additionally or alternatively, example computing system <NUM> may include additional I/O devices. For example, example computing system <NUM> may include I/O device <NUM>. In this example, I/O device <NUM> may include and/or represent a user interface that facilitates human interaction with computing system <NUM>. Examples of I/O device <NUM> include, without limitation, a computer mouse, a keyboard, a monitor, a printer, a modem, a camera, a scanner, a microphone, a touchscreen device, variations or combinations of one or more of the same, and/or any other I/O device.

Communication interface <NUM> broadly represents any type or form of communication device or adapter capable of facilitating communication between example computing system <NUM> and one or more additional devices. For example, in certain embodiments communication interface <NUM> may facilitate communication between computing system <NUM> and a private or public network including additional computing systems. Examples of communication interface <NUM> include, without limitation, a wired network interface (such as a network interface card), a wireless network interface (such as a wireless network interface card), a modem, and any other suitable interface. In at least one embodiment, communication interface <NUM> may provide a direct connection to a remote server via a direct link to a network, such as the Internet. Communication interface <NUM> may also indirectly provide such a connection through, for example, a local area network (such as an Ethernet network), a personal area network, a telephone or cable network, a cellular telephone connection, a satellite data connection, or any other suitable connection.

In certain embodiments, communication interface <NUM> may also represent a host adapter configured to facilitate communication between computing system <NUM> and one or more additional network or storage devices via an external bus or communications channel. Examples of host adapters include, without limitation, Small Computer System Interface (SCSI) host adapters, Universal Serial Bus (USB) host adapters, Institute of Electrical and Electronics Engineers (IEEE) <NUM> host adapters, Advanced Technology Attachment (ATA), Parallel ATA (PATA), Serial ATA (SATA), and External SATA (eSATA) host adapters, Fibre Channel interface adapters, Ethernet adapters, or the like. Communication interface <NUM> may also allow computing system <NUM> to engage in distributed or remote computing. For example, communication interface <NUM> may receive instructions from a remote device or send instructions to a remote device for execution.

In some examples, system memory <NUM> may store and/or load a network communication program <NUM> for execution by processor <NUM>. In one example, network communication program <NUM> may include and/or represent software that enables computing system <NUM> to establish a network connection <NUM> with another computing system (not illustrated in <FIG>) and/or communicate with the other computing system by way of communication interface <NUM>. In this example, network communication program <NUM> may direct the flow of outgoing traffic that is sent to the other computing system via network connection <NUM>. Additionally or alternatively, network communication program <NUM> may direct the processing of incoming traffic that is received from the other computing system via network connection <NUM> in connection with processor <NUM>.

Although not illustrated in this way in <FIG>, network communication program <NUM> may alternatively be stored and/or loaded in communication interface <NUM>. For example, network communication program <NUM> may include and/or represent at least a portion of software and/or firmware that is executed by a processor and/or Application Specific Integrated Circuit (ASIC) incorporated in communication interface <NUM>.

As illustrated in <FIG>, example computing system <NUM> may also include a primary storage device <NUM> and a backup storage device <NUM> coupled to communication infrastructure <NUM> via a storage interface <NUM>. Storage devices <NUM> and <NUM> generally represent any type or form of storage device or medium capable of storing data and/or other computer-readable instructions. For example, storage devices <NUM> and <NUM> may be a magnetic disk drive (e.g., a so-called hard drive), a solid state drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a flash drive, or the like. Storage interface <NUM> generally represents any type or form of interface or device for transferring data between storage devices <NUM> and <NUM> and other components of computing system <NUM>. In one example, [data storage <NUM>] from <FIG> may be stored and/or loaded in primary storage device <NUM>.

In certain embodiments, storage devices <NUM> and <NUM> may be configured to read from and/or write to a removable storage unit configured to store computer software, data, or other computer-readable information. Examples of suitable removable storage units include, without limitation, a floppy disk, a magnetic tape, an optical disk, a flash memory device, or the like. Storage devices <NUM> and <NUM> may also include other similar structures or devices for allowing computer software, data, or other computer-readable instructions to be loaded into computing system <NUM>. For example, storage devices <NUM> and <NUM> may be configured to read and write software, data, or other computer-readable information. Storage devices <NUM> and <NUM> may also be a part of computing system <NUM> or may be a separate device accessed through other interface systems.

Many other devices or subsystems may be connected to computing system <NUM>. Conversely, all of the components and devices illustrated in <FIG> need not be present to practice the embodiments described and/or illustrated herein. The devices and subsystems referenced above may also be interconnected in different ways from that shown in <FIG>. Computing system <NUM> may also employ any number of software, firmware, and/or hardware configurations. For example, one or more of the example embodiments disclosed herein may be encoded as a computer program (also referred to as computer software, software applications, computer-readable instructions, or computer control logic) on a computer-readable medium. The term "computer-readable medium," as used herein, generally refers to any form of device, carrier, or medium capable of storing or carrying computer-readable instructions. Examples of computer-readable media include, without limitation, transmission-type media, such as carrier waves, and non-transitory-type media, such as magnetic-storage media (e.g., hard disk drives, tape drives, and floppy disks), optical-storage media (e.g., Compact Disks (CDs), Digital Video Disks (DVDs), and BLU-RAY disks), electronic-storage media (e.g., solid-state drives and flash media), and other distribution systems.

The computer-readable medium containing the computer program may be loaded into computing system <NUM>. All or a portion of the computer program stored on the computer-readable medium may then be stored in system memory <NUM> and/or various portions of storage devices <NUM> and <NUM>. When executed by processor <NUM>, a computer program loaded into computing system <NUM> may cause processor <NUM> to perform and/or be a means for performing the functions of one or more of the example embodiments described and/or illustrated herein. Additionally or alternatively, one or more of the example embodiments described and/or illustrated herein may be implemented in firmware and/or hardware. For example, computing system <NUM> may be configured as an Application Specific Integrated Circuit (ASIC) adapted to implement one or more of the example embodiments disclosed herein.

<FIG> is a block diagram of an example network architecture <NUM> in which client systems <NUM>, <NUM>, and <NUM> and servers <NUM> and <NUM> may be coupled to a network <NUM>. As detailed above, all or a portion of network architecture <NUM> may perform and/or be a means for performing, either alone or in combination with other elements, one or more of the steps disclosed herein (such as one or more of the steps illustrated in <FIG>). All or a portion of network architecture <NUM> may also be used to perform and/or be a means for performing other steps and features set forth in the instant disclosure.

Client systems <NUM>, <NUM>, and <NUM> generally represent any type or form of computing device or system, such as example computing system <NUM> in <FIG>. Similarly, servers <NUM> and <NUM> generally represent computing devices or systems, such as application servers or database servers, configured to provide various database services and/or run certain software applications. Network <NUM> generally represents any telecommunication or computer network including, for example, an intranet, a WAN, a LAN, a PAN, or the Internet. In one example, client systems <NUM>, <NUM>, and/or <NUM> and/or servers <NUM> and/or <NUM> may include all or a portion of system <NUM> from <FIG>.

As illustrated in <FIG>, one or more storage devices <NUM>(<NUM>)-(N) may be directly attached to server <NUM>. Similarly, one or more storage devices <NUM>(<NUM>)-(N) may be directly attached to server <NUM>. Storage devices <NUM>(<NUM>)-(N) and storage devices <NUM>(<NUM>)-(N) generally represent any type or form of storage device or medium capable of storing data and/or other computer-readable instructions. In certain embodiments, storage devices <NUM>(<NUM>)-(N) and storage devices <NUM>(<NUM>)-(N) may represent Network-Attached Storage (NAS) devices configured to communicate with servers <NUM> and <NUM> using various protocols, such as Network File System (NFS), Server Message Block (SMB), or Common Internet File System (CIFS).

Servers <NUM> and <NUM> may also be connected to a Storage Area Network (SAN) fabric <NUM>. SAN fabric <NUM> generally represents any type or form of computer network or architecture capable of facilitating communication between a plurality of storage devices. SAN fabric <NUM> may facilitate communication between servers <NUM> and <NUM> and a plurality of storage devices <NUM>(<NUM>)-(N) and/or an intelligent storage array <NUM>. SAN fabric <NUM> may also facilitate, via network <NUM> and servers <NUM> and <NUM>, communication between client systems <NUM>, <NUM>, and <NUM> and storage devices <NUM>(<NUM>)-(N) and/or intelligent storage array <NUM> in such a manner that devices <NUM>(<NUM>)-(N) and array <NUM> appear as locally attached devices to client systems <NUM>, <NUM>, and <NUM>. As with storage devices <NUM>(<NUM>)-(N) and storage devices <NUM>(<NUM>)-(N), storage devices <NUM>(<NUM>)-(N) and intelligent storage array <NUM> generally represent any type or form of storage device or medium capable of storing data and/or other computer-readable instructions.

In certain embodiments, and with reference to example computing system <NUM> of <FIG>, a communication interface, such as communication interface <NUM> in <FIG>, may be used to provide connectivity between each client system <NUM>, <NUM>, and <NUM> and network <NUM>. Client systems <NUM>, <NUM>, and <NUM> may be able to access information on server <NUM> or <NUM> using, for example, a web browser or other client software. Such software may allow client systems <NUM>, <NUM>, and <NUM> to access data hosted by server <NUM>, server <NUM>, storage devices <NUM>(<NUM>)-(N), storage devices <NUM>(<NUM>)-(N), storage devices <NUM>(<NUM>)-(N), or intelligent storage array <NUM>. Although <FIG> depicts the use of a network (such as the Internet) for exchanging data, the embodiments described and/or illustrated herein are not limited to the Internet or any particular network-based environment.

In at least one embodiment, all or a portion of one or more of the example embodiments disclosed herein may be encoded as a computer program and loaded onto and executed by server <NUM>, server <NUM>, storage devices <NUM>(<NUM>)-(N), storage devices <NUM>(<NUM>)-(N), storage devices <NUM>(<NUM>)-(N), intelligent storage array <NUM>, or any combination thereof. All or a portion of one or more of the example embodiments disclosed herein may also be encoded as a computer program, stored in server <NUM>, run by server <NUM>, and distributed to client systems <NUM>, <NUM>, and <NUM> over network <NUM>.

As detailed above, computing system <NUM> and/or one or more components of network architecture <NUM> may perform and/or be a means for performing, either alone or in combination with other elements, one or more steps of an example method for controlling access to a peripheral device.

While the foregoing disclosure sets forth various embodiments using specific block diagrams, flowcharts, and examples, each block diagram component, flowchart step, operation, and/or component described and/or illustrated herein may be implemented, individually and/or collectively, using a wide range of hardware, software, or firmware (or any combination thereof) configurations. In addition, any disclosure of components contained within other components should be considered example in nature since many other architectures can be implemented to achieve the same functionality.

In some examples, all or a portion of example system <NUM> in <FIG> may represent portions of a cloud-computing or network-based environment. Cloud-computing environments may provide various services and applications via the Internet. These cloud-based services (e.g., software as a service, platform as a service, infrastructure as a service, etc.) may be accessible through a web browser or other remote interface. Various functions described herein may be provided through a remote desktop environment or any other cloud-based computing environment.

In various embodiments, all or a portion of example system <NUM> in <FIG> may facilitate multi-tenancy within a cloud-based computing environment. In other words, the software modules described herein may configure a computing system (e.g., a server) to facilitate multi-tenancy for one or more of the functions described herein. For example, one or more of the software modules described herein may program a server to enable two or more clients (e.g., customers) to share an application that is running on the server. A server programmed in this manner may share an application, operating system, processing system, and/or storage system among multiple customers (i.e., tenants). One or more of the modules described herein may also partition data and/or configuration information of a multi-tenant application for each customer such that one customer cannot access data and/or configuration information of another customer.

According to various embodiments, all or a portion of example system <NUM> in <FIG> may be implemented within a virtual environment. For example, the modules and/or data described herein may reside and/or execute within a virtual machine. As used herein, the term "virtual machine" generally refers to any operating system environment that is abstracted from computing hardware by a virtual machine manager (e.g., a hypervisor). Additionally or alternatively, the modules and/or data described herein may reside and/or execute within a virtualization layer. As used herein, the term "virtualization layer" generally refers to any data layer and/or application layer that overlays and/or is abstracted from an operating system environment. A virtualization layer may be managed by a software virtualization solution (e.g., a file system filter) that presents the virtualization layer as though it were part of an underlying base operating system. For example, a software virtualization solution may redirect calls that are initially directed to locations within a base file system and/or registry to locations within a virtualization layer.

In some examples, all or a portion of example system <NUM> in <FIG> may represent portions of a mobile computing environment. Mobile computing environments may be implemented by a wide range of mobile computing devices, including mobile phones, tablet computers, e-book readers, personal digital assistants, wearable computing devices (e.g., computing devices with a head-mounted display, smartwatches, etc.), and the like. In some examples, mobile computing environments may have one or more distinct features, including, for example, reliance on battery power, presenting only one foreground application at any given time, remote management features, touchscreen features, location and movement data (e.g., provided by Global Positioning Systems, gyroscopes, accelerometers, etc.), restricted platforms that restrict modifications to system-level configurations and/or that limit the ability of third-party software to inspect the behavior of other applications, controls to restrict the installation of applications (e.g., to only originate from approved application stores), etc. Various functions described herein may be provided for a mobile computing environment and/or may interact with a mobile computing environment.

In addition, all or a portion of example system <NUM> in <FIG> may represent portions of, interact with, consume data produced by, and/or produce data consumed by one or more systems for information management. As used herein, the term "information management" may refer to the protection, organization, and/or storage of data. Examples of systems for information management may include, without limitation, storage systems, backup systems, archival systems, replication systems, high availability systems, data search systems, virtualization systems, and the like.

In some embodiments, all or a portion of example system <NUM> in <FIG> may represent portions of, produce data protected by, and/or communicate with one or more systems for information security. As used herein, the term "information security" may refer to the control of access to protected data. Examples of systems for information security may include, without limitation, systems providing managed security services, data loss prevention systems, identity authentication systems, access control systems, encryption systems, policy compliance systems, intrusion detection and prevention systems, electronic discovery systems, and the like.

According to some examples, all or a portion of example system <NUM> in <FIG> may represent portions of, communicate with, and/or receive protection from one or more systems for endpoint security. As used herein, the term "endpoint security" may refer to the protection of endpoint systems from unauthorized and/or illegitimate use, access, and/or control. Examples of systems for endpoint protection may include, without limitation, anti-malware systems, user authentication systems, encryption systems, privacy systems, spam-filtering services, and the like.

While various embodiments have been described and/or illustrated herein in the context of fully functional computing systems, one or more of these example embodiments may be distributed as a program product in a variety of forms, regardless of the particular type of computer-readable media used to actually carry out the distribution. The embodiments disclosed herein may also be implemented using software modules that perform certain tasks. These software modules may include script, batch, or other executable files that may be stored on a computer-readable storage medium or in a computing system. In some embodiments, these software modules may configure a computing system to perform one or more of the example embodiments disclosed herein.

In addition, one or more of the modules described herein may transform data, physical devices, and/or representations of physical devices from one form to another. Additionally or alternatively, one or more of the modules recited herein may transform a processor, volatile memory, non-volatile memory, and/or any other portion of a physical computing device from one form to another by executing on the computing device, storing data on the computing device, and/or otherwise interacting with the computing device.

The preceding description has been provided to enable others skilled in the art to best utilize various aspects of the example embodiments disclosed herein. This example description is not intended to be exhaustive or to be limited to any precise form disclosed. Many modifications and variations are possible without departing from the scope of the instant disclosure. The embodiments disclosed herein should be considered in all respects illustrative and not restrictive. Reference should be made to the appended claims and their equivalents in determining the scope of the instant disclosure.

Claim 1:
A computer-implemented method (<NUM>) for controlling access to a peripheral device, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:
receiving (<NUM>), by one or more computing devices, an input/output request related to an application process attempting to access the peripheral device;
determining, by the one
or more computing devices, whether the input/output request is anomalous with respect to the application process attempting to access the peripheral device, the determination indicating that the input/output request is beyond a threshold level of abnormality for the application process;
determining (<NUM>), by the one or more computing devices, an access state for the application process indicative of whether the process will be allowed to gain access to the peripheral device, the access state being based on a context property of the application process; and
responding (<NUM>), by the one or more computing devices, to the input/output request with initiation of a virtual peripheral output from a virtual peripheral device if the request is beyond the threshold level of abnormality and if the access state is indicative of the application process not being allowed access to the peripheral device, wherein the virtual peripheral output is transmitted to the application process and:
emulates an output of the peripheral device in an output format expected by the application process; and
provides information to the application process about the access state and a reason for the access state; and
generating, by the one or more computing devices, an alert to a user associated with the peripheral device that the application process has been denied access to the peripheral device.