ERP System Data Confidentiality solution discussed with netizens

11:40:33 fear of netizens
Now I want to set up permissions on the distribution system so that ordinary operators can only view documents for one month to prevent information leakage. How is this feasible?

2007-08-23 11:40:52 drate
Well, there is no problem in implementing this in our system.

2007-08-23 11:41:22 drate
We can have two levels: terminal pos. We can allow them to view only 0-30 days of data on the local machine.

2007-08-23 11:42:16 drate
Online applications, we can use OLTP and OLAP to separate the data that people without permissions can see from you.

2007-08-23 11:42:24 drate
You also need to have permission to query reports.

11:43:23 fear of netizens
But this will involve some problems, such as inventory. If they can only view the documents for one month, the inventory will be inaccurate.

2007-08-23 11:43:49 drate
Well, here we can see the inventory. It should be the current inventory status, which is no problem.

2007-08-23 11:44:05 drate
However, if he wants to check a previous inventory transaction, such as warehouse picking and warehouse receiving operations, he will not be able to find it.

11:46:21 fear of netizens
Do you have any good solutions for system information confidentiality?

2007-08-23 11:46:37 drate
Do you mean that the entire system information is kept confidential?

2007-08-23 11:46:57 drate
Including data center management, client operation management, and network management

2007-08-23 11:47:04 drate
Data Application Management

2007-08-23 11:47:18 drate
Is the information only kept confidential for the distribution system?

11:48:04 fear of netizens
There are two problems currently encountered: one is afraid of SW's Data Query System, and the other is afraid that the sales staff will put the data on the local machine and leak it out.

2007-08-23 11:50:05 drate
Well, this problem can be solved consciously.

11:51:31 fear of netizens
Are there any good solutions?

2007-08-23 11:52:00 drate
Well, it is not a solution, but some measures can be used.

2007-08-23 11:53:10 drate
Including: 1. Technically, the database should be stored in the disk display cabinet. In this way, someone will check whether you can directly hot-plug the hard disk and take it out without data.

2007-08-23 11:54:01 drate
Second, make a simulated database that is the same as the external account for future reference. When the client logs on, it will log on to the simulated database.

2007-08-23 11:54:46 drate
Third, the store data of the client-pos can only store offline data for the current day, and the data must be cleared after data exchange ..

2007-08-23 11:55:39 drate
Fourth, the online transaction processing and online analysis should be separated. In this case, the most front-end applications should be transaction processing, and the database is also the latest new database, so there won't be too much historical data in

2007-08-23 11:56:29 drate
Fifth, training: consciously train employees to prevent data from being stored on the local hard disk, lock the screen when they leave the machine, and be alert when strangers come.

2007-08-23 11:57:06 drate
Sixth, system: Check employees' awareness, and sometimes use punitive measures. Otherwise, employees may not be aware of the importance of such measures.

2007-08-23 11:57:39 drate
7. drills. We need to simulate scenarios and conduct drills for these scenarios. In this way, even if there is anything, we can do the exercises to speed up the response.

2007-08-23 11:57:41 drate
That's all.

11:58:31 fear of netizens
Okay, thanks.

11:58:37 fear of netizens
I will sort it out first

2007-08-23 11:58:49 drate
Haha ..

2007-08-23 11:59:27 drate
At that time, you can see where else needs to be supplemented.

================================
I hope there are no better solutions for further discussions? Of course, the best solution is that enterprises can perform formal operations, but there is still a process for domestic enterprises to do this.