Method and system for moving customer data to trusted storage
Methods and systems are provided for moving customer data relating to a service from the service to a customer-controlled secure storage upon deletion of a customer account from the service. Exemplary methods and systems are provided for moving the customer data to a location which is under the control or under ownership of the customer in a secure and automated fashion. Additionally, methods and systems are provided for establishing a client/service to service relationship.
1. A method of moving customer data relating to a service to a secure storage under control of the customer upon termination of the service governed by a service-level agreement (SLA), the method comprising:
exchanging messages between a customer client device and a service provider for registering the customer for one or more services under control of an orchestrator;
registering a trust relationship between the service provider and the customer for accessing secure storage under control of a customer;
prior to termination of the one or more services, storing said customer data in at least one persistent storage associated with the service provider;
initiating a delete customer command;
fetching customer data from a current Software as a Service (SaaS) provider; and
upon termination of the one or more services, using the orchestrator, copying the customer data from said at least one persistent storage to the secure storage under control of the customer and thereafter deleting the customer data from said at least one persistent storage,
wherein the customer data from the current SaaS provider is permanently deleted, and
wherein any customer data stored in the orchestrator is also permanently deleted.
2. The method of claim 1 , wherein said messages are exchanged via a protocol that supports authorization workflows.
3. The method of claim 2 , wherein exchanging messages includes the service provider transmitting a message to the customer client device that includes service access details relating to at least one client service available to the service provider.
4. The method of claim 3 , wherein said at least one client service is networkable storage and said service access details include minimal data required to identify the secure storage.
5. The method of claim 4 , wherein the minimal data includes a network storage location of the secure storage, a file transfer protocol for copying the customer data from said at least one persistent storage to the secure storage, and said protocol that supports authorization workflows.
6. The method of claim 1 , wherein the service provider utilizes one of a one micro service, monolith or service-oriented architecture for providing said service such that the customer data is distributed between the service provider and at least one micro service, and further including copying customer data from the at least one micro service to the secure storage under control of the service provider upon termination of the service and thereafter deleting the customer data from the at least one micro service.
7. A system for moving customer data relating to a service to a secure storage under control of the customer upon termination of the service governed by a service-level agreement (SLA), the system comprising:
a service provider for registering the customer for one or more of services under control of an orchestrator and at least one application, service, or microservice for receiving said customer data and providing said service, wherein the customer data is distributed between the service provider and said at least one application, service or microservice;
at least one persistent storage associated with the service provider;
the secure storage under control of the customer upon termination of the service; and
a web server for storing said customer data in the at least one persistent storage and registering a trust relationship with the customer for accessing the secure storage under control of the customer,
wherein a networkable storage comprises the at least one persistent storage,
wherein the orchestrator copies customer data from the networkable storage to the secure storage upon termination of the service; and
wherein, upon termination, the customer data from a current Software as a Service (SaaS) provider is permanently deleted, and wherein any customer data stored in the orchestrator is also permanently deleted.
8. The system of claim 7 , wherein the web server registering a trust relationship with the secure storage includes exchanging messages between the web server and customer client device via a protocol that supports authorization workflows.
9. The system of claim 8 , wherein exchanging messages includes the service provider transmitting a message to the customer client device that includes service access details relating to at least one client service available to the service provider.
10. The system of claim 9 , wherein said at least one client service is the networkable storage and said service access details include minimal data required to identify the secure storage.
11. The system of claim 10 , wherein the minimal data includes a network storage location of the secure storage, a file transfer protocol for copying the customer data from said at least one persistent storage to the secure storage, and said protocol that supports authorization workflows.
12. The system of claim 8 , wherein the exchanging of messages uses representational state transfer (RESTful) web services.
13. A non-transient computer readable medium containing program instructions for causing a computer to perform the method governed by a service-level agreement (SLA) of:
exchanging messages between a customer client device and a service provider for registering a customer for one or more services under control of an orchestrator;
registering a trust relationship between the service provider and the customer for accessing secure storage under control of a customer;
prior to termination of the one or more services, storing said customer data in at least one persistent storage associated with the service provider;
initiating a delete customer command;
fetching customer data from a current Software as a Service (SaaS) provider; and
and upon termination of the one or more services, using the orchestrator, copying the customer data from said at least one persistent storage to the secure storage and thereafter deleting the customer data from said at last one persistent storage,
wherein the customer data from the current SaaS provider is permanently deleted, and
wherein any customer data stored in the orchestrator is also permanently deleted.