A robot according to an embodiment of the present disclosure includes an authentication interface for authenticating a user's boarding of the robot using authentication information of the user, a position detector for detecting a position of the robot in a space, a processor for identifying a first section corresponding to the detected position among at least one section in the space, recognizing at least one driving mode for the first section among a plurality of driving modes with different driving speeds, setting one of the recognized at least one driving mode as a driving mode for the first section based on the authentication information, and controlling driving of the robot based on the set driving mode, and a display for outputting information on the set driving mode.

A method of authenticating a consumable or detachable element of a continuous inkjet printer comprising: the controller of the printer generating a 1.sup.st item of random information that is dispatched to an authentication circuit of the element; encrypting the 1.sup.st item of information by the authentication circuit using a 1.sup.st encryption algorithm and a 1.sup.st secret key to form a 1.sup.st item of encrypted random information; dispatching the 1.sup.st item of information to the controller; encrypting the 1.sup.st item of information by the controller using a 2.sup.nd encryption algorithm and a 2.sup.nd secret key to form a 2.sup.nd item of encrypted random information; comparing the 1.sup.st item of encrypted random information with the 2.sup.nd encrypted item of random information to authenticate the consumable element; and if the consumable element is authenticated, dispatching at least one part of a 3.sup.rd key, termed the shared key, by the element to the printer.

A system and method including a mobile phone device and a mobile app, in which said mobile app comprises an unlocking module, an ad menu module, and point processing module stored in said computer readable storage medium, wherein said mobile app includes instructions which when executed by said mobile phone device, cause the mobile phone device to: process a waking up or powering up of said mobile device by said unlocking module; keep track of a user's point total by said point processing module; and process a graphic user interface to present a set of menu items in a lock screen by said ad menu module.

Systems, methods, and devices for managing privacy policies are disclosed. In one embodiment, a method for management of a user's privacy preferences may include: identifying a computer application installed on a user electronic device, or a website accessed using a browser executed by the user electronic device; retrieving a privacy policy document analysis for a privacy policy document associated with the computer application or the website, the privacy policy document analysis comprising a valuation of a plurality of privacy policy segments within the privacy policy document; receiving a privacy preference analysis for the user, the privacy preference analysis comprising a valuation of a plurality of privacy preferences for the user; identifying a recommended action in response to the valuation of one of the privacy policy segments being outside the scope of the valuation of one of the plurality of privacy preferences; and executing the recommended action.

Example methods and systems are directed to reducing latency in providing trusted execution environments (TEEs). Initializing a TEE includes multiple steps before the TEE starts executing. Besides workload-specific initialization, workload-independent initialization is performed, such as adding memory to the TEE. In function-as-a-service (FaaS) environments, a large portion of the TEE is workload-independent, and thus can be performed prior to receiving the workload. Certain steps performed during TEE initialization are identical for certain classes of workloads. Thus, the common parts of the TEE initialization sequence may be performed before the TEE is requested. When a TEE is requested for a workload in the class and the parts to specialize the TEE for its particular purpose are known, the final steps to initialize the TEE are performed.

A method for securely terminating a distributed trusted execution environment spanning a plurality of work accelerators. Each accelerator is configured to self-isolate upon determining that the distributed TEE is to be terminated across the system of accelerators. The data is also wiped from the processor memory of each accelerator, such that the data cannot be read out from the processor memory once the accelerator's links are re-enabled. The self-isolation is performed on each accelerator prior to the step of terminating the TEE on that accelerator. An accelerator only re-enables its links to other accelerators once the data is wiped from its processor memory such that the secret data is removed from the accelerator memory.

A method for securely terminating a distributed trusted execution environment (TEE) spanning a plurality of work accelerators. After wiping sensitive data from the memory of its accelerator, a root of trust for each accelerator is configured to receive confirmation that the data has been wiped from the processor memory in relevant other accelerators prior to moving on to the next stage at which the TEE on its associated accelerator is terminated. Since the data has been wiped from the other accelerators, even if a third party were to inject malicious code into the accelerator, they would be unable to read out the secret data from the other accelerators since the data has been wiped from those other accelerators. In this way, a mechanism is provided for ensuring that when the distributed TEE is terminated, malicious third parties are unable to read out confidential data from the accelerators.

A secure private network connectivity system (SNCS) within a cloud service provider infrastructure (CSPI) is described that provides secure private network connectivity between external resources residing in a customer's on-premise environment and the customer's resources residing in the cloud. The SNCS provides secure private bi-directional network connectivity between external resources residing in a customer's external site representation and resources and services residing in the customer's VCN in the cloud without a user (e.g., an administrator) of the enterprise having to explicitly configure the external resources, advertise routes or set up site-to-site network connectivity. The SNCS provides a high performant, scalable, and highly available site-to-site network connection for processing network traffic between a customer's on-premise environment and the CSPI by implementing a robust infrastructure of network elements and computing nodes that are used to provide the secure site to site network connectivity.

Disclosed are various embodiments for delegating administrator tasks from a primary administrator to a secondary administrator. A secondary administrator can create a temporary user account and cause a temporary client device to be enrolled with a management service. The temporary user and/or temporary client device can be provided with access to certain enterprise resources to which the secondary administrator is empowered to grant access.

A method is for a first-time startup of a not fully personalized secure element, which serves for the use of services of a mobile communication network, in a mobile terminal. In the method, the secure element is started and requested to transmit a status message. The secure element transmits a status message in which it is stated whether the secure element: S1) contains only a bootloader but as yet no firmware image for the secure element; S2) contains a firmware image for the secure element but is not yet fully personalized; or S3) is fully personalized. The secure element is accepted in the cases S1), S2) and S3) and rejected in other cases. In the case S1), a download for a firmware image of the secure element is initiated for a first-time startup.