The free WiFi is already marked in the public places of shopping, hotels, hospitals and stations."Provision of WiFi"and"Provide WiFi with compliance"Many managers have no idea where the boundary is, either over-doing it and getting rid of users; or being under surveillance. Clear compliance boundaries, WiFi's real-name certification system is so secure and practical.
Which sites must be named first.
Not all WiFi is named, but the public provision of Internet access is largely out of reach. The first step in our project is to help clients identify the nature of the site and identify which SSIDs must be known and which can go online. The border has been drawn wrongly, and the system behind it is empty. It is recommended that managers first take their own type of location to check the statutory requirements and not to guess for themselves about the undefined direct access to territorial security.
Match scenes with real name levels and collection fields
Compliance is not"The more we gather, the safer."The over-collection of personal information is also a violation. It is enough for the actual name of an ordinary public place to be mobile + identification code, or cell phone + identity check, to have no need to go up and sweep the face and record IDs. We've seen a café where customers can get WiFi to upload their identity photographs in order to receive information over and above their complaints. The real name certification system supports field collection by setting the scene, with the minimum public area gathering, and special sites (e.g. Internet cafes) only as much as they are required.
Privacy notification and user authorization cannot be avoided
The user should see the use statement and privacy clause of the authenticated WiFi before it, and then check for consent. This is not formalism, but a mandatory requirement under personal information protection laws. The WiFi authentication page must contain embedded notification text and authorization ticking, cannot be checked by default or hidden in a level III page. When we design the authenticated pages, the notice will be made into a simple layer with clear collection fields, uses, retention periods, withdrawals, and users’ read-and-read permission to enter certification.
Data localization and encryption are the bottom line.
Real name information is personal sensitive, and both transmissions and storage are encrypted. The cell number or identity information in the authentication process must be transmitted on the network through HTTPS or equivalent encryption channels, stored in a database that is either encrypted or dissensitive. There have been projects to explicitly contain real names in a regular table, which has been misled by insiders and created leaks. Compliance boundaries clearly require sensitive information to be protected throughout the entire time, and WiFi's actual name certification system should be designed as a base rather than an option.
You have to stay in the same place. It's not long, it's short.
The logs are kept for a statutory minimum period, usually 60 days, depending on the type of place and territorial requirements. They are too short, monitored for an absence of time in order to check, non-compliant; they are too long, violating the principle of minimizing personal information storage periods. WiFi authenticated systems need to be able to configure retention periods as required by statute, self-cleaning due to maturity and cleaning up actions themselves with marks. We recommend that customers make retention strategies into possible configurations, and that regulations require direct changes in parameters without code. This border is not well-stamped, and the system is stuck within the statutory area.
Reporting to the public only takes the designated route.
The WiFi operator wants to use the real name data for user drawings and precision marketing, which is used in violation of compliance boundaries."Regulatory reporting"and"Business analysis"Two streams of data flow, the reporting module reads only necessary fields and even specifies a given address. Managers must understand that real-name data is not an operating asset, they are compliance obligations, and they cannot touch commercial uses.
Physical or logical isolation of the visitors ' network and internal networks
The real name WiFi is intended for the public and the internal office network runs a business system, which must be isolated. Sharing a network, where visitors can theoretically access their own resources once certified by an actual name is a huge security risk and contrary to the principle of compliance with respect to network zoning. When they arrive, the visitor WiFi will export VLAN alone, with the real-name certification system running the area.
You have to think ahead of yourself when you're in trouble.
The real name certification system is installed and does not represent a great deal of success. Regulatory regulation may require that the authentication and online recording be obtained for a certain period of time, and that the system be provided quickly and accurately. This requires a stable, complete and time-segmented query interface. We suggest that managers practice once when they are on the system."Control of the certification"Process, confirm that the link from request to release data is not working and accurate. Many units do not practice."I can find out. I can tell."This is a test of the system ' s data governance capacity more than certification itself.