We're doing wireless real name certification for hotels and hotels. A lot of people are focusing on it."Can you pass the certification?"Go, think that just let the occupants enter a cell phone number for verification. But certification is only the first step in whether the whole system can stand at compliance check and see how it's keeping the log.
In a practical way, when many places are checking on the hotel's Internet compliance, you don't get to see if you have an authentication page."Is the log still there? How long can we check? Can you export to an IP by room by time?"The three questions were largely non-compliance, and the answer was not.
The statute requires how long the log will be retained.
The Public Security Department has specific regulations for Internet services premises.
Six months is the bottom line. Some places have been asked to go longer, like a year."Do you have a journal?"The question is also that the log format should be able to interface with the public security back-office system and at least support export in a standard format. If the log is on its own device, the format is private and only your tools can be opened, and the public security check may not be accepted.
What's the journal to remember?
A valid real name authentication log must contain at least the following fields: user ' s true identity information (name, type of document, identification number), Internet account or cell number, access time, break-time, IP address used (public and private IP both), associated equipment MAC address, access to AP location or room number.
There is a convenient missing point: IP matching before and after the NAT conversion. Hotel exports are usually with NAT, where all users share several public Internet IPs. If the logbook records only IPs without a private IP and time stamping, then public security will not be able to trace an individual or a room to a specific person.
In other words, there must be a connection query between the NAT map and the user-certification log. This is something that should be taken into account when designing the log structure, not until data are exported.
Storage and security of logs
The real name certification log contains the real identity of the occupants, which is much more sensitive than a normal weblog. Log storage security has to be at least in several ways: first, log data are encrypted during transmission and cannot be explicitly removed from the public network; second, storage devices are physically isolated or at least logically segregated, do not share storage space with other business systems and have no access control; third, log queries require authority management and operational audit, and who checks whose logs are recorded at what time.
In the actual hotel scene, the security of the equipment itself is also a problem if the logs are stored on local equipment in the store. The conditions in the shop rooms vary, either from a grocery room to one where the equipment can be encountered by anyone. So many chains of hotels start to synchronize the logs in real time to the group data centre or cloud platform, reducing the risk of local storage.
Data life cycle management cannot be kept in an unreserved condition.
The retention of a log is not the best thing to say, but it is stored on hard disks full with another hard disk. Personal information protection laws require that personal information handlers should be willing to remove personal information if their processing has been achieved, cannot be achieved, or no longer necessary for processing purposes.
This requires automated data life-cycle management capacity for the log system: a retention period, automatic clean-up after maturity or at least marking as"To be deleted", be confirmed by the administrator. Support data freeze during retention period——If there is an ongoing public security investigation, the corresponding logbook needs to be protected from automatic clean-up.
Auditability and traceability of logs
From an audit perspective, the log system itself needs to be protected from manipulation. This is a technical requirement for hotels, which are not financial institutions after all. But at least to write a log into an additional model, no modification or deletion of written log records is allowed. Any removal should have audit records independent of the log system.
A more practical approach is taken in the actual project: double-trip logs. The main log is available on local devices, and a copy is synchronized to group platforms or cloud ends in read-only fashion. This allows for a clean copy of compliance checks and audits even if the local equipment is malfunctioned or operated.
The U.N. Wireless Real name certification of hotel and hotel is not a compliance."You get the equipment and you comply."In preparing for a compliance audit, there is also an easy to ignore preparatory action: pre-do several logs export templates according to the normal inspection calibre used by public security. For example, all certified records of a week are exported over time, one month of online logs of a room by room number and one full person's Internet log by ID number. These templates are not useful in general terms, but once public security has asked for them to check."Get the logs from one of the rooms in the last six months.", without a template, it can take hours to get around. With preset templates, the results are available in minutes, and this is very helpful for compliance checks.