POST I call APP Britain

xxx

In 2019, there were 122,437 APP fraud cases in the UK, with losses hitting £456 million, up from £354 million in 2018. Financial providers returned about a quarter of losses – £116 million – to victims.

From APP fraud losses hit £456 million in 2019:

xxx

 

xxx

RBS Group (including Royal Bank of Scotland, NatWest and Ulster Bank) and HSBC (including First Direct) were unable to confirm a specific date when asked if they would be ready by the regulator’s deadline. Metro Bank told Which? that it has no current plans to implement CoP at all.

From Which? calls for all banks to adopt anti-fraud measures | Banks and building societies | The Guardian:

 

xxx

CHYP I spy COV-19

There was a post on Twitter in the midst of the coronavirus COV-19 pandemic that caught my eye. It quoted an emergency room doctor in Los Angeles asking for help from the technology community, saying “we need a platform for frontline doctors to share information quickly and anonymously”. It went on to state the obvious requirement that “I need a platform where doctors can join, have their credentials validated and then ask questions of other frontline doctors”.

This is an interesting requirement that tell us something about the kind of digital identity that we should be building for the modern world instead of trying to find ways to copy passport data around the web. The requirement, to know what someone is without knowing who they are, is fundamental to the operation of a digital identity infrastructure in the kind of open democracy that we (ie, the West) espouse. The information sharing platform needs to know that the person answering a question has relevant qualifications and experience. Who that person is is not important.

Now, in the physical world this is an extremely difficult problem to solve. Suppose there was a meeting of frontline doctors to discuss different approaches and treatments but the doctors wanted to remain anonymous for whatever reason (for example, they may not want to compromise the identity of their patients). I suppose the doctors could all dress up as ghosts, cover themselves in bedsheet and enter the room by presenting their hospital identity cards (through a slit in the sheet) with their names covered up by by black pen. But then how would you know that the identity card belongs to the “doctor” presenting it? After all the picture on every identity card will be the same (someone dressed as a ghost) and you have no way of knowing whether it was their ID cards or whether they were agents of foreign powers, infiltrators hellbent on spreading false information to ensure the maximum number of deaths. The real-world problem of demonstrating that you have some particular credential or that you are the “owner” of a reputation without disclosing personal information is a very difficult problem indeed.

(It also illustrates the difficulty of trying to create large-scale identity infrastructure by using identification methods rather than authenticating to a digital identity infrastructure. Consider the example of James Bond, one of my favourite case studies. James Bond is masquerading as a COV-19 treatment physician in order to obtain the very latest knowledge on the topic. He walks up to the door of the hospital where the meeting is being held and puts his finger on the fingerprint scanner at the door… at which point the door loudly says “hello Mr Bond welcome back to the infectious diseases unit”. Oooops.)

In the virtual world this is quite a straightforward problem to solve. Let’s imagine I go to the doctors information sharing platform and attempt to login. The system will demand to see some form of credential proving that I am a doctor. So I take my digital hospital identity card out from my digital wallet (this is a thought experiment remember, none of the things actually exist yet) and send the relevant credential to the platform.

The credential is an attribute (in this case, IS_A_DOCTOR) together with an identifier for the holder (in this case, a public key) together with the digital signature of someone who can attest to the credential (in thsi case, the hospital the employs the doctor). Now, the information sharing platform can easily check the digital signature of the credential, because they have the public keys of all of the hospital, and can extract the relevant attribute.

But how do they know that this IS_A_DOCTOR attribute applies to me and that I haven’t copied it from somebody else’s mobile phone? That’s also easy to determine in the virtual world with the public key of the associated digital identity. The platform can simply encrypt some data (anything will do) using this public key and send it to me. Since the only person in the entire world who can decrypt this message is the person with the corresponding private key, which is in my mobile phone’s secure tamper resistant memory (eg, the SIM or the Secure Enclave or Secure Element), I must be the person associated with the attribute. The phone will not allow the private key to be used to decrypt this message without strong authentication (in this case, let’s say it’s a fingerprint or a facial biometric) so the whole process works smoothly and almost invisibly: the doctor runs the information sharing platform app, the app invisbly talks to the digital wallet app in order to get the credential, the digital wallet app asks for the fingerprint, the doctor puts his or her finger on the phone and away we go.

