Abstract: Methods and systems are described herein for identifying anomalies within streamed event-based time-series data based on retroactively captured data lineage information. For example, the system may receive a request to identify an anomaly associated with a security-event-based time-series. The system may obtain the security-event-based time-series comprising a set of security-alerts further comprising security-alert data. Then the system may store the security-alert data for each security-alert in a database according to a schema. The system may then populate, based on the schema, a set of predefined prompts sections with the security-alert data of the set of security-alerts. The system may then identify the anomaly associated with the security-event-based time-series based on a summary generated by an artificial intelligence model using the set of predefined prompts.

Abstract: Described herein are systems, methods, and programming for determining network resource code updates in real time while also reducing network resource consumption used to determine performance impacts of the network resource code updates. Updates to code portions may be generated and evaluated in a secure virtual computing space for an event of a sequence of events. If the updates to the code portions satisfy processing conditions, other events from the sequence may be evaluated against the same updates. A retroactive analysis of a portfolio of authorized accounts, each including a respective sequence of events, may be analyzed to determine the impact of the network resource code updates to the portfolio.

Abstract: In some implementations, an identifier manager may receive, from a user device, a request for a virtual identifier, the request indicating an intended user for the virtual identifier and a permanent identifier to be associated with the virtual identifier. The identifier manager may receive, from the user device, an indication of a set of restrictions for the virtual identifier. The identifier manager may generate the virtual identifier in response to the request. The identifier manager may transmit, to an account manager, the virtual identifier for association with the permanent identifier and the set of restrictions. The identifier manager may determine a mobile receiving device based on the intended user. The identifier manager may verify a user of the mobile receiving device. The identifier manager may transmit, to an application executed by the mobile receiving device, the virtual identifier in response to verifying the user.

Abstract: In some implementations, a proxy device, configured to receive requests on behalf of a first card network, may receive a request to authorize an event. The request may include a virtual identifier that is associated with the first card network. The proxy device may map the virtual identifier to a permanent identifier that is associated with a second card network different from the first card network. The proxy device may replace the virtual identifier in the request with the permanent identifier in order to generate a detokenized request. The proxy device may transmit the detokenized request to the second card network for processing.