Abstract: An autonomous, mobile robotic device (AMR) is configured with one or more UVC radiation sources, and operates to traverse a path while disinfecting an interior space. Each UVC radiation source is connected to the AMR by an articulating arm that is controlled to orient each source towards a feature or surface that is selected for disinfection during the time that the AMR is moving through the space. The location of each feature selected for disinfection can be mapped, and this map information, a current AMR location and pose can be used to generate signals that are used to control the articulating arm to orient each UVC lamp towards a feature that is selected for disinfection.

Abstract: An autonomous, mobile robotic device (AMR) is configured with one or more UVC radiation sources, and operates to traverse a path while disinfecting an interior space. Each UVC radiation source is connected to the AMR by an articulating arm that is controlled to orient each source towards a feature or surface that is selected for disinfection during the time that the AMR is moving through the space. The location of each feature selected for disinfection can be mapped, and this map information, a current AMR location and pose can be used to generate signals that are used to control the articulating arm to orient each UVC lamp towards a feature that is selected for disinfection.

Abstract: An autonomous, mobile robotic device (AMR) is configured with one or more UVC radiation sources, and operates to traverse a path while disinfecting an interior space. Each UVC radiation source is connected to the AMR by an articulating arm that is controlled to orient each source towards a feature or surface that is selected for disinfection during the time that the AMR is moving through the space. The location of each feature selected for disinfection can be mapped, and this map information, a current AMR location and pose can be used to generate signals that are used to control the articulating arm to orient each UVC lamp towards a feature that is selected for disinfection.

Abstract: An autonomous, mobile robotic device (AMR) is configured with one or more UVC radiation sources, and operates to traverse a path while disinfecting an interior space. Each UVC radiation source is connected to the AMR by an articulating arm that is controlled to orient each source towards a feature or surface that is selected for disinfection during the time that the AMR is moving through the space. The location of each feature selected for disinfection can be mapped, and this map information, a current AMR location and pose can be used to generate signals that are used to control the articulating arm to orient each UVC lamp towards a feature that is selected for disinfection.

Abstract: Protected software, such as an application and/or DLL, is monitored by protective software to guard against attacks, while distinguishing spurious, benign events from attacks. In a 1-touch approach, the protected software is monitored in a testing environment to detect spurious, benign events caused by, e.g., incompatibility or interoperability problems. The spurious events can be remediated in different ways, such as by applying a relaxed security policy. In a production mode, or 0-touch mode, when the protected software is subject to attacks, the corresponding remediation can be applied when the spurious events are again detected. Security events which occur in production mode can also be treated as benign when they occur within a specified time window. The applications and/or DLLs can further be classified according to whether they are known to have bad properties, known to be well-behaved, or unknown. Appropriate treatment is provided based on the classification.

Abstract: A constraint is inserted into a program to address a vulnerability of the program to attacks. The constraint includes a segment of code that determines when the program has been asked to execute a “corner case” which does not occur in normal operations. The constraint code can access a library of detector and remediator functions to detect various attacks and remediate against them. Optionally, the detector can be employed without the remediator for analysis. The context of the program can be saved and restored if necessary to continue operating after remediation is performed. The constraints can include descriptors, along with machine instructions or byte code, which indicate how the constraints are to be used.

Abstract: A runtime code manipulation system is provided that supports code transformations on a program while it executes. The runtime code manipulation system uses code caching technology to provide efficient and comprehensive manipulation of an application running on an operating system and hardware. The code cache includes a system for automatically keeping the code cache at an appropriate size for the current working set of an application running.

Abstract: Hijacking of an application is prevented by monitoring control flow transfers during program execution in order to enforce a security policy. At least three basic techniques are used. The first technique, Restricted Code Origins (RCO), can restrict execution privileges on the basis of the origins of instruction executed. This distinction can ensure that malicious code masquerading as data is never executed, thwarting a large class of security attacks. The second technique, Restricted Control Transfers (RCT), can restrict control transfers based on instruction type, source, and target. The third technique, Un-Circumventable Sandboxing (UCS), guarantees that sandboxing checks around any program operation will never be bypassed.