Abstract: A method of securely storing a device password. The method includes receiving from a relying party, via a communication interface, a first public encryption key associated with a first device associated with a user identity. The method includes generating, at a second device associated with the same user identity and registering with the relying party, a public encryption key pair that includes a second public encryption key. The method includes performing a first level of encryption with respect to a password encryption key associated with encrypting a device password of the second device to produce a singly encrypted password encryption key using the second public encryption key. The method includes performing a second level of encryption with respect to the singly encrypted password encryption key to produce a doubly encrypted password encryption key using the first public encryption key and storing the it on the second device.

Abstract: A method of establishing communication with a second device via wireless communication channel that is not natively secure. The method includes performing mutual authentication between the first and second devices by receiving via the communication interface from the second device a FIDO public certificate of the second device and using a FIDO public key of the second device. The FIDO public key of the second device having been registered by the second device with a FIDO relying party in connection with a user identity associated with both the first device and the second device. The FIDO public key of the second device having been fetched by the first device from the FIDO relying party in connection with FIDO registration of the first device with the FIDO relying party in connection with the user identity. The method may include negotiating a shared secret used to engage in ongoing communication.

Abstract: Embodiments of the present disclosure generally relate to apparatus for substrate processing, and more specifically to apparatus for rotating substrates and to uses thereof. In an embodiment, an apparatus for rotating a substrate is provided. The apparatus includes a levitatable rotor comprising a plurality of magnets embedded therein, a plurality of gas bearings positioned to levitate the levitatable rotor, and a stator magnetically coupled to the levitatable rotor, the stator for producing a rotating magnetic field. Apparatus for processing a substrate with the apparatus for rotating substrates as well as methods of use are also described.

Abstract: Techniques are disclosed to obtain device posture of a third party managed device. In various embodiments, a unique identifier of the third party managed device is embedded in a registration communication sent from a third party managed device to an access node associated with a first party management entity. The registration communication is sent from the third party managed device to the access node. The access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device.

Abstract: A method of establishing communication with a second device via wireless communication channel that is not natively secure. The method includes performing mutual authentication between the first and second devices by receiving via the communication interface from the second device a FIDO public certificate of the second device and using a FIDO public key of the second device. The FIDO public key of the second device having been registered by the second device with a FIDO relying party in connection with a user identity associated with both the first device and the second device. The FIDO public key of the second device having been fetched by the first device from the FIDO relying party in connection with FIDO registration of the first device with the FIDO relying party in connection with the user identity. The method may include negotiating a shared secret used to engage in ongoing communication.

Abstract: Techniques are disclosed to obtain device posture of a third party managed device. In various embodiments, a unique identifier of the third party managed device is embedded in a registration communication sent from a third party managed device to an access node associated with a first party management entity. The registration communication is sent from the third party managed device to the access node. The access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device.

Abstract: Techniques are disclosed to obtain device posture of a third party managed device. In various embodiments, a unique identifier of the third party managed device is embedded in a registration communication sent from a third party managed device to an access node associated with a first party management entity. The registration communication is sent from the third party managed device to the access node. The access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device.

Abstract: Embodiments of the present disclosure generally relate to apparatus for substrate processing, and more specifically to apparatus for rotating substrates and to uses thereof. In an embodiment, an apparatus for rotating a substrate is provided. The apparatus includes a levitatable rotor comprising a plurality of magnets embedded therein, a plurality of gas bearings positioned to levitate the levitatable rotor, and a stator magnetically coupled to the levitatable rotor, the stator for producing a rotating magnetic field. Apparatus for processing a substrate with the apparatus for rotating substrates as well as methods of use are also described.

Abstract: Techniques are disclosed to obtain device posture of a third party managed device. In various embodiments, a unique identifier of the third party managed device is embedded in a registration communication sent from a third party managed device to an access node associated with a first party management entity. The registration communication is sent from the third party managed device to the access node. The access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device.

Abstract: Techniques are provided for establishing a secure exchange of data between containerized applications. A method can include registering, by a device, a first containerized application on the device with an access server, registering, by the device, a second containerized application on the device with the access server, verifying that the first containerized application and the second containerized application are configured to exchange data, and exchanging data between the first containerized application and the second containerized application registered with the access server.

Abstract: Methods, devices, and systems are described to modify the life cycle of a Google Android® application, in its application manifest file and byte code, such that the execution of the application can be controlled via policies and security governed by a workspace application installed on an Android-based device. Dummy wrapper classes are inserted into the byte code for network and I/O system calls that call security code before calling the original classes.

Abstract: Methods, devices, and systems are described to modify the life cycle of a Google Android® application, in its application manifest file and byte code, such that the execution of the application can be controlled via policies and security governed by a workspace application installed on an Android-based device. Dummy wrapper classes are inserted into the byte code for network and I/O system calls that call security code before calling the original classes.

Abstract: Methods, devices, and systems are described to modify the life cycle of a Google Android® application, in its application manifest file and byte code, such that the execution of the application can be controlled via policies and security governed by a workspace application installed on an Android-based device. Dummy wrapper classes are inserted into the byte code for network and I/O system calls that call security code before calling the original classes.

Abstract: Techniques are provided for establishing a secure exchange of data between containerized applications. A method can include registering, by a device, a first containerized application on the device with an access server, registering, by the device, a second containerized application on the device with the access server, verifying that the first containerized application and the second containerized application are configured to exchange data, and exchanging data between the first containerized application and the second containerized application registered with the access server.

Abstract: Methods, devices, and systems are described to modify the life cycle of a Google Android® application, in its application manifest file and byte code, such that the execution of the application can be controlled via policies and security governed by a workspace application installed on an Android-based device. Dummy wrapper classes are inserted into the byte code for network and I/O system calls that call security code before calling the original classes.

Abstract: Methods, devices, and systems are described to modify the life cycle of a Google Android® application, in its application manifest file and byte code, such that the execution of the application can be controlled via policies and security governed by a workspace application installed on an Android-based device. Dummy wrapper classes are inserted into the byte code for network and I/O system calls that call security code before calling the original classes.

Abstract: Methods, devices, and systems are described to modify the life cycle of a Google Android® application, in its application manifest file and byte code, such that the execution of the application can be controlled via policies and security governed by a workspace application installed on an Android-based device. Dummy wrapper classes are inserted into the byte code for network and I/O system calls that call security code before calling the original classes.

Abstract: A system and method for contextual visualization of content. An exemplary system comprises a visualization module that can determine a sentiment and at least one other metric relating to the content. The metric could be any of recency, velocity and virality. The visualization module generates a plot for visualizing the sentiment and the at least one other metric.