Sunday 25 September 2016

RIP IDA – privacy/identity assurance principles

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
We have seen how Digidentity, one of the Government Digital Service's "identity providers", can unilaterally revoke your on-line GOV.UK Verify (RIP) identity. In GDS's projected digital-by-default internet era world, with no on-line identity you won't exist.

We have seen how users of GOV.UK Verify (RIP) who registered with Barclays and the Post Office may find it impossible to access public services.

Cassidian, Ingeus, Mydex, PayPal and Verizon have all pulled out as "identity providers" to GOV.UK Verify (RIP).

Who does that leave?

Among others, Safran Morpho/SecureIdentity:


As you can see, back in February 2016 DMossEsq managed successfully to register for GOV.UK Verify (RIP) with Safran Morpho/SecureIdentity.

GDS's registration dialogue has been updated since then. They try to point new applicants at the "identity providers" most likely to be able to register them. That means pointing them away from the "identity providers" least likely to be able to register them.

Day in, day out, for months now, since at least 12 April 2016, Safran Morpho/SecureIdentity have suffered the humiliating indignity of being fingered by GDS as useless:


Quite why Safran Morpho/SecureIdentity put up with this astonishing behaviour is unclear.

Whatever the answer, DMossEsq was registered with Safran Morpho/SecureIdentity but when he tried to log on to HMRC's on-line self-assessment service the other day through Safran Morpho/SecureIdentity, he failed. Just as he had already failed with the Post Office. And Barclays. And Digidentity.

Like the Post Office, Safran Morpho/SecureIdentity is not properly a certified company. They were supposed to be certified by tScheme by May 2016, but it's never happened. When GDS tell you that all their "identity providers" are certified companies, they're wrong:


But that isn't the problem in this case. DMossEsq closed his account with Safran Morpho/SecureIdentity almost as soon as he opened it. That's why he can't log on to HMRC via Safran Morpho/SecureIdentity.

Why did he close the account? Because DMossEsq doesn't approve of downloading apps onto his mobile phone and Safran Morpho/SecureIdentity insist that you do.

You might as well deliberately install a virus – look at the functions Safran Morpho/SecureIdentity's app can perform on the mobile phone screen snapshot alongside.

Do you want Safran Morpho/SecureIdentity modifying your system settings? Or finding and using your other accounts?

No. This is utterly intrusive. And quite unnecessary for the job in hand – in this case, to look at HMRC's on-line self-assessment service.

Which brings us to the nine identity assurance principles promulgated by PCAG, the Privacy and Consumer Advisory Group. GDS repeatedly claim that they abide by these principles which are designed to guard our privacy. But they don't.

The PCAG identity assurance principles for GOV.UK Verify (RIP) are shown below in black with comments in red:

Identity Assurance Principle
Summary of the control afforded to an individual
1. User Control
I can exercise control over identity assurance activities affecting me and these can only take place if I consent or approve them
Not true.
• How would you know if your identity was being checked by someone tomorrow morning at 9 a.m.?
• When did you give your consent for the credit rating agencies to share your personal information with GDS's "identity providers"? Or the banks or the mobile phone companies ditto? What about your health records? And your travel records? And your education records? And your social media accounts?
• Is your consent informed? Is your consent given freely or do you rather feel that you have no alternative?
2. Transparency
Identity assurance can only take place in ways I understand and when I am fully informed
Not true. Do you understand how GDS's identity hub works? Are you fully informed on the matter of security?
3. Multiplicity
I can use and choose as many different identifiers or identity providers as I want to
Not true.
• DMossEsq has found himself subsequently unable to use Digidentity, Barclays and the Post Office despite having previously registered with them.
• And GDS warn that Safran Morpho/SecureIdentity are unlikely to be able to prove the identity of new applicants.
• Who can make these choices? GDS decided back in April 2016 that, with some exceptions, applicants for a GOV.UK Verify (RIP) account have to be at least 20 years old. What are 19 year-old voters supposed to do? They're excluded. Ditto 19 year-old taxpayers and benefits claimants. Ditto 20 year-olds with little credit history. GOV.UK Verify (RIP) is not for everyone. Some people can't choose any identifiers at all, nor any "identity providers".
4. Data Minimisation
My interactions only use the minimum data necessary to meet my needs
Not true.
• Registration, which is an "interaction", requires more and more personal information, far more than is required for the Government Gateway and therefore far more than the minimum.
• When it comes to verification, another sort of "interaction", who knows how much personal information is exchanged?
• The quantity of personal information seems to be determined by the needs of GDS and the "identity providers" and the relying parties like HMRC. Not the needs of the mere users.
5. Data Quality
I choose when to update my records
Not true. Digidentity decided that DMossEsq had to upload an image of his passport. Without that, they decided, he can't use his Digidentity account.
6. Service User Access and Portability
I have to be provided with copies of all of my data on request; I can move / remove my data whenever I want
Not true.
• You can't remove your personal information whenever you want. All "identity providers" keep it for at least seven years.

• Digidentity, like other "identity providers", share your personal information with unnamed suppliers. You don't know who they are. You don't know what personal information of yours they have. How can you remove it?
• There has been talk for a long time of "signal sharing" to detect and prevent fraud. Who would perform this function? Could you remove your personal information from them?
7. Certification
I can have confidence in the Identity Assurance Service because all the participants have to be certified against common governance requirements
Not true.
• Some "identity providers" are certified by tScheme. Others aren't. The governance requirements aren't common.
• Nor are they obviously effective – Verizon are certified by tScheme but their services have nevertheless been withdrawn: "Recent changes to Verizon’s contracting structure mean that the service in its current form has not yet fully completed the external certification process. Verizon is working with Cabinet Office and independent auditors to make sure their service meets the contractual requirements, is fully accredited, and gives the best results possible for users".
• What about Zendesk? That's a company GDS have got participating in GOV.UK Verify (RIP). Are Zendesk certified? No. Ditto StatusPage.io – can you be confident about the uncertified StatusPage.io who participate by logging all activity in GOV.UK Verify (RIP)?
8. Dispute Resolution
If I have a dispute, I can go to an independent Third Party for a resolution
Not true. Can you name this independent third party? There was supposed to be a GOV.UK Verify (RIP) ombudsman. None has been appointed.
9. Exceptional Circumstances
I know that any exception has to be approved by Parliament and is subject to independent scrutiny
Not true. Do you know that parliament approves all exceptions? How do you know? What independent scrutiny? There is none.

