Comment

Will ID cards emerge from the data disaster ashes?

The ability of the UK government to expose its citizens' personal data to the rest of the world appears unbounded. This week alone finds us surveying the wreckage after the details of three million drivers and thousands of pensioners follow those of half the population - those on child benefit - and have gone walkies.

And what has been the government's response? Clearly, it hasn't wanted to say too much in the light of a review or two that need to draw conclusions before remedies can be found. But chancellor of the exchequer Alistair Darling has stuck his neck out and come up a cunning analysis.

He says that the government needs to simplify organisational structures in some departments and review data-protection laws. The various departments concerned need clearer lines of responsibility, he reckons.

It all sounds pretty good, doesn't it? There's a bit of humble pie in there, along with a vague commitment to do something - anything - to help avoid it all happening again. Although the odds are that it will, given the glacial speed of change within large organisations such as the civil service. I know: I've worked there.

So the chancellor continues that we need some form of information Tsar to spot-check public sector organisations, and improve the way that data security practices are followed. So far, so flannelly.

But the civil service runs on data. Its job is about processing data, and moving it about. How on earth is a high-profile bod, no matter how many staff he or she is blessed with, going to control information sloshing around inside the whole civil service?

What's needed is not spot checks but solid education in the basics of data security -- for everyone, from the mandarins downwards. They all deal with our data, so they all need to be aware.

The other element of Alistair Darling's recipe is a sleight of hand. He talks about simplification of organisational structures in government. These are weasel words behind which hides the amalgamation of databases.

In other words, instead of having the child benefit database moved to the audit office, or drivers' details ferried off to the tax office, the best thing is to bring all that data together. Fewer chances of breaches, would appear to be the thinking, if it's all in one place.

And which other pet project stands to gain if all your data is housed in one place? Ah yes, ID cards.

Or is that just a step too Machiavellian?