Now the platform knows that I am a doctor but does not have any personally identifiable information about me and has no idea who I am. It does however have the public key and since the hospital has signed a digital certificate that contains this public key, if I should subsequently turn out to be engaged in dangerous behaviour, giving out information that I know to be incorrect, or whatever else doctors can do to get themselves disbarred from being doctors, then a court order against the hospital will result in them disclosing who I am. I can’t do bad stuff.

This is a good example of how cryptography can deliver some amazing but counterintuitive solutions to serious real-world problems. I know from my personal experience, and the experiences of colleagues at Consult Hyperion, that it can sometimes be difficult to communicate just what can be done in the world of digital identity by using what you might call counterintuitive cryptography, but it’s what we will need to make a digital identity infrastructure that works for everybody in the future. And, crucially, all of the technology exists and is tried and tested so if you really want to solve problems like this one, we can help right away.

POST 3Ws and a virus

There was a post on Twitter in the midst of the coronavirus COV-19 pandemic that caught my eye. It quoted an emergency room doctor in Los Angeles asking for help from the technology community, saying “we need a platform for frontline doctors to share information quickly and anonymously”. It went on to state the obvious requirement that “I need a platform where doctors can join, have their credentials validated and then ask questions of other frontline doctors”.

This an interesting requirement that tells us something about the kind of digital identity that we should be building for the modern world instead of trying to find ways to copy passport data around the web. The requirement, to know what someone is without knowing who they are, is fundamental to the operation of a digital identity infrasturture in the kind of open democracy that we (ie, the West) espouse. The information sharing platform needs to know that the person answering a question has relevant qualifications and experience. Who that person is is not important.

Now, in the physical world this is an extremely difficult problem to solve. Suppose there was a meeting of frontline doctors to discuss different approaches and treatments but the doctors wanted to remain anonymous for whatever reason (for example, they may not want to compromise the identity of their patients). I suppose the doctors could all dress up as ghosts, cover themselves in bedsheet and enter the room by presenting their hospital identity cards (through a slit in the sheet) with their names covered up by by black pen. But then how would you know that the identity card belongs to the “doctor” presenting it? After all the picture on every identity card will be the same (someone dressed as a ghost) and you have no way of knowing whether it was their ID cards or whether they were agents of foreign powers, infiltrators hellbent on spreading false information to ensure the maximum number of deaths. The real-world problem of demonstrating that you have some particular credential or that you are the “owner” of a reputation without disclosing personal information is a very difficult problem indeed.

(It also illustrates the difficulty of trying to create large-scale identity infrastructure by using identification methods rather than authenticating to a digital identity infrastructure. Consider the example of James Bond, one of my favourite case studies. James Bond is masquerading as a COV-19 treatment physician in order to obtain the very latest knowledge on the topic. He walks up to the door of the hospital where the meeting is being held and puts his finger on the fingerprint scanner at the door… at which point the door loudly says “hello Mr Bond welcome back to the infectious diseases unit”. Oooops.)

In the virtual world this is quite a straightforward problem to solve. Let’s imagine I go to the doctors information sharing platform and attempt to login. The system will demand to see some form of credential proving that I am a doctor. So I take my digital hospital identity card out from my digital wallet (this is a thought experiment remember, none of the things actually exist yet) and send it to the platform.

In this world, the credential is an attribute (in this case, IS_A_DOCTOR) together with an identifier for the holder (in this case, a public key) together with the digital signature of someone who can attest to the credential (in thsi case, the hospital the employs the doctor). Now, the information sharing platform can easily check the digital signature of the credential, because they have the public keys of all of the hospital, and can extract the relevant attribute.

But how do they know that this IS_A_DOCTOR attribute applies to me and that I haven’t copied it from somebody else’s mobile phone? That’s also easy to determine in the virtual world with the public key of the associated digital identity. The platform can simply encrypt some data (anything will do) using this public key and send it to me. Since the only person in the entire world who can decrypt this message is the person with the corresponding private key, which is in my mobile phone’s secure tamper resistant memory (eg, the SIM or the Secure Enclave or Secure Element), I must be the person associated with the attribute. The phone will not allow the private key to be used to decrypt this message without strong authentication (in this case, let’s say it’s a fingerprint or a facial biometric) so the whole process works smoothly and almost invisbly: the doctor runs the information sharing platform app, the app invisbly talks to the digital wallet app in order to get the credential, the digital wallet app asks for the fingerprint, the doctor puts his or her finger on the phone and away we go.