Principle #6 promises that "I can move / remove my data whenever I want". This is false. When DMossEsq closed his Safran Morpho/SecureIdentity account his data wasn't removed. It will be kept by Safran Morpho/SecureIdentity for seven years.

DMossEsq can't remove his data whenever he wants. Principle #6 is being flouted, please see Safran Morpho/SecureIdentity's privacy policy:
1.4 How long does Morpho keep your personal data

Morpho will keep your data for as long as necessary in order to provide you with the services available on our website and applications.

Morpho may also keep your contact details to send you service-related information. Morpho might use your contact details for direct marketing in connection with the service provided.

Morpho may keep records of your activities for seven (7) years after the date on which your identity account is closed, to handle complaints or disputes that may arise.

Morpho will keep your personal data to the extent necessary to comply with all applicable laws, regulations and code of practices.
It's not just Safran Morpho/SecureIdentity. All the "identity providers" keep your data whether you want them to or not. The "control afforded to an individual" is nil.

And it's not just Principle #6. GOV.UK Verify (RIP) flouts all nine privacy principles. It doesn't abide by a single one (6 May 2016 1). How GDS can claim that they do abide by these principles is a mystery.

That is what they say: "GOV.UK Verify [RIP] protects users' privacy. It has been designed to meet the principles developed by our privacy and consumer advisory group". But it's not true, is it.

----------

Updated 11.11.16

Check the GOV.UK performance platform and you'll find that nine government services can be accessed using GOV.UK Verify (RIP). That's what GDS say. There are many qualifications that should be added to that claim of theirs.

Let's let that drop for the moment and instead note here that two more services are to be added to that modest list, please see GOV.UK Verify [RIP] welcomes 2 more DVLA services:
You can now use GOV.UK Verify [RIP] to access the DVLA’s Driving with a medical condition service and Renew your medical driving licence service.
That looks like one service, not two, but don't let's cavil. Note rather this claim:
GOV.UK Verify [RIP] has been designed to minimise storage of personal data, so drivers can be assured that their personal information remains safe and private.
It does not follow from personal information storage being kept to a minimum that your personal information is safe and private.

And the design of GOV.UK Verify (RIP) requires your personal information – in this case including medical information – to be sprayed all over the world. Nothing could make it less likely that your personal information is "safe and private".

Then there's this claim:
With GOV.UK Verify [RIP] connected to Driving with a medical condition, the DVLA can be sure be sure [doubly sure?] applicants are who they say there [they?] are ...
The US National Institute for Standards and Technology disagree. They say that GOV.UK Verify (RIP) offers relying parties like DVLA nothing more than self-certification. Spraying your data all over the world is all downside.

DVLA is the Driver and Vehicle Licensing Agency. GDS have driven a coach and horses through their identity assurance principles, please see main post above. The National Health Service don't think that GOV.UK Verify (RIP) meets the standards required for medical records. You might be well advised to listen to them.


Updated 4.1.17 1

Late last year the Government Digital Service (GDS) published three articles about the GOV.UK Verify (RIP) privacy assurance principles:

Applying Failing to apply
the identity assurance principles

to GOV.UK Verify (RIP):
30 November 2016 Part 1
9 December 2016 Part 2
20 Decmber 2016 Part 3
"We’ve blogged a lot about how user security and privacy is [are] at the heart of GOV.UK Verify [RIP]", GDS say in Part 1. True enough but blogging about them doesn't demonstrate that GOV.UK Verify (RIP) really does provide security and privacy.

"We’ve also talked about the Privacy and Consumer Advisory Group (PCAG)", GDS go on, "and one of their key outputs: the Identity Assurance Principles. These exist to inform and guide the privacy-related aspects of identity assurance, especially in GOV.UK Verify [RIP]". Agreed. That's the idea ...

... but of course it's our contention above that GOV.UK Verify (RIP) doesn't abide by the identity assurance principles. And that's precisely what GDS themselves demonstrate, at length, over the course of these three articles.

Take principle #8, for example, treated in Part 3: "If I have a dispute, I can go to an independent third party for a resolution".

What do GDS say?

"If a user wants to raise a complaint, then they can do so through the certified company’s user support". That's not an independent third party.

Also, "if the user is not satisfied with the result, then they can get in touch with the GOV.UK Verify [RIP] user support team. They can look into the user’s problem to help offer a solution, and they can also raise the complaint with Verify’s Privacy Officer". Neither the user support team nor the Privacy Officer is an independent third party.

Also, "user support has the ability to share anonymised and statistical outcomes with the independent PCAG for further investigation, if required". But principle #8 says that you can go to an independent third party. That's not the same as GOV.UK Verify (RIP)'s user support team going to PCAG.

Does GOV.UK Verify (RIP) abide by principle #8? Manifestly, no.

Principle #9 is: "Any exception has to be approved by Parliament and is subject to independent scrutiny".

What does that mean?

GDS say: "An exceptional circumstance within the privacy principles is defined as a situation where it’s agreed that the privacy principles we’ve just covered are not followed".

We've just seen that principle #8 isn't followed. So that's an exception. Has it been approved by Parliament? No. So principle #9 isn't followed either.

Neither are principle ##1-7.

GDS may have succeeded in convincing themselves that GOV.UK Verify (RIP) complies with PCAG's identity assurance principles. But no-one else.


Updated 4.1.17 2

The following comment has been submitted on GDS's blog post Applying the identity assurance principles to GOV.UK Verify: Part 3:
David Moss
Your comment is awaiting moderation.
"It’s worth noting that all of our certified companies are certified by tScheme ..."
Morpho, the Post Office and the Royal Mail are not certified by tScheme [*].
"... but not necessarily separately. This is because when a certified company uses the same system as another company that is already tScheme certified, then there is no need for a second certification of the same system".
Does that mean that Morpho, the Post Office and the Royal Mail are not doing any real identity assurance work? The work is really being done behind the scenes by someone else?
Who is doing Morpho's work for them?
Who is doing the Post Office's work for them?
Who is doing the Royal Mail's work for them?
----------
Link to this comment

