search

mojaloop / fraud_risk_management

Central repo for fraud and risk management development and specifications
Other
14 stars 7 forks source link

[USER STORY] Archiving of historic data #39

Open JustusOrtlepp opened 4 years ago

JustusOrtlepp commented 4 years ago

Story Title

As a Mojaloop FRM operator, I want to archive historic customer and transactional information when the statutory limits on the retention of that information within an operational system has expired, so that I can be compliant with relevant legislation and so that I can maintain the efficient operation of the system by limiting the amount of historical data to process during fraud risk processing

Acceptance criteria

  1. Only an Mojaloop Hub Operator administrator is able to archive data
  2. The administrator is able to specify the cut-off date and time before which all data will be archived
  3. Archived information is no longer accessible by any operational (front-end) or system processes (e.g. fraud risk rules execution, viewing/inspection, etc)
  4. The archived data is still viewable within the database
  5. The archival of information is fully audit logged
JustusOrtlepp commented 4 years ago

Archival as opposed to straight-up purging allows for a "cooling down" period where data can be restored, if required or if archived erroneously.

There should also really be a user story for the restoration.