Privacy protection method for data sharing
By analyzing complaint information and geographical location information, combining multiple factors to evaluate user risks, and dynamically adjusting access permissions, the limitations of single-dimensional evaluation in traditional methods are solved, and the privacy protection accuracy and security of data sharing are improved.
Patent Information
- Application Number
- CN202411708495.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-27
- Publication Date
- 2024-12-27
- Estimated Expiration
- 2044-11-27
AI Technical Summary
Traditional data sharing privacy protection methods are based on single-dimensional evaluation, and cannot effectively respond to complex privacy protection needs, failing to make full use of complaint information and geographical location information, resulting in lagging responses to privacy protection measures and lack of flexibility, making it difficult to dynamically evaluate user access risks.
By obtaining and analyzing user complaint information and geographical location information, combining the data existence time and complaint information ratio, dynamically judge data sensitivity, and assessing user access risks based on multiple factors, adjusting access rights to improve the accuracy and security of privacy protection. sex.
It significantly improves the accuracy and flexibility of data privacy protection, can identify potential risk areas and users, dynamically control access rights, reduce the possibility of data leakage, and improve the security of data sharing.
Smart Images

Figure CN119203247A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of privacy protection for data sharing, and in particular to a privacy protection method for data sharing. Background Art
[0002] Carbon footprint data may contain sensitive information such as a company's production process, energy usage, and supply chain management. If this information is leaked to competitors, it may weaken the company's market position and competitive advantage. Therefore, protecting the privacy of carbon footprint data helps maintain these partnerships and prevent trust crises caused by sensitive information leaks. Carbon footprint data may involve a company's technological innovation and intellectual property rights. Protecting this data can prevent competitors from obtaining the company's core technology, thereby protecting the company's innovative achievements. Therefore, a privacy protection method for carbon footprint data is particularly important.
[0003] The risk assessment of traditional data sharing privacy protection methods is often based on a single dimension, such as determining access risks based only on access frequency, user identity or data sensitivity. This single assessment model cannot effectively respond to complex privacy protection needs, because data leakage risks are usually the result of multiple factors. Single-dimensional assessment methods are difficult to capture the specific risks of access behaviors, such as considering the risks brought by user IP addresses, complaint records and accessed data at the same time. Therefore, the limitations of this assessment method reduce the accuracy and effectiveness of privacy protection.
[0004] In the process of data sharing, user complaint information is an important source of feedback data. Traditional methods rarely use complaint information to adjust access policies in privacy protection. A large number of complaint information about specific data may mean that the data has privacy risks, but traditional methods do not make effective use of these feedbacks and fail to associate complaint information with sensitivity settings, user rights management, etc. This defect leads to a relatively delayed adjustment of privacy protection measures, making it difficult to respond to user feedback risks in a timely manner, and lacking flexibility and responsiveness.
[0005] Traditional privacy protection methods for data sharing generally determine access rights based on user identity or permission level. It is difficult to dynamically assess user access risks based on user behavior characteristics. For example, the number of complaints may change over time, affecting the assessment of access risks. If the user's access risk is not dynamically updated based on these changes, the system may allow high-risk users to access sensitive data, increasing the possibility of data leakage.
[0006] In the data sharing scenario, the user's geographic location information can provide an important basis for risk judgment. Traditional data sharing privacy protection methods usually do not consider the impact of user geographic location on data access security, and only use access rights as the core determining factor. The distribution of geographic locations helps to reveal the potential threats of data circulation paths and sensitive information dissemination; for example, if a large number of access requests come from a specific area, it may point to abnormal cluster access behavior, and ignoring this information will lead to blind spots in security protection. At the same time, this defect may cause the cross-regional privacy risks faced by data sharing to be ignored. Summary of the invention
[0007] The present invention provides a privacy protection method for data sharing, which is used to promote the solution of the problems mentioned in the above background technology.
[0008] The present invention provides the following technical solution: Optionally, a privacy protection method for data sharing, characterized in that: it includes: The user who applies for access to the data is recorded as the access user, and the owner of the data that the access user applies to access is recorded as the holding user; Record the data requested by the accessing user as data to be accessed; Obtain the number of complaint information involving the data to be accessed among all complaint information; The complaint information includes the data involved in the complaint and the time of the complaint; Judging whether the data to be accessed is high-sensitivity data or low-sensitivity data according to the number of complaint information involving the data to be accessed in the complaint information; Establish position set number one; If the data to be accessed is low-sensitivity data, obtain the IP address of the user who applies to access the data to be accessed, obtain the geographical location and longitude and latitude coordinates corresponding to each IP address, form a pairing relationship between the IP address and the geographical location and longitude and latitude coordinates corresponding to the IP address, and include all pairing relationships in the first location set; Based on the pairing relationship in the first position set, determine whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data; Get the access risk of the access user; Based on the access risk of the accessing user and the type of the data to be accessed, determine whether the accessing user can access the data to be accessed.
[0009] Optionally, determining the sensitive type of the data to be accessed according to the number of complaint information related to the data to be accessed in the complaint information is specifically: Obtain the number of complaint information involving the data to be accessed in the complaint information, the number is recorded as A; Set the number threshold Z1; If A ≥ Z1, the data to be accessed is recorded as highly sensitive data; If A<Z1, obtain the existence time of the data to be accessed, recorded as T days; Set the data existence time threshold T1, the unit is set to day, and set the ratio threshold Z2; If T≤T1, obtain the ratio of A to T and calculate it as A÷T; If (A÷T) ≥ Z2, the data to be accessed is recorded as highly sensitive data; If (A÷T) < Z2, the data to be accessed is recorded as low-sensitivity data; If T>T1, obtain the time when the data to be accessed is uploaded and record it as the upload time; The time after the upload time and with an interval of (2 / 3) T from the upload time is recorded as the front-end time, and the time after the upload time and with an interval of T from the upload time is recorded as the back-end time; The time period between the upload time and the front-end time is recorded as the front-end time period, and the time period between the front-end time and the back-end time is recorded as the back-end time period; The number of complaint information involving the data to be accessed in the complaint information in the front-end time period is obtained, recorded as A1, and the number of complaint information involving the data to be accessed in the complaint information in the back-end time period is obtained, recorded as A-A1; If {A1÷[(2 / 3)T]}<{(A-A1)÷[(1 / 3)T]}, the data to be accessed is recorded as highly sensitive data; If {A1÷[(2 / 3)T]}≥{(A-A1)÷[(1 / 3)T]}, the data to be accessed is recorded as low-sensitivity data.
[0010] Optionally, judging whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data according to the pairing relationship in the first position set is specifically: Get the number of pairing relationships in the first position set, denoted as D; Mark the area corresponding to each geographical location in the D pairing relationships in the first location set on the map; Set the marking times percentage threshold Z3; Get the number of times each area is marked; For each marked area, if the ratio of the number of times the area is marked to D is ≥ Z3, the area is recorded as a risk area; If the ratio of the number of times a region is marked to D is less than Z3, no processing is performed; Get the number of times the risk area is marked, recorded as M; Mark the geographical locations corresponding to M IP addresses in the risk area; Obtain the coordinate values of the longitude and latitude corresponding to the M geographical locations marked in the risk area, which are recorded as (E1, F1), (E2, F2), (E3, F3)...(E M , F M ); Get the average of the longitude and latitude values, record them as E and F respectively, and calculate them as E=(E1+E2+E3……E M )÷M, F=(F1+F2+F3……F M )÷M; Record the longitude and latitude coordinates (E, F) as the center coordinates of point 1; Get (E1, F1), (E2, F2), (E3, F3)... (E M , F M ) to the center coordinate of No. 1, which is recorded as G1, G1, G1...G M ; Get G1, G1, G1...G M The average value is recorded as G AVG , calculated as G AVG =(G1+G2+G3……G M )÷M; Take the center coordinate of No. 1 as the center and make a circle with radius G AVG circle, get (E1, F1), (E2, F2), (E3, F3)... (E M , F M ) Among the geographical locations corresponding to the M longitude and latitude coordinates, the number of geographical locations located in the area covered by the circle is denoted by G.
[0011] Optionally, judging whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data according to the pairing relationship in the first position set further includes: Set the geographical location ratio threshold Z4 and the risk user ratio threshold Z5; If G÷M≥Z4, obtain whether there are risky users among the visiting users corresponding to the IP addresses in the circle coverage area. If there are risky users, obtain the number of risky users, recorded as B; The risky users are specifically: If the cumulative number of complaints against a user is greater than 0, the user will be marked as a risky user; If the ratio of B to G (B÷G) ≥ Z5, the area covered by the circle is recorded as a potential risk area, and the data to be accessed has the risk of being converted from low-sensitivity data to high-sensitivity data; If the ratio of B to G (B÷G) is less than Z5, there are no risky users among the accessing users corresponding to the IP addresses within the circle coverage area, or G÷M is less than Z4, then the data to be accessed does not have the risk of being converted from low-sensitivity data to high-sensitivity data.
[0012] Optionally, obtaining the access risk of the access user is specifically: For users who are complained about: If the cumulative number of complaints against the accessing user = 1, the accessing account will be banned for 30 days; If the cumulative number of complaints against the visiting user = 2, the user's account will be banned for 180 days; If the cumulative number of complaints against the visiting user = 3, the user's account will be banned for 365 days; If the cumulative number of complaints against the visiting user = 4, the user's account will be permanently banned; Get the cumulative number of bans for the access user. If the cumulative number of bans for the access user is greater than 0 but less than or equal to 2, the access user has a Class I access risk, and the Class I access risk value is recorded as P1. If the cumulative number of bans for the access user is greater than 2, the access user has a first-class access risk, and the first-class access risk value is recorded as P2, P1<P2; If the cumulative number of bans for the accessing user is equal to 0, then the accessing user does not have a Class I access risk.
[0013] Optionally, obtaining the access risk of the access user further includes: Set the access user existence time threshold T2; Get the existence time of the accessing user, recorded as C; Get the time when the access user completes registration, which is recorded as the registration time; The time before the registration time and seven days after the registration time is recorded as the registration front end time; The time period between the registration front-end time and the registration time is recorded as the registration front-end time period; If the access user's existence time C < T2, obtain the access user's IP address and record it as the target IP address; Users with the same IP address as the visiting user are recorded as one type of user; If there is a type of user in the registration front-end time period and this type of user is banned, the accessing user has a type 2 access risk, and the type 2 access risk value is recorded as Q; If there is no first-class user banned during the registration front-end time period, the accessing user does not have the second-class access risk; Set distance threshold Z5; If the geographical location corresponding to the target IP address is in a potential risk area, the access user has three types of access risks, and the three types of access risk values are recorded as R2; If the geographical location corresponding to the target IP address is not located in the potential risk area, and the distance between the geographical location corresponding to the target IP address and the center coordinate of No. 1 is ≤ Z5, then the access user has three types of access risks, and the three types of access risk values are recorded as R1, R1<R2; If the distance between the geographical location corresponding to the target IP address and the center coordinates of No. 1 is greater than the distance threshold Z5, then there is no third-level access risk for the accessing user.
[0014] Optionally, the step of judging whether the accessing user can access the data to be accessed in combination with the access risk of the accessing user and the type of the data to be accessed is as follows: Get the total access risk value of the access user, denoted as U; The total access risk value is specifically the sum of the first-category access risk value, the second-category access risk value, and the third-category access risk value; If the access user has one type of access risk and three types of access risks, and the value of the first type of access risk is P2, and the value of the third type of access risk is R3, then the total access risk value of the access user is U=P2+R3; Set the total risk value threshold Z6; The total access risk value of the access user is U≥Z6, and the access user is recorded as a high-risk user; The total access risk value of the access user U<Z6, and the access user is recorded as a low-risk user; When the data to be accessed is low-sensitivity data and the accessing user is a low-risk user, the accessing user can directly access the data to be accessed; When the data to be accessed is low-sensitivity data and the accessing user is a high-risk user, the accessing user can directly access the data to be accessed after the user's approval; When the data to be accessed is highly sensitive data and the accessing user is a low-risk user, the accessing user can directly access the data to be accessed after the user's approval; When the data to be accessed is highly sensitive data and the accessing user is a high-risk user, access will be denied.
[0015] The present invention has the following beneficial effects: 1. This privacy protection method for data sharing determines the sensitivity category of data by the number of complaint information involving the data to be accessed in the complaint information; if the number of complaint information involving the data to be accessed reaches the set threshold, it is marked as highly sensitive data; if the number of complaint information involving the data to be accessed does not reach the threshold, the sensitive type is further determined based on the data existence time and the number of complaint information involving the data to be accessed; this scheme can dynamically update the sensitive type of data based on the complaint information of the holding user, improve the recognition rate of highly sensitive data, and enhance the flexibility of data privacy protection.
[0016] 2. This privacy protection method for data sharing, when judging the sensitive type of the data to be accessed, if the existence time of the data to be accessed is short, the ratio of the number of complaint information to the existence time is obtained. If the ratio is greater than the set threshold, the data to be accessed is recorded as high-sensitivity data, and if the ratio is less than the set threshold, the data to be accessed is recorded as low-sensitivity data; if the existence time of the data to be accessed is long, the upload time is divided into two different stages before and after, and the number of complaint information in the two different stages is counted respectively, and a comparative analysis is performed; this method can identify whether the number of complaint information involving the data to be accessed surges in a short period of time. If there is a surge, the data to be accessed is recorded as high-sensitivity data, and if there is no surge, the data to be accessed is recorded as low-sensitivity data; this scheme avoids a single judgment on the data of the entire existence time of the data to be accessed, thereby making a refined judgment on the data sensitivity type; this method significantly improves the accuracy of privacy protection and makes data protection measures more in line with actual needs.
[0017] 3. This privacy protection method for data sharing obtains the IP address of the visiting user for a short-lived account, and obtains the blocking status of the account under this IP address. If an account under this IP address has been blocked recently, it is possible that the visiting user of the blocked account has registered a new account to access the account again after being blocked, so the access risk is high. Therefore, once a blocked account is found, the newly registered account can be immediately monitored to detect and prevent malicious behavior in a timely manner; by checking the blocking records under the IP address, such repeated attacks can be effectively prevented to protect data security.
[0018] 4. This privacy protection method for data sharing counts the number of times each area in the No. 1 location set is marked, defines the area where the number of markings exceeds the percentage threshold as a risk area, and continues to mark the address location of each visiting user in the risk area to determine whether there is a concentrated distribution of users in the risk area. If there is a concentrated distribution of users, then it is determined whether there are risky users in the area where users are concentrated. If there are risky users and the proportion of risky users is high, the area where users are concentrated is recorded as a potential risk area, and the data to be accessed has the risk of being converted from low-sensitivity data to high-sensitivity data. This solution can identify and lock potential risk areas. If the IP address of the visiting user is in the potential risk area, the access risk of the visiting user is increased. This method makes privacy protection targeted and can perform more stringent access control on users in specific areas.
[0019] 5. In this privacy protection method for data sharing, the risk value of the accessing user is evaluated based on multiple factors, including the number of complaints and IP address, etc. It can dynamically evaluate the user's access risk, and then calculate the total risk value of the accessing user, and determine the access rights of the accessing user in combination with the sensitive type of the data; if the user's risk value exceeds the set threshold, the system will regard it as a high-risk user, thereby restricting its access rights; this scheme dynamically controls the user's access rights based on the data sensitivity type and the user's total risk value, thereby improving the accuracy and security of access control; compared with a single permission control method, this method can adjust user permissions according to the access risk value, effectively reducing the possibility of malicious access or improper use of data; in this way, the scheme achieves hierarchical and refined privacy protection, making data sharing safer. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 It is a schematic diagram of the structure of the present invention. DETAILED DESCRIPTION
[0021] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0022] Embodiment 1, a privacy protection method for data sharing, characterized by comprising: For a carbon footprint disclosure data sharing platform, all shared data are carbon footprint disclosure data. After each enterprise uploads its carbon footprint disclosure information to the sharing platform, the user who applies to access the data is recorded as the access user, and the owner of the data that the access user applies to access is recorded as the holding user, and the holding user is each enterprise; Record the data requested by the accessing user as data to be accessed; Obtain the number of complaint information involving the data to be accessed among all complaint information. When the accessing user leaks the data or performs improper operations, such as when the shared and disclosed supply chain carbon footprint data is abused, the holding user, i.e. the enterprise, can complain to the data sharing platform to ensure that the data they hold is not leaked and further spread. After the holding user complains, the complained accessing user will be banned, and the banned accessing user cannot apply to access the data during the ban period; The complaint information includes the data involved in the complaint and the time of the complaint; Judging whether the data to be accessed is high-sensitivity data or low-sensitivity data according to the number of complaint information involving the data to be accessed in the complaint information; Establish position set number one; If the data to be accessed is low-sensitivity data, obtain the IP address of the user who applies to access the data to be accessed, obtain the geographical location and longitude and latitude coordinates corresponding to each IP address, form a pairing relationship between the IP address and the geographical location and longitude and latitude coordinates corresponding to the IP address, and include all pairing relationships in the first location set; Based on the pairing relationship in the first position set, determine whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data; Get the access risk of the access user; Based on the access risk of the accessing user and the type of the data to be accessed, determine whether the accessing user can access the data to be accessed.
[0023] The method of determining the sensitive type of the data to be accessed according to the number of complaint information related to the data to be accessed in the complaint information is specifically: Obtain the number of complaint information involving the data to be accessed in the complaint information, the number is recorded as A; Set a number threshold Z1. The function of Z1 is to determine the sensitive type of the data to be accessed. If the number of complaint information involving the data to be accessed is greater than or equal to the number threshold Z1, it means that the risk of leakage of the data to be accessed is high, and the data to be accessed is marked as highly sensitive data. If the number of complaint information involving the data to be accessed is less than the number threshold Z1, it means that the risk of leakage of the data to be accessed is low, but the sensitive type of the data to be accessed needs to be further determined. If A≥Z1, it means that the risk of the data to be accessed being leaked is high, and the data to be accessed is recorded as highly sensitive data; If A<Z1, it means that the risk of the data to be accessed being leaked is low, and the existence time of the data to be accessed is obtained, which is recorded as T days; Set the data existence time threshold T1. When the data to be accessed is marked as low-sensitivity data based on the number of complaint information related to the data to be accessed in the complaint information, it is necessary to further determine the sensitivity type of the data to be accessed based on the relationship between its existence time and the existence time threshold T1. The unit is set to day. Set the ratio threshold Z2. When the existence time of the data to be accessed is less than the existence time threshold T1, determine the sensitivity type of the data to be accessed based on the ratio of the number of complaint information related to the data to be accessed in the complaint information to the registration time. When the ratio is greater than or equal to the ratio threshold Z2, it means that the reason why the number of complaint information related to the data to be accessed in the complaint information is less than the number threshold Z1 is that the existence time of the data to be accessed is short. Therefore, the data to be accessed is marked as high-sensitivity data. When the ratio is less than the ratio threshold Z2, it means that the reason why the number of complaint information related to the data to be accessed in the complaint information is less than the number threshold Z1 is that the number of complaint information related to the data to be accessed in the complaint information is small. Therefore, the data to be accessed is still marked as low-sensitivity data. If T≤T1, obtain the ratio of A to T and calculate it as A÷T; If (A÷T) ≥ Z2, it means that the number of complaint information involving the data to be accessed in the complaint information is less than the number threshold Z1. The reason is that the data to be accessed has a short existence time, and the data to be accessed is recorded as highly sensitive data; If (A÷T) < Z2, it means that the number of complaint information involving the data to be accessed in the complaint information is less than the number threshold Z1. The reason is that the sensitivity of the data to be accessed is low, and the data to be accessed is recorded as low-sensitivity data; If T>T1, it means that the data to be accessed has existed for a long time. Therefore, it is necessary to determine whether there is a surge in the number of complaint information involving the data to be accessed in the complaint information, and obtain the time when the data to be accessed is uploaded, which is recorded as the upload time; The time after the upload time and with an interval of (2 / 3) T from the upload time is recorded as the front-end time, and the time after the upload time and with an interval of T from the upload time is recorded as the back-end time; The time period between the upload time and the front-end time is recorded as the front-end time period, and the time period between the front-end time and the back-end time is recorded as the back-end time period; The number of complaint information involving the data to be accessed in the complaint information in the front-end time period is obtained, recorded as A1, and the number of complaint information involving the data to be accessed in the complaint information in the back-end time period is obtained, recorded as A-A1; If {A1÷[(2 / 3)T]}<{(A-A1)÷[(1 / 3)T]}, it means that the number of complaint information involving the data to be accessed has increased sharply recently, and the data to be accessed is recorded as highly sensitive data; If {A1÷[(2 / 3)T]}≥{(A-A1)÷[(1 / 3)T]}, it means that the number of complaint information involving the data to be accessed in the complaint information has not increased sharply in the recent period, and the data to be accessed is recorded as low-sensitivity data.
[0024] The step of judging whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data based on the pairing relationship in the first position set is as follows: Get the number of pairing relationships in the first position set, denoted as D; Mark the area corresponding to each geographical location in the D pairing relationships in the first location set on the map; Set the marking times ratio threshold Z3, and count the times each area in the first position set is marked and compare it with the marking times ratio threshold Z3 as the condition for judging whether the area is a risk area. When the marking times exceeds the ratio threshold, it means that the area has the conditions to become a risk area. When the marking times does not exceed the ratio threshold, it means that the area does not have the conditions to become a risk area. Get the number of times each area is marked; For each marked area, if the ratio of the number of times the area is marked to D is ≥ Z3, it means that the area has the conditions to become a risk area, and the area is recorded as a risk area; If the ratio of the number of times a region is marked to D is less than Z3, it means that the region does not meet the conditions to become a risk area and no processing is performed; Get the number of times the risk area is marked, recorded as M; Mark the geographical locations corresponding to the M IP addresses in the risk area, and continue to mark the address locations of each visiting user in the risk area to determine whether there is a concentrated distribution of users in the risk area; Obtain the coordinate values of the longitude and latitude corresponding to the M geographical locations marked in the risk area, which are recorded as (E1, F1), (E2, F2), (E3, F3)...(E M , F M ), perform algebraic processing based on the latitude and longitude coordinates corresponding to each IP address to determine whether the access users corresponding to the M IP addresses are concentratedly distributed; Get the average of the longitude and latitude values, record them as E and F respectively, and calculate them as E=(E1+E2+E3……E M )÷M, F=(F1+F2+F3……F M )÷M; The longitude and latitude coordinates (E, F) are recorded as the center coordinate No. 1, and the center coordinate No. 1 is the geometric center of the M longitude and latitude coordinates; Get (E1, F1), (E2, F2), (E3, F3)... (E M , F M ) to the center coordinate of No. 1, which is recorded as G1, G1, G1...G M ; Get G1, G1, G1...G M The average value is recorded as G AVG , calculated as G AVG =(G1+G2+G3……G M )÷M; Take the center coordinate of No. 1 as the center and make a circle with radius G AVG circle, get (E1, F1), (E2, F2), (E3, F3)... (E M , F M ) Among the geographical locations corresponding to the M longitude and latitude coordinates, the number of geographical locations located in the area covered by the circle is denoted by G.
[0025] The step of judging whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data according to the pairing relationship in the first position set further includes: A threshold Z4 for the proportion of the number of geographic locations is set. The function of Z4 is to determine whether there is a concentrated distribution of users in the risk area. When the proportion of the number of geographic locations in the area covered by the circle is greater than or equal to the threshold Z4 for the proportion of the number of geographic locations, it indicates that there is a concentrated distribution. Therefore, it is necessary to further determine whether the number of risky users in the area covered by the circle will cause the risk of the data to be accessed being converted from low-sensitivity data to high-sensitivity data. A threshold Z5 for the proportion of risky users is set. The function of Z5 is to determine whether the number of risky users in the area covered by the circle will cause the risk of the data to be accessed being converted from low-sensitivity data to high-sensitivity data. When the proportion of risky users in the area covered by the circle is greater than or equal to the threshold Z5 for the proportion of risky users, the number of risky users in the area covered by the circle will cause the risk of the data to be accessed being converted from low-sensitivity data to high-sensitivity data. When the proportion of risky users in the area covered by the circle is less than the threshold Z5 for the proportion of risky users, the number of risky users in the area covered by the circle will not cause the risk of the data to be accessed being converted from low-sensitivity data to high-sensitivity data. If G÷M≥Z4, it means that there are concentrated users in the risk area. It is necessary to further determine whether the number of risky users in the area covered by the circle will cause the risk of the data to be accessed being converted from low-sensitivity data to high-sensitivity data. Obtain whether there are risky users among the accessing users corresponding to the IP addresses in the area covered by the circle. If there are risky users, obtain the number of risky users, which is recorded as B. The risky users are specifically: If the cumulative number of complaints against a user is greater than 0, the user will be marked as a risky user; If the ratio of B to G (B÷G) ≥ Z5, it means that the proportion of risky users in the area covered by the circle is relatively large, which will cause the risk of the data to be accessed being converted from low-sensitivity data to high-sensitivity data. The area covered by the circle is recorded as a potential risk area, and the data to be accessed has the risk of being converted from low-sensitivity data to high-sensitivity data; If the ratio of B to G (B÷G) is less than Z5, there is no risky user among the accessing users corresponding to the IP addresses in the area covered by the circle, or G÷M is less than Z4, then the data to be accessed does not have the risk of being converted from low-sensitivity data to high-sensitivity data and will not be processed; by counting the number of times each area in the No. 1 position set is marked, the area where the number of times it is marked exceeds the percentage threshold is defined as a risk area, and the address location of each accessing user continues to be marked in the risk area to determine whether there is a concentrated distribution of users in the risk area. If there is a concentrated distribution of users, then whether there are risky users in the area where users are concentrated is obtained. If there are risky users and the proportion of risky users is high, the area where users are concentrated is recorded as a potential risk area, and the data to be accessed has the risk of being converted from low-sensitivity data to high-sensitivity data; this scheme can identify and lock potential risk areas. If the IP address of the accessing user is in the potential risk area, the access risk of the accessing user is increased; this method makes privacy protection targeted and can perform more stringent access control on users in specific areas.
[0026] The access risk of obtaining the access user is specifically: For users who are complained about: If the cumulative number of complaints against the accessing user = 1, the accessing account will be banned for 30 days; If the cumulative number of complaints against the visiting user = 2, the user's account will be banned for 180 days; If the cumulative number of complaints against the visiting user = 3, the user's account will be banned for 365 days; If the cumulative number of complaints against the visiting user = 4, the user's account will be permanently banned; Get the cumulative number of bans for the access user. If the cumulative number of bans for the access user is greater than 0 but less than or equal to 2, the access user has a Class I access risk, and the Class I access risk value is recorded as P1. If the cumulative number of bans for the access user is greater than 2, the access user has a first-class access risk, and the first-class access risk value is recorded as P2, P1<P2; If the cumulative number of bans for the accessing user is equal to 0, then the accessing user does not have a Class I access risk.
[0027] The obtaining of the access risk of the access user further includes: Set the access user existence time threshold T2; Get the existence time of the accessing user, recorded as C; Get the time when the access user completes registration, which is recorded as the registration time; The time before the registration time and seven days after the registration time is recorded as the registration front end time; The time period between the registration front-end time and the registration time is recorded as the registration front-end time period; If the existence time of the accessing user C is less than T2, it means that the existence time of the accessing user's account is short. The IP address of the accessing user is obtained and recorded as the target IP address. The access to the shared supply chain carbon footprint disclosure data can be tracked through the IP address. Users with the same IP address as the visiting user are recorded as one type of user; If there is a type of user in the registration front-end time period, and this type of user is banned, then the access user has a second type of access risk, and the second type of access risk value is recorded as Q; for access users with a short account existence time, obtain the IP address of the access user, and obtain the ban status of the account under this IP address. If an account under this IP address has been banned recently, it may be that the access user of the banned account has registered a new account again to access after being banned, so the access risk is high. Therefore, once a banned account is found, the newly registered account can be immediately monitored to detect and prevent malicious behavior in time; by checking the ban records under the IP address, such repeated attacks can be effectively prevented to protect data security; If there is no first-class user banned during the registration front-end time period, the accessing user does not have the second-class access risk; Set a distance threshold Z5. The function of Z5 is to determine whether the distance between the visiting user and the center coordinate of No. 1 will cause access risk to the visiting user. When the distance between the visiting user and the center coordinate of No. 1 is less than the radius of the potential risk area, it means that the visiting user is in the potential risk area and has a greater access risk. When the distance between the visiting user and the center coordinate of No. 1 is greater than the radius of the potential risk area but less than Z5, it means that the visiting user is near the potential risk area and has a smaller access risk. When the distance between the visiting user and the center coordinate of No. 1 is greater than Z5, it means that the visiting user is not near the potential risk area and therefore does not have an access risk. If the geographical location corresponding to the target IP address is in a potential risk area, it means that the access user has a great access risk. Then the access user has three types of access risks, and the three types of access risk values are recorded as R2; If the geographical location corresponding to the target IP address is not located in the potential risk area, and the distance between the geographical location corresponding to the target IP address and the center coordinate of No. 1 is ≤ Z5, it means that the access user is located near the potential risk area and has a greater access risk. Then the access user has three types of access risks, and the three types of access risk values are recorded as R1, R1<R2; If the distance between the geographical location corresponding to the target IP address and the center coordinates of No. 1 is greater than the distance threshold Z5, then there is no third-level access risk for the accessing user.
[0028] The determination of whether the accessing user can access the data to be accessed is based on the access risk of the accessing user and the type of the data to be accessed, specifically: Get the total access risk value of the access user, denoted as U; The total access risk value is specifically the sum of the first-category access risk value, the second-category access risk value, and the third-category access risk value; If the access user has one type of access risk and three types of access risks, and the value of the first type of access risk is P2, and the value of the third type of access risk is R3, then the total access risk value of the access user is U=P2+R3; Set a total risk value threshold Z6. The function of Z6 is to determine the risk type of the accessing user. When the total access risk value of the accessing user is greater than or equal to the total risk value threshold Z6, it means that the access risk of the accessing user is high, so the accessing user is recorded as a high-risk user; when the total access risk value of the accessing user is less than the total risk value threshold Z6, it means that the access risk of the accessing user is low, so the accessing user is recorded as a low-risk user; The total access risk value of the access user U≥Z6 indicates that the access risk of the access user is high, and the access user is recorded as a high-risk user; The total access risk value of the access user U<Z6, indicating that the access risk of the access user is low, and the access user is recorded as a low-risk user; When the data to be accessed is low-sensitivity data and the accessing user is a low-risk user, the accessing user can directly access the data to be accessed; When the data to be accessed is low-sensitivity data and the accessing user is a high-risk user, the accessing user can directly access the data to be accessed after the user's approval; When the data to be accessed is highly sensitive data and the accessing user is a low-risk user, the accessing user can directly access the data to be accessed after the user's approval; When the data to be accessed is highly sensitive data and the accessing user is a high-risk user, access will be denied; the risk value of the accessing user is evaluated based on multiple factors, including the number of complaints and IP address, etc., which can dynamically evaluate the user's access risk, and then calculate the total risk value of the accessing user, and determine the access rights of the accessing user in combination with the sensitive type of the data; if the user's risk value exceeds the set threshold, the system will regard it as a high-risk user, thereby restricting its access rights; this solution dynamically controls the user's access rights based on the data sensitivity type and the user's total risk value, thereby improving the accuracy and security of access control; compared with a single permission control method, this method can adjust user permissions according to the access risk value, effectively reducing the possibility of data being maliciously accessed or improperly used; in this way, the solution achieves hierarchical and refined privacy protection, making data sharing safer.
[0029] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.
[0030] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the technical principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.
Claims
1. A privacy protection method for data sharing, characterized by: include, The user who applies for access to the data is recorded as the access user, and the owner of the data that the access user applies to access is recorded as the holding user; Record the data requested by the accessing user as data to be accessed; Obtain the number of complaint information involving the data to be accessed among all complaint information; The complaint information includes the data involved in the complaint and the time of the complaint; Judging whether the data to be accessed is high-sensitivity data or low-sensitivity data according to the number of complaint information involving the data to be accessed in the complaint information; Establish position set number one; If the data to be accessed is low-sensitivity data, obtain the IP address of the user who applies to access the data to be accessed, obtain the geographical location and longitude and latitude coordinates corresponding to each IP address, form a pairing relationship between the IP address and the geographical location and longitude and latitude coordinates corresponding to the IP address, and include all pairing relationships in the first location set; Based on the pairing relationship in the first position set, determine whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data; Get the access risk of the access user; Based on the access risk of the accessing user and the type of the data to be accessed, determine whether the accessing user can access the data to be accessed.
2. A privacy protection method for data sharing according to claim 1, characterized in that: The method of determining the sensitive type of the data to be accessed according to the number of complaint information related to the data to be accessed in the complaint information is specifically: Obtain the number of complaint information involving the data to be accessed in the complaint information, the number is recorded as A; Set the number threshold Z1; If A ≥ Z1, the data to be accessed is recorded as highly sensitive data; If A<Z1, obtain the existence time of the data to be accessed, recorded as T days; Set the data existence time threshold T1, the unit is set to day, and set the ratio threshold Z2; If T≤T1, obtain the ratio of A to T and calculate it as A÷T; If (A÷T) ≥ Z2, the data to be accessed is recorded as highly sensitive data; If (A÷T) < Z2, the data to be accessed is recorded as low-sensitivity data; If T>T1, obtain the time when the data to be accessed is uploaded and record it as the upload time; The time after the upload time and with an interval of (2 / 3) T from the upload time is recorded as the front-end time, and the time after the upload time and with an interval of T from the upload time is recorded as the back-end time; The time period between the upload time and the front-end time is recorded as the front-end time period, and the time period between the front-end time and the back-end time is recorded as the back-end time period; The number of complaint information involving the data to be accessed in the complaint information in the front-end time period is obtained, recorded as A1, and the number of complaint information involving the data to be accessed in the complaint information in the back-end time period is obtained, recorded as A-A1; If {A1÷[(2 / 3)T]}<{(A-A1)÷[(1 / 3)T]}, the data to be accessed is recorded as highly sensitive data; If {A1÷[(2 / 3)T]}≥{(A-A1)÷[(1 / 3)T]}, the data to be accessed is recorded as low-sensitivity data.
3. A privacy protection method for data sharing according to claim 1, characterized in that: The step of judging whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data based on the pairing relationship in the first position set is as follows: Get the number of pairing relationships in the first position set, denoted as D; Mark the area corresponding to each geographical location in the D pairing relationships in the first location set on the map; Set the marking times percentage threshold Z3; Get the number of times each area is marked; For each marked area, if the ratio of the number of times the area is marked to D is ≥ Z3, the area is recorded as a risk area; If the ratio of the number of times a region is marked to D is less than Z3, no processing is performed; Get the number of times the risk area is marked, recorded as M; Mark the geographical locations corresponding to M IP addresses in the risk area; Obtain the coordinate values of the longitude and latitude corresponding to the M geographical locations marked in the risk area, which are recorded as (E1, F1), (E2, F2), (E3, F3)...(E M , F M ); Get the average of the longitude and latitude values, record them as E and F respectively, and calculate them as E=(E1+E2+E3……E M )÷M, F=(F1+F2+F3……F M )÷M; Record the longitude and latitude coordinates (E, F) as the center coordinates of point 1; Get (E1, F1), (E2, F2), (E3, F3)... (E M , F M ) to the center coordinate of No. 1, which is recorded as G1, G1, G1...G M ; Get G1, G1, G1...G M The average value is recorded as G AVG , calculated as G AVG =(G1+G2+G3……G M )÷M; Take the center coordinate of No. 1 as the center and make a circle with radius G AVG circle, get (E1, F1), (E2, F2), (E3, F3)... (E M , F M ) Among the geographical locations corresponding to the M longitude and latitude coordinates, the number of geographical locations located in the area covered by the circle is denoted by G.
4. A privacy protection method for data sharing according to claim 1, characterized in that: The step of judging whether the data to be accessed has a risk of being converted from low-sensitivity data to high-sensitivity data according to the pairing relationship in the first position set further includes: Set the geographical location ratio threshold Z4 and the risk user ratio threshold Z5; If G÷M≥Z4, obtain whether there are risky users among the visiting users corresponding to the IP addresses in the circle coverage area. If there are risky users, obtain the number of risky users, recorded as B; The risky users are specifically: If the cumulative number of complaints against a user is greater than 0, the user will be marked as a risky user; If the ratio of B to G (B÷G) ≥ Z5, the area covered by the circle is recorded as a potential risk area, and the data to be accessed has the risk of being converted from low-sensitivity data to high-sensitivity data; If the ratio of B to G (B÷G) is less than Z5, there are no risky users among the accessing users corresponding to the IP addresses within the circle coverage area, or G÷M is less than Z4, then the data to be accessed does not have the risk of being converted from low-sensitivity data to high-sensitivity data.
5. A privacy protection method for data sharing according to claim 1, characterized in that: The access risk of obtaining the access user is specifically: For users who are complained about: If the cumulative number of complaints against the accessing user = 1, the accessing account will be banned for 30 days; If the cumulative number of complaints against the visiting user = 2, the user's account will be banned for 180 days; If the cumulative number of complaints against the visiting user = 3, the user's account will be banned for 365 days; If the cumulative number of complaints against the visiting user = 4, the user's account will be permanently banned; Get the cumulative number of bans for the access user. If the cumulative number of bans for the access user is greater than 0 but less than or equal to 2, the access user has a Class I access risk, and the Class I access risk value is recorded as P1. If the cumulative number of bans for the access user is greater than 2, the access user has a first-class access risk, and the first-class access risk value is recorded as P2, P1<P2; If the cumulative number of bans for the accessing user is equal to 0, then the accessing user does not have a Class I access risk.
6. A privacy protection method for data sharing according to claim 1, characterized in that: The obtaining of the access risk of the access user further includes: Set the access user existence time threshold T2; Get the existence time of the accessing user, recorded as C; Get the time when the access user completes registration, which is recorded as the registration time; The time before the registration time and seven days after the registration time is recorded as the registration front end time; The time period between the registration front-end time and the registration time is recorded as the registration front-end time period; If the access user's existence time C < T2, obtain the access user's IP address and record it as the target IP address; Users with the same IP address as the visiting user are recorded as one type of user; If there is a type of user in the registration front-end time period and this type of user is banned, the accessing user has a type 2 access risk, and the type 2 access risk value is recorded as Q; If there is no first-class user banned during the registration front-end time period, the accessing user does not have the second-class access risk; Set distance threshold Z5; If the geographical location corresponding to the target IP address is in a potential risk area, the access user has three types of access risks, and the three types of access risk values are recorded as R2; If the geographical location corresponding to the target IP address is not located in the potential risk area, and the distance between the geographical location corresponding to the target IP address and the center coordinate of No. 1 is ≤ Z5, then the access user has three types of access risks, and the three types of access risk values are recorded as R1, R1<R2; If the distance between the geographical location corresponding to the target IP address and the center coordinates of No. 1 is greater than the distance threshold Z5, then there is no third-level access risk for the accessing user.
7. A privacy protection method for data sharing according to claim 1, characterized in that: The determination of whether the accessing user can access the data to be accessed is based on the access risk of the accessing user and the type of the data to be accessed, specifically: Get the total access risk value of the access user, denoted as U; The total access risk value is specifically the sum of the first-category access risk value, the second-category access risk value, and the third-category access risk value; If the access user has one type of access risk and three types of access risks, and the value of the first type of access risk is P2, and the value of the third type of access risk is R3, then the total access risk value of the access user is U=P2+R3; Set the total risk value threshold Z6; The total access risk value of the access user is U≥Z6, and the access user is recorded as a high-risk user; The total access risk value of the access user U<Z6, and the access user is recorded as a low-risk user; When the data to be accessed is low-sensitivity data and the accessing user is a low-risk user, the accessing user can directly access the data to be accessed; When the data to be accessed is low-sensitivity data and the accessing user is a high-risk user, the accessing user can directly access the data to be accessed after the user's approval; When the data to be accessed is highly sensitive data and the accessing user is a low-risk user, the accessing user can directly access the data to be accessed after the user's approval; When the data to be accessed is highly sensitive data and the accessing user is a high-risk user, access will be denied.
Citation Information
Patent Citations
Implementation scheme of privacy protection and security access based on distributed heterogeneous mass data
CN106789972A
Novel information security access control system and method based on user risk assessment
CN112685711A
Sensitive data anonymous access method based on knowledge signatures
CN113132116A
Access authority management method and equipment based on access behavior
CN116992411A
User-controllable privacy data authorization sharing method and system and medium
CN117544622A