Now the platform knows that I am a doctor but does not have any personally identifiable information about me and has no idea who I am. It does however have the public key and since the hospital has signed a digital certificate that contains this public key, if I should subsequently turn out to be engaged in dangerous behaviour, giving out information that I know to be incorrect, or whatever else doctors can do to get themselves disbarred from being doctors, then a court order against the hospital will result in them disclosing who I am. I can’t do bad stuff.

It is possible to make a much stronger form of this kind of conditional anonymity (that is, no you knows who you are, unless you do something against the law) by using cryptographic blinding to deliver unconditional anonymity. Here is another medical example to make the point.

Suppose I am a nurse and I want to go through some whistleblowing platform to alert the authorities to the fact that the anaesthesiologist that I’m working with is off his head on ketamine. Now, if there is any possibility of the anaesthesiologist’s lawyer ever finding out who I am then I might not want to remake the report at all. This would clearly not be in the public interest. So in this case, the whistleblowing case, we might want to provide unconditional anonymity in the interests of public safety.

Again it’s very hard to imagine how to do this in the physical world, but in the virtual world it is quite straightforward. I send my public key to the hospital to be digitally signed to prove that I’m a nurse. Before I send it to them I apply a cryptographic “blinding factor”. Blinding factors are a clever piece of mathematics (first used at scale by the pioneering David Chaum at DigiCash) that means that you can form digital signatures across data without being able to know what the data is

(So the hospital signs the public key multiplied by a cryptographic blinding factor and when I receive the signed public key back from them I divide out the cryptographic blinding factor. The digital signature remains valid. But now, not even the hospital knows my public key because they signed the blinded version of the key, not the key itself.)

This is another example of how cryptography can deliver some amazing but counterintuitive solutions to serious real-world problems. I know from my personal experience that it can sometimes be difficult to communicate just what can be done in the world of digital identity by using what you might call counterintuitive cryptography, but it’s what we will need to make a digital identity infrastructure that works for everybody in the future.

Patronscan wants cities to require bars to scan your ID with its service so it can maintain a secret, unaccountable blacklist / Boing Boing

xxx

Patronscan is the leading provider of ID-scanning/verification services to bars and restaurants, and one of its selling points is that it allows its customers to create shared blacklists of undesirable customers who can then be denied services at every other establishment that uses its services.

From Patronscan wants cities to require bars to scan your ID with its service so it can maintain a secret, unaccountable blacklist / Boing Boing:

This is, in essence, much the same as China’s social scoring except that it is operated by unaccountable private companies rather than by the government.

Nike and Macy’s tinker with blockchain – Decrypt

xxx

“It builds on a prior RFID Labs’ initiative, Project Zipper, which studied RFID in retail supply chains, finding that retailers, brand owners and logistics providers all share data in different formats.”

From “Nike and Macy’s tinker with blockchain – Decrypt”.

xxx

xxx

“Through adopting blockchain technology, the CHIP initiative enables partners to use a common language for better inventory visibility and data analysis.”

From “Nike and Macy’s tinker with blockchain – Decrypt”.

 

xxx

Monzo boss warns Open Banking reforms have ‘zero benefit’

xxx

The UK’s efforts to implement Open Banking have had zero positive impact on innovation in the banking sector, Monzo founder Tom Blomfield has warned.

Mr Blomfield cautioned that the flagship regulation, which was supposed to crack open the software of big banks and make it easier for consumers to switch services, has failed.

“The positive effect of Open Banking on innovation has been nil,” Mr Blomfield said. “I don’t see any businesses based on Open Banking in Europe whatsoever.”

From Monzo boss warns Open Banking reforms have ‘zero benefit’:

xxx

Is a universal digital Driving Licence around the corner?

xxx

ISO/IEC 18013 establishes guidelines for the design format and data content of an ISO-compliant driving licence (IDL) with regard to human-readable features (ISO/IEC 18013-1), ISO machine-readable technologies (ISO/IEC 18013-2), access control, authentication and integrity validation (ISO/IEC 18013-3), and associated test methods (ISO/IEC 18013-4). It creates a common basis for general use and mutual recognition of the IDL without impeding individual countries/states in applying their privacy rules and national/community/regional motor vehicle authorities in taking care of their specific needs.

From Is a universal digital Driving Licence around the corner?:

xxx

(2) Innovation in the payment sector: Bitcoin, Libra & Co at the mpe 2020 | LinkedIn

