Consolidated data restoration framework

1. A system for identifying occurrence of events and performing one or more actions to mitigate impacts of the events, the system comprising:

at least one network communication interface;

at least one non-transitory storage device; and

at least one processing device coupled to the at least one non-transitory storage device and the at least one network communication interface, wherein the at least one processing device is configured to:

identify an anomaly based on one or more indicators and one or more dataflows;

in response to identifying the anomaly, determine occurrence of an event and generate one or more propagation models associated with the event;

perform event impact analysis based on the one or more propagation models;

perform one or more actions to contain the event based on the one or more propagation models;

identify a last good copy of data;

retrieve the last good copy of data; and

restore the last good copy of data, wherein restoring the last good copy of data further comprises:

confirming an approach for restoring the last good copy of data;

determining one or more restoral activities associated with the approach;

verifying that the one or more restoral activities do not cause any synchronization issues;

performing the one or more restoral activities;

performing validation after performing the one or more restoral activities; and

determining that the validation is successful and activate at least one dataflow of the one or more dataflows.

2. The system of claim 1 , wherein the at least one processing device is configured to:

gather data from one or more data sources of an entity; and

generate one or more dataflows using the data gathered from the one or more data sources.

3. The system of claim 1 , wherein the at least one processing device is configured to monitor the one or more dataflows to establish one or more standards associated with the one or more dataflows.

4. The system of claim 3 , wherein the at least one processing device is configured to identify the anomaly based on performing rule-based analysis, wherein performing the rule-based analysis comprises:

continuously monitoring the one or more dataflows in real-time;

determining a deviation in the one or more standards associated with the one or more dataflows, wherein the deviation in the one or more standards is associated with at least one of direction, frequency, source, destination, and datatype of the one or more dataflows; and

identifying occurrence of the anomaly based on determining the deviation.

5. The system of claim 4 , wherein the at least one processing device is configured to identify the occurrence of the anomaly based on determining that the deviation is not associated with a change ticket.

6. The system of claim 3 , wherein the at least one processing device is configured to identify the anomaly based on performing time-series analysis, wherein performing the time-series analysis comprises:

continuously monitoring the one or more dataflows in real-time;

determining a deviation in the one or more standards associated with the one or more dataflows, wherein the deviation is associated with at least one of volume, duration, and timings of the one or more dataflows; and

identifying occurrence of the anomaly based on determining the deviation.

7. The system of claim 1 , wherein performing the event impact analysis further comprises:

determining propagation of harmful content associated with the event based on the one or more propagation models; and

determining impact associated with the propagation of the harmful content.

8. The system of claim 1 , wherein the at least one processing device is configured to:

identify one or more options for retrieving the last good copy of data from a metadata inventory;

determine that a most viable option exists for retrieving the last good copy of data from the one or more options;

retrieve the last good copy of data from the most viable option; and

validate the last good copy of data before restoring the last good copy of data.

9. The system of claim 1 , wherein the at least one processing device is configured to:

identify one or more options for retrieving the last good copy from a metadata inventory;

determine that a most viable option does not exist for retrieving the last good copy from the one or more options;

determine that recreation of data is not possible based on determining that the most viable option does not exist; and

provide information associated with the event and the one or more options to one or more users via a dashboard.

10. The system of claim 1 , wherein the at least one processing device is configured to perform the one or more restoral activities in a sequence.

11. A computer program product for identifying occurrence of events and performing one or more actions to mitigate impacts of the events, the computer program product comprising a non-transitory computer-readable storage medium having computer executable instructions for causing a computer processor to perform the steps of:

identifying an anomaly based on one or more indicators and one or more dataflows;

in response to identifying the anomaly, determining occurrence of an event and generate one or more propagation models associated with the event;

performing event impact analysis based on the one or more propagation models;

performing one or more actions to contain the event based on the one or more propagation models;

identifying a last good copy of data;

retrieving the last good copy of data; and

restoring the last good copy of data, wherein restoring the last good copy of data further comprises:

confirming an approach for restoring the last good copy of data;

determining one or more restoral activities associated with the approach;

verifying that the one or more restoral activities do not cause any synchronization issues;

performing the one or more restoral activities;

performing validation after performing the one or more restoral activities; and

determining that the validation is successful and activate at least one dataflow of the one or more dataflows.

12. The computer program product of claim 11 , wherein the computer executable instructions cause a computer processor to perform the steps of:

gathering data from one or more data sources of an entity; and

generating one or more dataflows using the data gathered from the one or more data sources.

13. The computer program product of claim 11 , wherein the computer executable instructions cause a computer processor to perform the step of monitoring the one or more dataflows to establish one or more standards associated with the one or more dataflows.

14. The computer program product of claim 13 , wherein the computer executable instructions cause a computer processor to perform the step of identifying the anomaly based on performing rule-based analysis, wherein performing the rule-based analysis comprises:

continuously monitoring the one or more dataflows in real-time;

determining a deviation in the one or more standards associated with the one or more dataflows, wherein the deviation in the one or more standards is associated with at least one of direction, frequency, source, destination, and datatype of the one or more dataflows; and

identifying occurrence of the anomaly based on determining the deviation.

15. The computer program product of claim 13 , wherein the computer executable instructions cause a computer processor to perform the step of identifying the anomaly based on performing time-series analysis, wherein performing the time-series analysis comprises:

continuously monitoring the one or more dataflows in real-time;

determining a deviation in the one or more standards associated with the one or more dataflows, wherein the deviation is associated with at least one of volume, duration, and timings of the one or more dataflows; and

identifying occurrence of the anomaly based on determining the deviation.

16. The computer program product of claim 11 , wherein performing the event impact analysis further comprises:

determining propagation of harmful content associated with the event based on the one or more propagation models; and

determining impact associated with the propagation of the harmful content.

17. The computer program product of claim 11 , wherein the computer executable instructions cause a computer processor to perform the steps of:

identifying one or more options for retrieving the last good copy of data from a metadata inventory;

determining that a most viable option exists for retrieving the last good copy of data from the one or more options;

retrieving the last good copy of data from the most viable option; and

validating the last good copy of data before restoring the last good copy of data.

18. The computer program product of claim 11 , wherein the computer executable instructions cause a computer processor to perform the steps of:

identifying one or more options for retrieving the last good copy from a metadata inventory;

determining that a most viable option does not exist for retrieving the last good copy from the one or more options;

determining that recreation of data is not possible based on determining that the most viable option does not exist; and

providing information associated with the event and the one or more options to one or more users via a dashboard.

19. A computer implemented method for identifying occurrence of events and performing one or more actions to mitigate impacts of the events, the method comprising:

identifying an anomaly based on one or more indicators and one or more dataflows;

in response to identifying the anomaly, determining occurrence of an event and generate one or more propagation models associated with the event;

performing event impact analysis based on the one or more propagation models;

performing one or more actions to contain the event based on the one or more propagation models;

identifying a last good copy of data;

retrieving the last good copy of data; and

restoring the last good copy of data, wherein restoring the last good copy of data further comprises:

confirming an approach for restoring the last good copy of data;

determining one or more restoral activities associated with the approach;

verifying that the one or more restoral activities do not cause any synchronization issues;

performing the one or more restoral activities;

performing validation after performing the one or more restoral activities; and

determining that the validation is successful and activate at least one dataflow of the one or more dataflows.