Update 5.1.17 1

The DMossEsq comment above on the GOV.UK Verify (RIP) blog has been deleted and the following email response has been received:
From: Emily Ch'ng
Sent: 04 January 2017 14:49
To: DMossEsq
Subject: Your comment on the GOV.UK Verify blog

Dear David,

Thank you for your comment on the GOV.UK Verify blog. I am the blog's moderator.

I would like to let you know that I am unable to approve your comment as we do not discuss the subcontracting details of GOV.UK Verify's certified companies in the public domain as this is commercially sensitive and thus confidential information.

If you would like to find out further details about certified companies and tScheme, you are free to contact the certified companies themselves.

Many thanks for your interest in GOV.UK Verify.

Kind regards,
--

Emily
Digital Engagement Manager

Government Digital Service

Update 5.1.17 2

The following response to GDS has been sent:
From: David Moss
Sent: 05 January 2017 11:40
To: 'Emily Ch'ng'
Subject: RE: Your comment on the GOV.UK Verify blog, http://www.dmossesq.com/2016/09/rip-ida-privacyidentity-assurance.html#update3

Dear Emily

Thank you for your email.

In her blog post Applying the identity assurance principles to GOV.UK Verify [RIP]: Part 3
Orvokki Lohikoski, the GOV.UK Verify (RIP) privacy officer, writes:
"It’s worth noting that all of our certified companies are certified by tScheme, but not necessarily separately".
In other words, all of our certified companies are certified by tScheme except that they're not ...

... a museum quality example of self-contradiction that she attempts to resolve by saying:
"when a certified company uses the same system as another company that is already tScheme certified,
then there is no need for a second certification of the same system".

That inevitably raises the question in the mind of the public
which uncertified certified companies
rely on which certified certified companies,
a question which the Government Digital Service raise
but which you then say in your email that they will not discuss.
So why raise it?
It looks as though GDS are teasing the public.

Given that the service operated by Morpho – one of the certified companies – is not approved by tScheme,
which tScheme-approved company is really doing the work?
The same question needs to be raised in the cases of the Post Office and the Royal Mail.
Their services also are not approved by tScheme.
People think they are dealing with the Post Office, say, but in reality they're not.
People are being deceived by GDS's GOV.UK Verify (RIP).

Not only will you not answer the question on the GOV.UK Verify (RIP) blog which you moderate,
you won't even publish it – my comment on Ms Lohikoski's blog post has been deleted.

"Make things open: it makes things better", it says in the GDS Design Principles.
It would make things better in this case but,
for reasons of commercial sensitivity and confidentiality,
GDS are not being open.
The public are being lured into handing over sensitive personal information
in the hope that it will be treated confidentially
by certified companies that may not be certified.
But despite having to pay for the privilege, we are not allowed to know how the system works.

You recommend that I should raise the question
which non-tScheme-approved companies rely on which tScheme-approved companies
with the "identity providers" themselves.
Thank you for that recommendation, I shall do so.

That leaves the public and the certified companies to sort out their relationship with no assistance from GDS.
It cuts GDS out of the loop
in the identity assurance ecosystem/market
that GDS say they are trying to promote and regulate.
A market which relies on self-contradiction.
A market which moderates/suppresses public discussion of its workings
on the very forum which invites comments.
A market predicated on an openness which is not available precisely when it is needed.
A market which everyone acknowledges depends on trust.
What are the public to make of that?

Ms Lohikoski has the impssible task of convincing the public
that GOV.UK Verify (RIP) abides by the identity assurance principles
laid down by the Privacy and Consumer Advisory Group.
It manifestly doesn't.
And PCAG have undermined their own credibility by pretending that it does,
last March and in Ms Lohikoski's December blog post.

GDS have no experience of creating and operating a market and it shows.
GOV.UK Verify (RIP) is a mess.
By comparison, the stock market is a model of openness.

Yours sincerely
David Moss


RIP IDA – privacy/identity assurance principles

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
We have seen how Digidentity, one of the Government Digital Service's "identity providers", can unilaterally revoke your on-line GOV.UK Verify (RIP) identity. In GDS's projected digital-by-default internet era world, with no on-line identity you won't exist.

We have seen how users of GOV.UK Verify (RIP) who registered with Barclays and the Post Office may find it impossible to access public services.

Cassidian, Ingeus, Mydex, PayPal and Verizon have all pulled out as "identity providers" to GOV.UK Verify (RIP).

Who does that leave?

Thursday 22 September 2016

RIP IDA – the Post Office

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
We have seen how Digidentity, one of the Government Digital Service's "identity providers", can unilaterally revoke your on-line GOV.UK Verify (RIP) identity. In GDS's projected digital-by-default internet era world, with no on-line identity you won't exist.

We have seen how users of GOV.UK Verify (RIP) who registered with Barclays may find it impossible to access public services.

Cassidian, Ingeus, Mydex, PayPal and Verizon have all pulled out as "identity providers" to GOV.UK Verify (RIP).

Who does that leave?

Among others, the trusty old Post Office:


What happens when DMossEsq now tries to access HMRC's on-line self-assessment service? He enters his username and password, the Post Office send a one-time password to his mobile, he enters it and sees:


But don't get your hopes up because next thing you know, "Aw, Snap! Something went wrong".

There are four more "identity providers" to check – CitizenSafe/GB Group plc, Experian, the Royal Mail and SecureIdentity/Morpho. But we're really not having much luck with GOV.UK Verify (RIP), are we. It doesn't work. That's what it looks like.

And by the way, when we say "trusty old Post Office", remember that the Post Office isn't actually certified trustworthy by tScheme. Their application lapsed 18 months ago in February 2015.

Digidentity, surprisingly in view of our findings, is certified trustworthy. But the Post Office isn't. It's not a "certified company", whatever the Government Digital Service say.

