One of the most painful things about Portal's transporter is that a full-time Internet account in the dormitory. The sharing of accounts seems small, and it makes the bill completely unreal, and also poses security and audit risks: real events, with logs full of the same number, and no specific person to follow. We do campus web projects, so sharing is almost the type of matching capability that all schools need, but it is never a single function, but a combination box.
Practice I: Binding permissible terminals
The most basic move is a number of devices that can be tied. The mobile phones, tablets and notebooks used by students are registered, so that they can be removed before new ones are added. We usually give two or three units to accommodate the multi-equipment reality and block the sharing of classes.
Practice II: Multiple login and checkout of same account numbers
The same account entry is in block A, and B is kicked out or asked to confirm twice that it prevents a number from moving across the dormitory. We have seen a much more sophisticated way of playing, which is to hold the login position on the floor and even on the bedroom, and an unusual login directly. This action is particularly useful for blocking sharing because the essence of sharing is that accounts live simultaneously in multiple locations.
Practice III: Register of commonly used equipment
Registering the usual equipment of students and checking it out once, for example by text messages or email. We have done statistics, and when we register the equipment, the number is dropped significantly because the person who borrows it has to pass a dent, which makes it easy to leave. Registration is not restricted; it is a roadblock for normal users and for unusual users.
Practice IV: Behavioural abnormality detection
The system can look at unusual signals: out-of-the-morning, single account traffic is far more normal, multiple login over short periods of time, and these are triggering review. We usually make these tests into backstage statements, see the network center regularly, and then reprocess suspiciouss, not necessarily intercept in real time.
Practice V: Self-help release
Students themselves can see what equipment is tied and where it was entered on the self-help page, and find that it is not untied. We have counted it online, open equipment self-service management, and the number of passengers with an unusual number of nets and accounts has been cut by almost half because students themselves can discover problems and handle them.
It's the hardest way to balance things.
To prevent sharing, too many students are calling out, using too loosely and at what threshold, depending on how many complaints the school’s management culture and network centres can handle. We generally recommend that it be relaxed and tightened, with full observation data available early on the line, and then that we make some adjustments. Don’t get stuck, and it is easy to bounce back, but not to end up.
Not just technology.
Technology can block most, but not all. The access information and the account code is kept up to date so that students know what happens when they share accounts. We've seen schools with very hard technology, but with few systems, where students do not know it is illegal, but find the school system useless.
Shut up: A combination of fists, not single points
I'm gonna leave a message to the manager.
Sometimes it is necessary to let go temporarily, such as a network of test weekly rooms or a sleeping group. We suggest that Internet center teachers be given a temporary lift or a temporary release, open on demand and collect by maturity, instead of writing down strategies. Flexibility does not amount to losing control; the key is to leave marks and recoverables, with handlers holding switches, and not to react to special situations.
Data Reciprocal Sharing Mode
The sharing is not done. It is time to see the data that are shared, find high-impact beddings and hours, and target alarms or adjust thresholds. We have repeated the disks, some floor sharing was concentrated on weekend nights, and overall sharing rates dropped after targeted interventions. Data-driven fine-tuning is more effective than a single cut, and less triggers student rebounds.
Don't let the user feel protected.
And it's important to prevent sharing. We tend to wrap the restrictions into protection, for example by telling students that they can tie their equipment to a burglary sign instead of simply prohibiting sharing. To be clear, students have less resistance, more cooperation, and less management costs.
We generally recommend that schools report shared data on governance every semester, so that students see it being carefully managed rather than set. Transparency is a constraint in itself, knowing that people are watching and fewer people want to drill. The sense of continuity of governance is more important than a single punch.
The number of terminals, logs, equipment registers, behavior testing, self-help management are the only combination that is stable. Finding a balance and then adding to the system will make Portal really work on this matter.