A memory device management system includes a first key acquisition unit that acquires a first key, a second key generation unit that generates a second key in accordance with a configuration of a memory device that is a management target, an equality determination unit that determines an equality between a value of the first key and a value of the second key, and a data erasure processing unit that erases data stored in the memory device in a case of a determination that the value of the first key and the value of the second key are different.

An information processing apparatus includes a controller configured to manage the printing device on the basis of user information of a corresponding user. The controller further performs: (a) acquiring individual information identifying the printing device; (b) acquiring initialization identification information used for determining whether an information initialization has been performed on a specific printing device identified by the individual information acquired in the (a) acquiring; (c) determining, on the basis of the individual information acquired in the (a) acquiring and the initialization identification information acquired in the (b) acquiring, whether the information initialization has been performed on the specific printing device along with transfer of ownership of the specific printing device from a first user to a second user; and (d) prohibiting, in response to determining in the (c) determining that the information initialization has been performed, the second user from accessing the user information of the first user.

The various implementations described herein include methods and systems of data governance. In one aspect, a method of purging backup data includes obtaining a database table having a corresponding data policy and generating an encrypted version of the database table by applying an encryption key, including encrypting at least a portion of the database table. The method further includes identifying an expiration date for the encryption key based on the data policy, and storing the encryption key, the expiration date, and an encryption identifier for the encryption key in an encryption table. The method also includes receiving a command to back up the database table and, in response to the command, generating a backup of the encrypted version of the database table. The method further includes storing the backup and, when a current date is at least the expiration date for the encryption key, deleting the encryption key.

In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may determine that the staged job needs to be executed by a baseboard management controller (BMC) while an information handling system (IHS) is held in a power-on self-test; create a hybrid job associated with the staged job; reboot the IHS; launch an IHS firmware application in a pre-boot IHS firmware environment; provide, to the BMC, a command to execute a first portion of the hybrid job; obtain, by the BMC, an authentication key; provide, by the BMC, the authentication key to the non-volatile storage device; execute, by the BMC, the first portion of the hybrid job to configure the non-volatile storage device; and execute, by the IHS firmware application, the second portion of the hybrid job to poll the baseboard management controller for a result status of configuring the non-volatile storage device.

Provided are a security defense method and apparatus applied to a network security defense system. The method includes: using memoryless technology in a cyberspace information system, where the memoryless technology includes technology which is not affected by generalized disturbance; eliminating a memory of the cyberspace information system on an effect of random disturbance by using a redundancy and replacement mechanism; and eliminating a memory of the cyberspace information system on an effect of non-random disturbance by eliminating a memory of a program running in the cyberspace information system and/or data in the cyberspace information system. The present solution can block a memory of the cyberspace information system on an error caused by the generalized disturbance including the non-random disturbance and the random disturbance, thereby improving security of the cyberspace information system.

Techniques to manage mobile devices are disclosed. In various embodiments, a request to perform a management action with respect to a mobile device is received from a mobile device management (MDM) authority. A scope of authority of the MDM authority with respect to the mobile device is determined. The management action is caused to be performed with respect to the mobile device based at least in part on the determined scope of authority of the MDM authority with respect to the mobile device.

A method includes utilizing a user computing device to remove privacy information. The user computing device may obtain a vehicle identification number associated with a target vehicle that has a target in-vehicle device from which privacy information of a user is to be removed. Using the vehicle identification number, the user computing device may obtain vehicle parameters associated with the target vehicle. The user computing device may obtain a privacy information removal file comprising an instruction set associated with removing privacy data from candidate in-vehicle devices, and may present the instruction set. The user computing device may obtain a user feedback experience. The user feedback experience may include a confirmation of removal of the privacy information from the at least one candidate in-vehicle device, user comments, a voice recording, or an image, captured by a camera of the user computing device, of the at least one candidate in-vehicle device.

Embodiments disclosed are directed to a computing system that performs steps to forensically isolate a compromised storage resource (e.g., bucket) of a production cloud computing and storage environment. In response to detecting an unauthorized access to resources (e.g., objects) stored in storage resource of the production cloud computing and storage environment, the computing system deploys a forensic isolation application that freezes the compromised storage resource so that a forensic analysis can be performed, duplicates the compromised storage resource's resources, and stores the duplicate resources as forensically isolated resources in a storage device outside of the production cloud computing and storage environment. The forensic isolation application then stores the duplicate resources as operational resources. Subsequently, the forensic isolation application reroutes authorized requests for the frozen resource to the operational copy of the frozen resource.

Aspects of the disclosure relate to a system that provides enhanced security of information transmitted by connected devices. The system may be used to request resources from members of a donee's virtual group. Donated funds or line of credit may be loaded to the donee's digital wallet with no link to any of the donee's personal accounts. The request for resources may utilize secure correspondence between the donee and the prospective donors. The secure correspondence may be locked and prevented from being forwarded or captured via a screenshot to ensure confidentiality. If an attempt is made to forward or copy the secure correspondence, the secure correspondence may be deleted. Donated funds/line of credit may be allocated for specific use, and may not be owned by the donee until used.

A TPM is implemented in an SOC for thwarting PIN state replay attacks. Programmable fuses are used as a counter and an on-die RAM stores a blown-fuse count and a TPM state that includes a PIN-failure count and a fuse count. TPM initialization includes incrementing the TPM state PIN-failure count if the blown-fuse count is greater than the TPM state fuse count. Once a PIN is received, if the TPM state PIN-failure count satisfies a PIN failure policy and the PIN is correct, the TPM state PIN-failure count is cleared, and if the PIN is incorrect, a fuse is blown and the blown-fuse count is incremented. If the fuse blow fails, TPM activity is halted. If the fuse blow succeeds, the TPM state PIN-failure count is incremented and the TPM state fuse count is set equal to the blown-fuse count. The TPM state is saved to off-die non-volatile memory.