The Post Office is only allowed to operate as an "identity provider" because of some otherwise undisclosed connection to Digidentity:
Post Office uses the same system as another provider which has been t-Scheme certified, so we [GDS] have agreed that there is no need for a second certification of the same system unless and until Post Office introduces anything that is different in its system for verifying identities, in which case that would need to be separately certified.
If you register for GOV.UK Verify (RIP) via the Post Office, are you really being catered for by Digidentity?

RIP IDA – the Post Office

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
We have seen how Digidentity, one of the Government Digital Service's "identity providers", can unilaterally revoke your on-line GOV.UK Verify (RIP) identity. In GDS's projected digital-by-default internet era world, with no on-line identity you won't exist.

We have seen how users of GOV.UK Verify (RIP) who registered with Barclays may find it impossible to access public services.

Cassidian, Ingeus, Mydex, PayPal and Verizon have all pulled out as "identity providers" to GOV.UK Verify (RIP).

Who does that leave?

Wednesday 21 September 2016

RIP IDA – Ingeus, Cassidian, Mydex, Paypal, Verizon, Digidentity and Barclays

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
We have seen how Digidentity, one of the Government Digital Service's "identity providers", can unilaterally revoke your on-line GOV.UK Verify (RIP) identity. In GDS's projected digital-by-default internet era world, with no on-line identity you won't exist.

In the remaining months of your existence, let's take a look at the other "identity providers". Are they behaving like Digidentity?

Ingeus – one of GDS's early "identity providers", they never provided anyone with a GOV.UK Verify (RIP) on-line identity. Ditto Cassidian. And Mydex. And PayPal. They all pulled out before they could do any harm. Verizon stayed a while, but now they, too, have pulled out. So that's five "identity providers" we don't need to worry about.

After Digidentity, DMossEsq signed up with Barclays. They're a bank. Banks are good at on-line identity management. Registration went smoothly:


Six months later:


It is almost inconceivable that DMossEsq should enter his username or password incorrectly. Nevertheless, try 'Need help signing in?' as suggested, and what does he see?


DMossEsq has dutifully tried repeatedly, every few minutes, but mobile security code generation just keeps on failing.

It's not looking healthy, is it, GOV.UK Verify (RIP)'s identity assurance. It's getting harder to feel confidence in it.

How on earth can a gigantic UK retail bank get into this embarrassing position?

Here's one theory.

The Barclays GOV.UK Verify (RIP) service depends in some unspecified way on Verizon. "We may share your personal information with ... Verizon, our technical services partner, so they can perform certain parts of the Identity Service on our behalf", it says in the Barclays privacy policy. Now that Verizon have disappeared perhaps Barclays can't function.

The theory may or may not be right. Either way, that's seven GOV.UK Verify (RIP) "identity providers" down and just four to go ...

... in a later post.

----------

Updated 22.9.16

"Seven GOV.UK Verify (RIP) 'identity providers' down and just four to go"? No. It's five to go – CitizenSafe/GB Group plc, Experian, the Post Office, the Royal Mail and SecureIdentity/Morpho. Not four. Five.


RIP IDA – Ingeus, Cassidian, Mydex, Paypal, Verizon, Digidentity and Barclays

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
We have seen how Digidentity, one of the Government Digital Service's "identity providers", can unilaterally revoke your on-line GOV.UK Verify (RIP) identity. In GDS's projected digital-by-default internet era world, with no on-line identity you won't exist.

In the remaining months of your existence, let's take a look at the other "identity providers". Are they behaving like Digidentity?

Ingeus – one of GDS's early "identity providers", they never provided anyone with a GOV.UK Verify (RIP) on-line identity. Ditto Cassidian. And Mydex. And PayPal. They all pulled out before they could do any harm. Verizon stayed a while, but now they, too, have pulled out. So that's five "identity providers" we don't need to worry about.

Tuesday 20 September 2016

RIP IDA – agile identity, now you are you, now you're not

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
"Congratulations!", they said in the email, "You have completed the registration process":


There he was, DMossEsq, all kitted up with a brand new on-line identity, provided by GOV.UK Verify (RIP) via Digidentity, one of the Government Digital Service's "identity providers".

Digidentity had collected all the details of DMossEsq's passport and driving licence, among other things, and here they were confirming that he is him, the person he claims to be. "Your registration has been completed" – that's what the email says. And polite to a fault, Digidentity even said: "Thank you for registering".

And yet yesterday, when DMossEsq tried to log in for the sixteenth time since that email, he couldn't get through to his personal tax account. There has been no communication from Digidentity since the email above but Digidentity now want more passport details before they'll confirm that DMossEsq is DMossEsq:


Digidentity want an image of the passport uploaded, using an app of theirs which has to be downloaded onto DMossEsq's mobile phone first:


The GOV.UK Verify (RIP) team make it all sound so easy. Register once and they'll vouch for you, they know who you are because you've already proved it and they'll tell HMRC or whoever yes, this is DMossEsq. You have to hand over an inordinate amount of personal information about yourself but at least you'll then be able to use public services on-line.

Not true.

The bargain has been broken. You've handed over the personal information. You still can't use public services on-line.

It seems that an "identity provider" can without warning decide that you aren't you after all and demand further proof without which you can't communicate with any government departments using GOV.UK Verify (RIP).

That could be serious. Suppose you were away from home without your passport, on a sales trip to the Northern Powerhouse, for example, selling gluten-free cupcakes to digital entrepreneurs, and you needed to pay your tax bill. You sit down in your hotel room confident that you can make this payment because you've got your trusty Digidentity on-line identity already set up ...

... only to find that your on-line identity has been taken away from you. Result? You have to pay interest on your tax and a penalty in addition. And there's no compensation. Thank you, GOV.UK Verify (RIP).

Even if you do have your passport with you in the hotel, why should you have to download an app from Digidentity? That's tantamount to deliberately installing a virus.

You never know where you are with GOV.UK Verify (RIP). That could be one reason no-one's using it.

How does this come about? How have the Government Digital Service (GDS) acquired the attitude that they can change the rules behind your back?

The answer is "agile".

