在数据库上处理客户信息
我想讨论一个Escenario。
如果我拥有几个客户共享的Web应用程序,那么每个人都有自己的数据库。在某个时候,客户将报告错误。如何处理这些数据的最佳方法?因为我在思考安全含义,这意味着从客户端下载备份,并授予一个开发人员以对误差进行故障排除。
但是需要在真实环境中这些数据来重现错误。有什么想法吗?采取考虑安全含义,这意味着开发人员可以访问所有客户端数据。
I have an escenario i would like to discuss.
If i had a web app shared by several clients, everyone with their own database. In some time a client will report an error. How would it be the best way to handle this data?. Because im thinking on security implications that implies downloading a backup from clients and give to one developer to troubleshoot the erros.
But need this data in a real environment to reproduce the error. Any Ideas? Taking on consideration security implications that means the developer having access to all clients data.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
请让客户端在开发环境中重现错误,并与您共享Dev数据库文件的副本。然后,您的开发人员可以处理有关该问题的数据。
请确保要求共享的数据不是PCI或PII,并且根据CPNA(如果客户是我们的)
Please have the client reproduce the error in their DEV environment and share the copy of the DEV database file with you. Your developers could then work with the data on the issue.
Kindly ensure the data being asked to share is not PCI or PII and in accordance to CPNA (if the client is US based)
这取决于问题。
通常,插入,更新或删除的数据具有一些国王,您可以使用虚拟数据库复制,每个表中只有一两个行,您尝试重现错误。
如果您具有良好的错误记录功能,则可以保存在文本文件或sqlite中所有相关信息,例如出现问题的位置和原因。这将为您节省很多麻烦。
如果您需要数据库:
您还原备份并将所有敏感数据替换为更新命令,并在传递数据之前查看是否仍然发生错误。
为此,您可以提前编写这些更新命令。
一些数据库还可以加密列或混淆它们,因此您应该看到数据库支持它,并且可以在还原的数据上使用它。
that depends on the problem.
Usually the inserted, updated or deleted data have some kings that you can reproduce with a dummy database, with only one or two rows in each table and you have try to reproduce the error.
If you have good error logging feature, that saves in an text file or sqlite all relevant information like where the problem occurred and what was the cause. it will save you a lot of trouble.
If you need the database:
you restore the backup and replace all sensitive data with an UPDATE command and see if the error still occurs, before you pass the data on .
For that you can in advance write those update commands.
Some databases can encrypt also columns or obfuscate them, so you should see of your databse supports that and you can use it on the restored data.