The organisers of Merchant Payments Ecosystem in Berlin this year were kind enough to invite me to deliver the keynote. Frank Meier is kind to say that “the Innovation Director at Consult Hyperion is largely responsible for the organisation and implementation of the MPE and is internationally regarded as one of the leading experts on digital money and digital identity“. 

Well! I’m flattered to be described this way, but the truth is that while I do provide input to Filip and his amazing team, I cannot take the credit for the organisation and implementation of MPE. I hope I can take some credit for framing the issues and setting the right tone for the event (Frank says “in his usual light-hearted manner, the Briton laid the cornerstone for a three-day conference marathon”) which was, as it always has been, excellent.

POST Mobile driving licence (mDL)

When I was in New York a couple of months ago I had to visit a couple of different buildings for various meetings. At the first building, I was asked for identification. As I am English and not North Korean, I don’t carry identification papers with me when I walk down the street and my British passport and British driving licence (neither of which the security guard could have verified even if I had shown them to him) were locked up securely back in the hotel safe. I presented my standard US identification document. This an old building pass from the previous Consult Hyperion office in midtown. It expired a couple of years ago, but it has my picture on it and it says “David Birch”. It was accepted without question and I was allowed in.

When I went into a second building on that same day, I was asked to scan my driver’s license! They had a scanner on the counter to read the barcode on the back of US driver’s licenses. Obviously I don’t have a US driver’s license, so I showed them my expired building pass again, I was given entry to the building.

If I did have the US driver’s license, then there’s no way I would have let them scan it.

Apart from the obvious fact that my ability to drive is unrelated to whether I have been invited to a meeting or not, nothing that is on my driving licence (except perhaps my name, which had already told the guy on the desk) is any of their business and by handing over my personal information to yet another random database held by yet another random company, I was vastly increasing the chance of my licence data and my personal details being being stolen.

It’s amazing how the driving licence has become an identity document and how machine-readable driving licences have become a vector for collecting personal information. One of my favourite stories about this relates to an experiment done in Washington state, in which researchers hooked up the driving licence scanner to a display over the door. As patrons entered the bar, their personal data was displayed above them for all to see! I imagine having your name, date of birth, address, height and weight displayed the moment you enter any establishment.

Why is this still going on? We live in a world of laser beams and robots on Mars, a world of digital signatures and blockchains. Why are we displaying data to people who don’t need it (or deserve it) instead of 

The first steps are already being taken. Consider this example taken from the IEEE Spectrum magazine: “A young woman sits at a bar on Bourbon Street in New Orleans and orders a beer. The bartender asks for identification. The bar patron pulls out her phone, clicks on an app, and displays a digital version of her driver’s license showing she is over 21. In response, the bartender pulls out her own phone, clicks on the same app, uses it to scan the woman’s digital license, and verifies that her information is legit”.

(I was beyond excited to discover than Louisiana is implementing a version of the “psychic ID” that I set out back in 2005!. [Here’s a paper about it from 2009.])

All of which explains why I am very interested in machine-readable driving licences (mDLs) and how we might use them to deliver population-scale identity. The ISO standard for mDLs is ISO 18013. It creates a common basis for general use and mutual recognition of the IDL without impeding individual countries/states in applying their privacy rules and national/community/regional motor vehicle authorities in taking care of their specific needs. and it is five parts as follows:

  1. Guidelines for the design format and data content of an ISO-compliant driving licence (IDL) with regard to human-readable features.

  2. Machine-readable technologies.

  3. Access control, authentication and integrity validation.

  4. Associated test methods.

  5. Global interoperability.

So, ISO 18013-5 is the new global interoperability standard. Could digital driving licenses evolve into one form of global identity? Actually, I think the answer to this is yes, because ISO 18013-5 includes provisions for extensions to the data model to permit specific “regional” additions to the standard data (e.g., REAL ID across just the USA).

Iso 18013 5

The American Association of Motor Vehicle Administrators (AAMVA) published a useful white paper on “Mobile Drivers’ License Functional Needs” a couple of years ago.

xxx

AAMVA Director of Identity Management Geoff Slagle said he does not believe there will be wide scale adoption of the digital licenses by either states or citizens anytime soon because:

·    No standards are currently in place for the actual DDL and how it will be used on the smartphone.

·    Equipment capability for law enforcement to use during traffic stops needs to be standardized.

·    Consumer apprehension over technology and privacy concerns will continue.

From Is a Digital Driver’s License in your Future?: NMA Weekly E-Newsletter #476 – National Motorists Association.

 

xxx

Design a site like this with WordPress.com
Get started