Their agile software engineering methodology assumes that they can iterate. They can make changes to live public services all the time. That's what Google do with Chrome, for example. And Google embody the internet era. GDS want to transform government so that it becomes digital by default. And what does "digital" mean? Answer: "digital means applying the culture, practices, processes and technologies of the internet era to respond to people’s raised expectations". So that's what GDS can do with GOV.UK Verify (RIP).

They were warned about this, in January 2013, when four professors told them that: "there are risks that rapidly changing services will deter the takeup of digital services, not encourage it". They didn't listen.

----------

Updated 22.9.16

The matters above have been brought to Digidentity's attention and the Government Digital Service's.

GDS never respond, of course.

Digidentity have responded, please see tweets alongside.

In addition to those tweets, Digidentity also sent two identical emails saying "your identity document is accepted" (please see copy below).

Which document? They don't say.

Whatever their emails say, DMossEsq's GOV.UK Verify (RIP) account registered with Digidentity still doesn't work. He still can't use it to access his personal tax account.

Why doesn't the account work? It used to.

What's changed?

Are Digidentity allowed to withdraw the right to access public services from people to whom they have previously granted that right?

Should they notify people first?

Are they allowed to demand more and more intrusive access to people's personal information such as insisting on their app being installed on our mobile phones?

Can they change the rules as they're going along so that one day you are you and the next day you're not?

Are GDS comfortable with Digidentity creating people on-line and deleting them, wiping them out, so that they don't exist any more?

Do GDS even know it's happening or have they lost track?

These are general policy questions of interest to everyone. Digidentity's offer to discuss them in private won't do.

"We're building trust by being open" – that's GDS's claim. Time to prove it.

What identity document? No new document has been submitted.


Updated 12.6.17

DMossEsq has made no attempt to use his Digidentity GOV.UK Verify (RIP) account since 19 September 2016, please see above. Today, the following email was received:


"We're sorry but we couldn't verify your identity". Very odd. DMossEsq hasn't asked Digidentity to verify his identity. Perhaps someone else has. Who? Why?


Updated 14.6.17

It looked as though someone was trying to use one of DMossEsq's GOV.UK Verify (RIP) accounts, the one maintained by Digidentity, please see above.

An email to Digidentity elicited several prompt responses, please see below, for which they have been thanked.

In the event, it was not a third party but Digidentity themselves who were accessing the account, they were trying to do one of their periodic checks that the account is still kosher. It might improve the user experience in future to make that clear in the email automatically sent to the accountholder.
From: Support [mailto:helpdesk@digidentity.co.uk]
Sent: 13 June 2017 17:00
To: DMossEsq
Subject: [Digidentity] Re: Registration Query

##- Please type your reply above this line -##
Your request (8209) has been updated. To add additional comments, reply to this email.

Liz (Digidentity UK)
Jun 13, 18:00 CEST

Dear Mr Moss,

We have investigated your account further and it appears that our system went through some recent verification checks. These were automatically made on your account without you needing to log in. We require these checks from time to time in order to continue proving who you are.

As you did register quite a long time ago however, what I needed to do is reprocess your information so that we could still be sure that it was definitely you registering online. Now that I have done this, you are still fully verified.

I wish to apologise for any cause for concern. You should now be able to log into your Digidentity account in future and be redirected to the service you require.


Liz (Digidentity UK)
Jun 13, 17:24 CEST

Dear Mr Moss,

Thank you for your message.

What I have done is passed your account to the relevant team at the company in order to investigate further. I would like to thank you for your patience in the meantime. I will get back to you as soon as I have more information.


David Moss
Jun 13, 14:40 CEST

Sirs

I received the email below, “Your registration couldn’t be completed”. It’s a mystery. I have not attempted to use the account for many many months now. Is there any way you can investigate to see who was trying to use it?

Yours faithfully
David Moss

----------
From: noreply@digidentity.eu [mailto:noreply@digidentity.eu]
Sent: 12 June 2017 15:52
To: DMossEsq
Subject: Your registration couldn't be completed.

We’re sorry but we couldn’t verify your identity

Unfortunately we couldn’t verify your identity

Unfortunately your identity can’t be verified right now. Please go back to the GOV.UK Verify webpage or contact our helpdesk if you have any questions regarding your registration.

Kind regards,
Digidentity
Copyright © 2017, All rights reserved | https://www.digidentity.eu


This email is a service from Digidentity UK. Delivered by Zendesk
[N8O6PO-EPKO]
"CEST" turns up a lot in the correspondence with Digidentity. It stands for Central European Standard Summer Time, the timezone chosen by Zendesk, who provide user support services to the Government Digital Service and, so it appears, to Digidentity as well. As we were saying in March:
While claiming to put the user in control, GDS like us to spray our personal information all over the world when we register with GOV.UK Verify (RIP). Their heart really isn't in this privacy lark, is it. They use Eventbrite to organise events. They use Zendesk for user support. They use StatusPage for network monitoring. They use Survey Monkey for user feedback. All the personal information involved is stored and used beyond your control and now GDS want you to upload your CV to Jobvite.

Updated 20.5.18

In a re-run of what happened last year, 1 May 2018, DMossEsq got an email from Digidentity saying "Your registration couldn't be completed". Same day, DMossEsq brings this to Digidentity's attention and points out that he hasn't tried to register recently. Five more emails are exchanged over the next two days and then, 18.5.18, this email arrives from Digidentity:
From: Support <helpdesk@digidentity.co.uk>
Sent: 18 May 2018 10:09
To: DMossEsq
Subject: [Digidentity UK] Re: Account Query

##- Please type your reply above this line -##

Your request (999999) has been updated. To add additional comments, reply to this email.


Liz (Digidentity UK)
May 18, 11:08 CEST

Dear Mr Moss,

I wish to apologise for the delay in getting back to you regarding your query; I wanted to be clear on the matter before informing you.

Although I was not aware of this, it seems that you are well known to some of the Digidentity team. They informed me about some of your blogs where you have documented the GOV.UK Verify registration that we provide. One blog I want to draw to your attention is the following: https://www.dmossesq.com/2016/09/agile-identity.html. It seems that on this site, you posted your personal QR code.

