
The article trumpets the 1 million users figure but conveniently forgets that access to ContactPoint does not mean access to all records.
GPs can only see details of children registered with their surgery; teachers can only see children enrolled in their school; social services can only see children in their "area". And so on.
In other words, ContactPoint users cannot see any more childrens' records than they *already have access to*.
So why have the database if access is so restricted? Because they can see more info. For example a GP almost certainly won't currently know who a child's teacher is. So when the child comes into the surgery with unexplained bruising, the GP can't easily contact the teacher to ask if the parents are lying when they claim the child has been bullied at school, or fell over in the playground or whatever. With ContactPoint access they can.
[Aside: Personally I think this is a "good thing". However, it's all a total waste of money if more "Baby P's" are going to be allowed to happen. There's no point giving those involved with a child easy ways to warn about abuse if social services are going to do fuck all about it.]
There are occasions when a user would want to search for a child that they do not normally have access to. For example, police in one town find a runaway child from the other end of the country. To search for this child they need to invoke "break glass" functionality. Doing so automatically warns that user's supervisor (who may not have access to children's records at all but has access to ContactPoint for management purposes). The supervisor is trusted to determine whether the break glass facility is used legitimately or not. (E.g the duty sergeant may do it ten times a week whereas an ordinary constable may never need to do so.)
Yes, the two of them could abuse this arrangement but that requires collusion.
To the other posters with concerns:
@Ash: users can obviously leave the terminal logged in. However, login is two-factor so the owner of the token that had been (ab)used would get the blame for any accesses carried out. All accesses are audited.
@Nick: ditto the need for a token to log in. So even if Gov. gateway data is out in the open, it can't be used to log in.
@Norman Publicus: You are exactly right and I hope my explanation above goes some way to addressing your concerns.
@John Ozimek: all these people *already* have access to child details by the nature of their jobs.
@AC 14:07: just because the agency you work for is poor at data security, does not mean that ContactPoint will be. From what you say, you should be invoking whistleblower legislation to make a formal complaint.
@AC 14:10: "special" cases include MPs sprogs, celebrities sprogs etc. It is inevitable that some user somewhere will ill-advisedly "test the security of the system" by trying to look up a celeb's kid's details. The user's attempt will be audited, flagged-up and they will be spoken to by a supervisor. It's better that they fail and be warned/disciplined rather than succeed and be warned/disciplined.
@AC 14:51 The test databases are as carefully controlled as the real one in. (Same data centre security, same DBA employment vetting etc.) But no access from the outside world - so actually more secure than the real one.
@Chris Thorpe: two factor authentication is used. That doesn't stop the user leaving their token on the desk with a post-it with their pin on. However they would be effing stupid to do so: all accesses are logged so if a child is kidnapped and abused, for example, the first thing the police will find is that the child was the subject of a ContactPoint search and will be round to that user PDQ.
@AC 15:10
1) The database is not on DVD, trust me. :-)
2) The council already have a legal obligation to ensure that your child is educated so they *must* know whether he/she is enrolled in a school or being educated at home.
3) The same way that schools identify children now: first name, middle name, surname, dob, address etc. No id card required.
@AC 15:26 All access to ContactPoint is audited. A user could always try to add an unfounded allegation onto the system but they would always be traceable.
@Nigel: I would like to say that it is "impossible" for a single person to "leak" all of the data. However that can never be true. Someone could always turn up, shoot the security guards and threaten the DBAs with a pistol until they get the data on a single disk. But a person with the that kind of motivation and access to weaponry is unlikley to want data.
@The Other Steve
It's true. IT staff won't have access. It is perfectly possible to administer a faulty webserver without needing access to the database. If there is a fault on a DB server, the DBA can be supervised by a, well, supervisor, to ensure that he only does DBA things and not look at the data.
Can you cleanse, de-dupe data without looking at it? Of course you can: no single person is going to look at n million records and de-dupe them. Automated matching eliminates most duplicates. Somethings will inevitably be impossible to resolve atuomatically. These are reported back to the local authority of the child in question to resolve. So the person doing the de-duping is a local authority employee who already has access to the records in question.
@AC 16:19 Actually it is relatively easy to secure a *centralised* database. Securing a *decentralised* one is much harder.