An indication that data packets of personal data that correspond to data packet types for data categories are approved for transfer between user accounts via the personal data sharing platform is provided. A first data packet identifying first personal data that is related to a first user of the first user account is received. The first data packet includes first personal data values that correspond to first attributes specified by a first data packet type and that have been individually encrypted at first user account. Whether the first data packet satisfies a condition that the first data packet include data values for each of the first attributes specified by the first data packet type for a first data category is determined. Responsive to determining that the first data packet satisfies the condition, the individually encrypted first personal data values and the corresponding first attributes are stored at a data store.

An example operation may include one or more of connecting, by a scheduler node, to a blockchain network comprised of member nodes, receiving, by the scheduler node, a plurality of transactions that include deadlines from the member nodes, comparing, by the scheduler node, the deadlines of the plurality of the transactions against an average time to append to a ledger (ATAL) pre-calculated for the scheduler node, dropping, by the scheduler node, the transactions of the plurality of the transactions, if a sum of the ATAL and a current time is larger than the deadlines of the plurality of the transactions, calculating, by the scheduler node, a priority usage balance (PUB) for the member nodes based on the transactions of the plurality of transactions remaining after the transactions of the plurality of the transactions have been dropped, scheduling, by the scheduler node, a transaction with an earliest deadline from the plurality of the remaining transactions to be validated first for an execution, and arranging, by the scheduler node, a validation order for the plurality of the remaining transactions based on the PUBs.

Aspects of the subject disclosure may include, for example, obtaining a content item, receiving a first token that comprises an identification of a date and a time when a first portion of the content item is obtained, a location where the first portion of the content item is obtained, or a combination thereof, and transmitting the content item and the first token to a database. Other embodiments are disclosed.

Aspects refresh permission credentials by populating within user profile data sets cached for members an invalidated value and a first timestamp of said populating the invalidated value; selecting user profile data sets including the invalidated value; identifying a second timestamp of time of creation of the permission credential within the selected user profile data sets; and in response to determining that a time elapsed between the first and second timestamps does not exceed a threshold, rebuilding the selected user profile data sets to include an updated value of the permission credential and set the second timestamp value to a current time of the rebuild, and cache (store) the rebuilt selected user profile data set within the repository.

Systems and methods are disclosed for preventing relay or replay attacks using time-stamped, localized footprint data. An access device may receive, from one or more beacon transmitters, a plurality of broadcast messages, each broadcast message, of the plurality of broadcast messages, comprising a timestamp and a unique identifier for a beacon transmitter, of the one or more beacon transmitters. The access device may store the timestamps and the unique identifiers. The access device may receive, from a user device, an access request comprising timestamps and unique identifiers corresponding to a subset of the broadcast messages received by the access device. The access device may verify that the stored timestamps and unique identifiers match the timestamps and unique identifiers received from the user device. Based on the verifying, the access device may authenticate the access request.

Wireless communications systems may detect network attacks based on analysis of medium access control (MAC) addresses and origination locations associated with incoming authentication requests. For example, a DoS attack may be detected by determining (e.g., via a database) whether a particular MAC address is associated with multiple authentication request messages without proceeding to an authentication step. According to the described techniques, a system (e.g., an AP, controller/cloud, etc.) may maintain a database of authentication requests and associated MAC addresses, timestamps, and location information. As such, upon reception of an authentication request corresponding to a MAC address, the MAC address may be compared to the database. If the delta (e.g., timestamp difference) between authentication requests from a same MAC address is less than a threshold, the system may detect a potential DoS attack by a client associated with the MAC address and the MAC address may be removed from the AP.

The present disclosure relates to systems, non-transitory computer-readable media, and methods for dynamically controlling ephemeral messaging threads and ephemeral message duration settings across computing devices while improving security by maintaining end-to-end encryption. In particular, in one or more embodiments, the disclosed systems can transmit encrypted ephemeral messages, including ephemeral message duration settings and ephemeral setting timestamps. The disclosed systems can decrypt received messages on receiving client devices and dynamically apply ephemeral message duration settings to different message threads. For example, the disclosed systems can modify existing duration settings at a receiving client device to match a received ephemeral message duration setting based on determining that the received ephemeral setting timestamp predates an existing setting timestamp. Further, the disclosed systems can apply the ephemeral message duration setting to delete ephemeral messages from an ephemeral message thread.

Methods, systems, and devices supporting network and container level traffic analysis and correlation are described. An application server may receive network traffic data from a network-level data capture system and receive container-level application traffic data from a container-level data capture system. The application server may then hash the destination addresses, the time stamp information, and the data amount information from the network traffic data to create a first set of hash values and hash the destination addresses, the time stamp information, and the data amount information from the application traffic data to create a second set of hash values. The application server may then identify matching hash values from the first set of hash values and the second set of hash values and then merge into a data queue the corresponding network traffic with metadata associated with the corresponding application traffic data to create a merged data set.

Systems, methods, and computer-readable media are disclosed for randomized file segmentation and storage. Example methods may include separating, by a system comprising a plurality of servers, a data file into a plurality of file fragments, sending a first file fragment to a first randomly selected server of the plurality of servers, determining a first token having a random expiration time, causing the first token to be stored at the first randomly selected server in association with the first file fragment, sending a second file fragment to a second randomly selected server of the plurality of servers, determining a second token having a random expiration time, and causing the second token to be stored at the second randomly selected server in association with the second file fragment.

This disclosure describes systems on a chip (SOCs) that prevent side channel attacks on encryption and decryption engines of an electronic device. The SoCs of this disclosure concurrently operate key-diverse encryption and decryption datapaths to obfuscate the power trace signature exhibited by the device that includes the SoC. An example SoC includes an encryption engine configured to encrypt transmission (Tx) channel data using an encryption key and a decryption engine configured to decrypt encrypted received (Rx) channel data using a decryption key that is different from the encryption key. The SoC also includes a scheduler configured to establish concurrent data availability between the encryption and decryption engines and activate the encryption engine and the decryption engine to cause the encryption engine to encrypt the Tx channel data concurrently with the decryption engine decrypting the encrypted Rx channel data using the decryption key that is different from the encryption key.