The reason it took longer than expected for me to get back in touch with you is because I have been waiting on a response from another Digidentity user. In the end I did not get a reply from her, but from what we can gather, she may have searched for help online when uploading her own document via the app, possibly when she did not understand about how to scan a QR code. If you search for 'Digidentity QR code', your blog comes up in the image search.

What we can determine from this is that she scanned your own QR code instead, which was connected to your own account. As a result, her photo was uploaded to your account. Our system highlighted this mismatch in information, causing a registration rejection and sending the message you received. Although I did not understand this at the time, it is likely what caused the message to be sent last time you contacted us.

I suppose this is the consequence of posting a personal part of your registration online, which we strongly advise against users doing. Our system rightly detected when this occurred, but we are increasing security and have improved the scanning of the QR code process and it will only be possible to use the QR code as a one off (expires after use), meaning that this situation will no longer occur in future.

I hope that I have informed you sufficiently regarding the matter.

Kind regards,
Liz
Digidentity Customer Support
It seems that including the Digidentity QR code in the 20 September 2016 post above opened the door to people using it to try to register for a GOV.UK Verify (RIP) account.

The attempt(s) failed thanks to Digidentity's existing procedures. Digidentity have nevertheless, as a result of this incident, decided to enhance their procedures to make the use of their QR codes one-time only – a decent partial solution but note that DMossEsq didn't use the QR code so the first user would still be someone else not DMossEsq.

The QR code has now been obfuscated in the blog post above.

Search for 'Digidentity QR code' in Google images as Digidentity suggest and you will find the code Digidentity sent DMossEsq and several others.

In the interests of science, DMossEsq logged in to his Digidentity account to see the picture of the lady who tried to register using his QR code. Nothing doing, it's not there.

He then tried to log in to his personal tax account using his Digidentity GOV.UK Verify (RIP) account. Nothing doing, he's still not him:


The details provided on 23 February 2015 matched the information held by DVLA, HM Passport Office and Callcredit, please see above. Now they don't – now you are you, now you're not.

On the one hand, good work done by the Digidentity customer support team. And by Mr Marcel Wendt, the founder of Digidentity, whom DMossEsq bumped into at the Think.Digital Identity for government conference on 18 May 2018 and who knew all about the incident.

On the other hand, you don't get these problems with the Government Gateway. That's no doubt one reason why Her Majesty's Revenue and Customs don't recommend GOV.UK Verify (RIP). And why GOV.UK Verify (RIP) died.

RIP IDA – agile identity, now you are you, now you're not

No need to say it, it goes without saying, it should be obvious to all but,
just in case it isn't obvious to all,
IDA is dead.

IDA, now known as "GOV.UK Verify (RIP)",
is the Cabinet Office Identity Assurance programme.
"Congratulations!", they said in the email, "You have completed the registration process":


There he was, DMossEsq, all kitted up with a brand new on-line identity, provided by GOV.UK Verify (RIP) via Digidentity, one of the Government Digital Service's "identity providers".

Digidentity had collected all the details of DMossEsq's passport and driving licence, among other things, and here they were confirming that he is him, the person he claims to be. "Your registration has been completed" – that's what the email says. And polite to a fault, Digidentity even said: "Thank you for registering".

Sunday 18 September 2016

Ruminating about process

It's over two years since we looked at the achievements of the Government Digital Service (GDS). It looked to us then as though the big achievers digitalwise were not GDS at all, despite their noisy claims, but Her Majesty's Revenue and Customs (HMRC).

GDS aim one day to deliver something called "Government as a Platform (GaaP)". They have a publishing platform and a performance platform already up and running. They're working on at least three other platforms:
  • GOV.UK Verify (RIP) is meant to be a standard cross-government platform for identity assurance.
  • GOV.UK Notify is meant to be a standard way for government to send texts, emails and letters.
  • GOV.UK Pay is meant to be a standard way for government to collect payments.
GOV.UK Notify
Five days ago GDS published From pounds to pennies and months to minutes. They make a vague claim there to the effect that GOV.UK Notify could reduce central government costs and reduce the time taken to make changes. There's no guarantee that these reductions will be made. Just a claim.

"GOV.UK Notify now has 8 service teams sending texts and emails as part of our private beta", GDS tell us. That was 13 September 2016. Three days later, we learnt that it's not just government departments communicating with each other, government departments are communicating with some suppliers, too – Using GOV.UK Notify to communicate with suppliers. Presumably government departments and their suppliers have always communicated with each other. Is GOV.UK Notify an improvement? In what way? GDS don't tell us.

Back in July 2016, Civil Service World (CSW) magazine told us that GOV.UK Notify has "now begun sending messages to people applying for student finance and UK visas as part of the government’s invite-only public beta testing". There has been no update on the progress of this beta testing.

Cabinet Office minister Ben Gummer is quoted in the same CSW article as saying: "In GOV.UK Notify, we have developed an impressive, cost-saving product that can be used across any government department for lots of different services – making it easier for the public to interact with government and keep track of their applications and requests". There is no evidence to support these claims of his.

That's GDS.

Meanwhile the Daily Telegraph newspaper announces that HMRC have tested text messages with over 13,000 taxpayers and found that they increase tax payment rates by up to 7%. That looks like a properly constructed case in support of using texts, unlike the GDS claims.

What's more, there is no sign that HMRC are using GOV.UK Notify. They seem to have their own text-generating system. Bang goes GDS's hope of providing the single platform for government notifications.

GOV.UK Pay
"On Friday 2 September we took our very first live payment on GOV.UK Pay ... This is the first time we’ve processed a payment using a real card". That was GDS, in GOV.UK Pay is ready for business.

Would you describe a payments system that has processed one single solitary payment as "ready for business"?

Is that lonely only child of a payment enough evidence to support GDS's claim that "we're making it easier for citizens to make payments, and more efficient for civil servants to process these payments"?

GDS have four "beta partners" in the development of GOV.UK Pay – Companies House, the Environment Agency, the Home Office and the Ministry of Justice. HMRC isn't one of them.

According to GDS's UK government performance platform, HMRC received about 63 million payments in the year to September 2015. Quite why the statistics stop then is not clear.

What is clear is that we're talking about a lot of payments. HMRC have to think commercially and responsibly about how they collect these payments.

HMRC publish the methodology by which they calculate the cost of collecting each payment, 19p on average. GDS provide no methodology and no unit cost.

It would be worrying if HMRC entrusted their 63 million receipts p.a. to GOV.UK Pay on the basis of GDS's hot-headed claims about a single payment. But they haven't. Neither has anyone else.

GOV.UK Verify (RIP)
GDS's foray into the world of identity assurance is a disaster.

Meanwhile, HMRC added millions of users to their new personal tax accounts service this year, using the old Government Gateway.

And that's not their only on-line service by any means. HMRC processed 1.19 billion stamp duty reserve tax (SDRT) transactions, for example, in the year to September 2015 (digital take-up = 100%). Who is paying this SDRT? GOV.UK Verify (RIP) doesn't tell HMRC the answer because GOV.UK Verify (RIP) isn't involved.

Then there are the 412 million PAYE transactions (95.8%) and the 146 million customs transactions (100%) and the 63 million payments HMRC receive every year, please see above, etc ...

That's a lot of users and they all have to be identified. GOV.UK Verify (RIP) involvement? Nil.

HMRC v. GDS
It was an embarrassing mistake for Sir Jeremy Heywood, the Cabinet Secretary, to promote GDS as the organisation to deliver government transformation. As GDS themselves put it, "this page is no longer being updated".

It was a mistake for Matt Hancock, the previous Cabinet Office minister, and it's a mistake for Ben Gummer, the current one, please see above. It was a mistake for Stephen Foreshew-Cain, GDS's last executive director, and it would be a mistake for Kevin Cunnington, its first director general ...

... but he hasn't made that mistake. Instead, with John Manzoni, chief executive of the civil service and permanent secretary at the Cabinet Office, he's taking GDS in another direction, GDS promised 'national presence' as it takes over DWP's Digital Academy and leaves Aviation House.

That may be more up GDS's street. They are obviously happy ruminating about process – please see Using Activity Theory to build effective personas, for example, or 100 rounds of user research on GOV.UK Verify [RIP].

There's no doubt two years after the previous review that HMRC remain the great achievers when it comes to delivering on-line government transaction systems.

----------

Updated 5.3.17

A triumphant Government Digital Service (GDS) announced the other day on 1 March 2017 that GOV.UK Notify is now open for use.

"Back in May last year GOV.UK Notify sent its first messages as part of our invite-only beta phase", they said. "Now - after 9 months, 3.5 million messages, 32 live services, 850 code deployments, and 500 hours of user research — we’re making Notify available to all of central government".

GOV.UK Notify is a GDS service for central government departments to "send emails and text messages to [their] users". About time, too, you may say. What took them so long?

It's not quite like that.

It may have taken GDS until now to make a notification service "available to all of central government" but DVLA, for example, the driver and vehicle licensing agency, have been sending emails for more than 10 years now:
From: Vehicle Licensing Online [mailto:donotreply@vehiclelicence.gov.uk]
Sent: 19 April 2006 17:12
To: <DMossEsq>
Subject: Confirmation of Tax Disc Application

THIS IS AN AUTOMATED EMAIL - PLEASE DO NOT REPLY AS EMAILS
RECEIVED AT THIS ADDRESS CANNOT BE RESPONDED TO.

Confirmation of Tax Disc Application

Thank you for using DVLA Vehicle Licensing Online. Your application for a new
Tax Disc has been successful.

Reference Number: 1031 0163 9722 1190
Application made on: 19/04/2006 17:08:02
Tax Disc Period: 12 months
Tax Disc Duty: £175.00

The Tax Disc and receipt should arrive in the post within 5 working days.

Should your tax disc not arrive after 5 working days, then please phone us on 0870 850 4444 and choose option 4 then option 1 and be prepared to quote the Reference Number.
GDS tell us that "we expect to start offering Notify to local government by late 2017, once we’ve sorted out the pricing model". But even the dear old London Borough of Merton have been sending emails for at least the past four years:
From: Permitsnoreply@merton.gov.uk
Sent: 22 January 2013 13:05
To: <DMossEsq>
Subject: Payment Confirmation

This is an e-mail from London Borough of Merton.

Your payment has been processed successfully. The details of your payment are :

Payment Reference : 28040
Permit Number : RPP11937
Amount Paid : 65.00 pounds
Date Paid : 22-Jan-2013

This message has been generated automatically. Please do not reply.
Neither Merton nor DVLA are likely to share GDS's excitement about GOV.UK Notify.

Nor Companies House. Here's a notification they sent over 13 years ago:
From: web-filing@companies-house.gov.uk
Sent: 02 January 2004 10:41
To: <DMossEsq>
Subject: Companies House WebFiling Service

This message has been generated in response to your request for a Security Code for use on the Companies House WebFiling service.

Your Security Code is <security code>.

This code will be automatically linked to the e-mail address <DMossEsq>, and any company transactions received under this code will be confirmed to this address.

Additional security codes can be requested for alternative e-mail addresses.

Thank you for visiting the Companies House Website. Contact Centre tel: 0870 33 33 636 or e-mail: enquiries@companieshouse.gov.uk
GDS list 33 central government services currently testing GOV.UK Notify on their performance dashboard. Guess who's not on the list.

That's right.

Her Majesty's Customs and Excise Revenue and Customs (HMRC). The big one.

Just how big is made clear in an interview given to Derek du Preez, please see HMRC Digital Chief – ‘This transformation is the biggest in our history’: "Hardik Shah, Deputy Director, Chief Digital and Information Officer group, HMRC, ... explained that £536 billion of revenue is collected by HMRC every year and that this is the amount that flows through its IT systems ... HMRC processes more than 2 billion transactions every year and Shah said that 90% of those happen online already ...".

HMRC have had automated notification operating for years. Here they were last year for example telling DMossEsq that it's time to submit one of his VAT returns:
From: vatnotifications@eprompts.hmrc.gov.uk
Sent: 24 July 2016 02:30
To: <DMossEsq>
Subject: Reminder to file your VAT Return


Hello Subscriber

You need to submit a VAT return for the period 01.05.16 to 31.07.16 for <Company name>, VAT registration number <VAT no.>.

To submit the return go to the HMRC Services: Sign in or register page on GOV.UK to sign in.

Alternatively, if you use accounting software, in most cases you can use it to quickly prepare and submit your VAT return directly to HMRC.

You'll need to pay your VAT bill by the deadline shown on your VAT return. You may have to pay a surcharge if you don't pay on time.

For details of the due date for returns and payments go to the VAT Returns guide on GOV.UK.

The easiest way to avoid missing a payment deadline is to pay by Direct Debit.

Don't reply to this email as it's an automated reminder.


HM Revenue and Customs
HMRC send texts as well as emails, as noted in the Daily Telegraph article referred to above and in their guidance note on how to recognise phishing attacks. GDS will have to produce similar guidance for their users when GOV.UK Notify finally goes live. (The service is currently still in beta.)

HMRC don't need GOV.UK Notify. Or GOV.UK Pay – they're already used to collecting hundreds of billions of pounds p.a. Famously, they don't need GOV.UK Verify (RIP) either. That's three platform services for GDS's Government as a Platform strategy that HMRC aren't using (excluding a bit of grudging use of GOV.UK Verify (RIP)).

GDS are trying to get government departments to stick all their applications and all their data in the cloud. That's the strategy. There's a long way to go. But not for HMRC. They're already well on the way, as they told Mr du Preez:
When we started our transformation in 2015, we realised our IT infrastructure was not suitable. That’s when we started our virtualisation programme. Some 50% of our IT estate is already virtualised, and given the size of our estate, that’s not a small thing. And we did that in less than 2 years.

Almost 90% of our SAP estate is virtualised, in a private cloud. It wasn’t easy, technologies were developing, security isn’t easy, so we had to do a lot of work with our partners to get the right solution. But it’s now 90% virtualised. All of our SAP apps were virtualised in about 9 months.

We are now in the final stage of database virtualisation, and we only have three databases left. Hopefully by the end of the financial year we will be 100% virtualised on our SAP estate.
Who is leading whom here? You can notify whoever you like with your answer by email, text, tweet or letter, but from where we're sitting it looks as if GDS aren't so much devising the government's transformation strategy as trying breathlessly to keep up with HMRC.


Updated 13.4.18



The Government Digital Service's job is to transform government. Instead of doing that, they ruminate about process.

Katy Arnold, the head of user research at the UK Home Office, posted a tweet yesterday morning about storing and sharing the results of user research.

User research is one of the processes government transformers are meant to go through to achieve their objectives.

Lorna Wall is the user research lead for GOV.UK Verify (RIP), the inanimate pan-government identity assurance scheme still being promoted hopelessly and pointlessly by GDS.

Ms Wall commented (or ruminated) on Ms Arnold's tweet. Not once. But twice.

There have been about 150 rounds of user research into GOV.UK Verify (RIP) and it's a "challenge", she says, to store the results accessibly.

This research has been going on for nearly five years she says in her second tweet and, what with changes in personnel, it's hard to keep track of which research findings led to which design decisions. That, too, is a "challenge".

You'd think that the user research profession might have solved this problem by now. Apparently not.

At GDS, they continue to conduct user research into GOV.UK Verify (RIP), they've done it about 150 times, they've been doing it for nearly five years and they're still "struggling" to maintain the relevance of all this work. Meantime, GOV.UK Verify (RIP) has failed.

That was the real challenge – to make pan-government identity assurance work. They've failed. But work continues to be done on cataloguing their user research results.

Have you ever seen a clearer example of missing the point? Of continuing the process because the process must be continued even though it's not working?

What was GDS's objective?

To deliver an identity assurance scheme?

Or to maintain an accessible set of research results?

Neither has been achieved.

In this instance, GDS have lost the plot.

Let that be an example to others, who are supposed to be guided in their attempts to transform government by the syllabus taught at GDS's academy. 5 years. 150 iterations. No cigar.


Updated 17.4.18

According to the Autumn Budget 2017 (p.5) the UK government expects to receive payments of about £769 billion in 2018-19:


The Government Digital Service's payments platform, GOV.UK Pay, collected its first payments on 13 November 2016 – £170. During fiscal year 2017-18 it collected a total of £38,653,834.

That's 0.005% of the 2018-19 figure. At this rate 99.995% of all receipts will not involve GOV.UK Pay.

On 31 March 2016 GDS described GOV.UK Pay as a "greenfield project". They provided a link explaining that "the term greenfield project is used in many industries, including software development where it means to start a project without the need to consider any prior work". Two years later, the result of not considering any prior work is a system which collects 0.005% p.a. of the government's receipts.

How did GDS get into this ridiculous backwater?

Their March 2016 blog post says that "user research showed us how frustrating payment pages can be". Good old user research. GDS's favourite process. It doesn't seem to have helped GOV.UK Pay any more than it helped GOV.UK Verify (RIP), please see above.

The blog post says also "we’ve had the freedom to make good technical choices that address user needs". Good old user needs. GDS's lodestar. But they're not the only ones, Her Majesty's Revenue and Customs and others must be quite good at working out user needs, perhaps better than GDS are, given that 99.995% of receipts don't rely on GOV.UK Pay.

The natives are getting restless about claims to be uniquely guided by user needs, please see the tweet alongside.

"... we’ve built a consistent and reliable user experience hosted securely on GOV.UK", GDS say. Maybe. But 99.995% of the time that experience is irrelevant.

Nowhere in their March 2016 blog post do GDS say how much money will be saved by using GOV.UK Pay nor when the savings can be expected to start. That's no way to mount a business case.

But of course GDS aren't trying to mount a business case. They're trying, ineffectually as it turns out, to bring about a callow vision they have of government as a platform. It's ideological. An "intellectual pissing match", as Mike Bracken would say.

How much longer will GDS be allowed to ruminate? When will they be expected to deliver something?