Phil Leggetter - Dec 2020

Phil Leggetter

Developer Experience

As a developer-first and API-first company, we prioritise tools that will make you, the developer, successful. Today we're excited to announce the tru.ID CLI: built on top of our public APIs, open sourced, and your go-to developer tool when building on the **tru.ID** platform.

## Why a CLI?

Many of us spend a lot of time in the terminal, so a CLI enables you to work from where you already are. IDEs such as Visual Studio Code and Android Studio come with in-built terminals. But having a CLI also allows us to build integrations into existing development workflows, via scripts, outside of the IDE. For example, [Xcode behaviours](https://developer.apple.com/library/archive/documentation/ToolsLanguages/Conceptual/Xcode_Overview/CustomizingYourWorkflow.html) or integration into CI/CD workflows.

## Using Oclif & Open Source

The [tru.ID](http://tru.ID) CLI is built upon the excellent [oclif open CLI framework](https://oclif.io/) by Heroku. Oclif provides a foundation for CLI functionality such as subcommands, command arguments and flags, plugin support and lots of utilities that enable us to focus on features instead of building our own CLI framework.

If you'd like to see how we've used Oclif the [**tru.ID** CLI](https://github.com/tru-ID/tru-cli) is on GitHub. Within the GitHub repo you'll find two branches:

- `main` for the latest stable release
- `canary` if you'd like to try out the latest features

We'd love to hear what you think so please ask questions, share ideas and raise PRs on the [tru-ID/cli repo](https://github.com/tru-ID/tru-cli/issues).

## Install and Setup the **tru.ID** CLI

For the moment the only installation option is via NPM so you'll need Node.js installed.

With Node.js installed you install the **tru.ID** CLI as follows:

```bash
$ npm install -g @tru_id/cli
```

Or, if you prefer [Yarn](https://yarnpkg.com/):

```bash
$ yarn global add @tru_id/cli
```

To try out the latest features use `@tru_id/cli@canary`.

With the `tru` command installed, setup the CLI with the credentials you'll find within the [**tru.ID** console](https://tru.id/console).

```bash
$ tru setup:credentials {client_id} {client_secret} eu
```

`eu` is the region where your account data is stored and, at the time of this blog post, is the only region we have available (more coming soon).

You can now query the credit you have available using:

```bash
$ tru workspaces
```

And the output will be similar to:

```bash
credentials.client_id                data_residency balance.amount_available balance.currency created_at
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx EU             28                       API              2020-08-12T12:46:56+0000
```

## Creating a **tru.ID** Project

Projects are configuration containers within the **tru.ID** platform and you'll normally have a one-to-one mapping of a tru.ID project to an application that you are developing (though you may also create a project per environment: `dev`, `staging` and `prod`). A key piece of configuration are the project `credentials` which contain a `client_id` and `client_secret` that you use to authenticate interactions with the tru.ID APIs.

You create projects using the CLI:

```bash
$ tru projects:create "My Awesome Project"
```

And you'll see output such as:

```bash
Creating Project "My Awesome Project"
Project configuration saved to "~/my_awesome_project/tru.json".
```

The `tru.json` file contains your project configuration including the project credentials. Don't check this into source control!

With a project created you can `cd my_awesome_project` so the CLI can read the `tru.json` file from the `cwd` and you have everything you need to fully utilise the **tru.ID** CLI.

## Trying the tru.ID APIs

CLIs normally focus on platform management functionality, such as creating and managing projects, but we decided to also add commands to let you try out our products from the terminal. Of course, you can also try these out programmatically too.

### SIMCheck

[SIMCheck](https://tru.id/docs/sim-check) is an API that queries when the SIM card associated with a phone number last changed:

```bash
$ tru simchecks:create
```

With the output being similar to the following, which prompts for the phone number to be checked:

```bash
? Please enter the phone number you would like to SIMCheck +{phone_number}
Creating SIMCheck for +{phone_number}

	status: COMPLETED
	no_sim_change: true
	last_sim_change_at: 2017-01-26T07:16:57+0000
```

The `no_sim_change` value indicates that the SIM card hasn't changed within the last seven (7) days, and `last_sim_change_at` specifies the last change date (when I changed my mobile phone provider from giffgaff UK to EE UK).

### PhoneCheck

PhoneCheck verifies that a phone number is associated with a SIM card within the mobile device. This is achieved via tru.ID's integration with MNOs (Mobile Network Operators) around the world. For a more in-depth look at how this works, check out the [PhoneCheck integration guide](https://tru.id/docs/phone-check/integration). Of course, you can also try this out via our CLI:

```bash
$ tru phonechecks:create --workflow
```

The output of this command prompts for a phone number and also displays a QR code to scan on a mobile device. It also provides instructions to disable WiFi on the device, as part of the PhoneCheck workflow is to make a web request over the device's mobile data connection.

```bash
? Please enter the phone number you would like to PhoneCheck +{phone_number}
Creating PhoneCheck for +{phone_number}
PhoneCheck ACCEPTED
check_id: 76a36abb-8495-403a-9f71-531c80c6a26b
check_url: https://eu.api.tru.id/phone_check/v0.1/checks/76a36abb-8495-403a-9f71-531c80c6a26b/redirect
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ █▄█  ██ ▄███ ▀▄▄ ▄▀█ ██ ▄  ▀██▀█▀▀  █  ▄ ██ ▄▄▄▄▄ █
█ █   █ █ ▄▀▄ █▄█▄█▀█████ ▄█ ██▄▄▄▄█▀▀█▀ █ ▀█▄▀▄ ██ █   █ █
█ █▄▄▄█ █▄ █▀  ▀▀▀   ▀▀  ▀█ ▄▄▄   ▄█▄▄   ▀ ▀▄▄▄▀▄██ █▄▄▄█ █
█▄▄▄▄▄▄▄█▄▀▄█▄█▄█▄█▄▀▄█▄█ ▀ █▄█ █▄█ ▀▄▀ ▀ ▀ ▀▄█ ▀▄█▄▄▄▄▄▄▄█
█    ▀▀▄▀▄▄▀▄▀▀█▄▄ ▀▄▄  ▀ ▄ ▄▄▄  ███ █▀██ ▀▀ ▀▀▄▄  ██ ▄▄▀▄█
███▀▄▀▄▄█▄ ▀   ▀██ ██▄▄▄▀ ▄▄██▀ █▄ ▀ ▀▀▄ ▄ ▀█ ▄  ▄████ █  █
█▀▄█ ▀▀▄█▀ ▄█▄▄ █▄█▄  █▄▄██ █▀▄▄ ▀ ▄▀▄   ▀▄▄▀▀ ▄▄█▄▀▄▀ █▄▄█
█▄██ ▄ ▄▄ ▄▀▀▀▀█ ▄▀██▄▄▀▀ ▄▄▄█ ▄▄ ██▄█ █▀ █ █ ▄█▀▀ ▄▀▀▀ █▀█
█▄▀▀▄██▄█▄▄▄  ▄▄▄ █▀██▄█ ▄ █▄█ ▄▄▄▄ ▀█▀▄▀▀▄▄▄▄▄  ▄ █ █▄██ █
█ ▀ ▄ ▀▄▄▀  █▄▀▀ ▄  ██▀█▀▄▀ ▄█ ▀██▀▄█▀▄ █▀▀█▀█▀  ▀▀▄▀▀▀█▀▀█
███ ▄▀ ▄ ▀  ▀▀ ██ ▄███  ▀ ▄▀▄ █▀██▄▄▀▀███ ▄ ▀▀ ▄▀ █▄█▄▀ █▀█
█▀▄ ▀██▄▀ █ ▀█ ▄▀▄ █ ▄  ▀███▄▄█▄█▄▄▄█▀▄▀█▀▀ ▄█  █▄▀▀█▄██▄ █
█▀▄██ ▄▄ ▄ █ ▀ ▄█▄   ▀█▀█▄ ▀█▀▀█▄▀ █▄▄ ▀███▄▄█ ██▄  ▀█▄█▄▄█
██▄▀  ▄▄▄ ▀▀ ▀█▀▀ ▄▄▄▀█▄█ ▄ ▄▄▄   █▄▀██▄▀▀█▄▄▀▄▄▀ ▄▄▄ ▀▀▀▀█
█ ▀ ▄ █▄█ ▀█▀ ▄▀▀ █▄██▀▀ █▀ █▄█ ▄▄ ▀█▀ ▄▄▀ ██▄▄▀▄ █▄█ ▀▄▀ █
██▀▀█ ▄▄  ██▄▄█▄ ▄█▀ ▀█ ▀█▄  ▄▄  ▄█▄▄ █  ▀▄▀██ ▄▄  ▄ ▄██ ▀█
█ ▄██ ▄▄ ███▀█▄█▄███ ▄    █▄▀█ █ ▀ ▄▀▀▄██▄▄▀█▀██▀█▀▄ █▀▄▄▀█
██▄   ▀▄█▀▄ ▄▀██▀  ▀ █▄▀ ▄▄█ ▀███ █ █  █▀▄█▄▄ █▄█▀█ ▄ ███▄█
█▄██▀ █▄█▄▄█ ▄█▀███ ▀██▀█▄█▄ ▄ ▄ ▀ █▀ █ ██▄▄█▀▀█▀▀▄▄▀█ ▀▀██
█▀▄█▄▄▄▄▄█  █ ██ ▄▀▄  ▄▀▀ ▀ ▄▄ █ ▀█▀ ▀█ █▄▀ ▀▀██▀ █▀▄█ ▀█▄█
█▀▄█ █▄▄▀ █▀▀ █▀  ▀▀██▄▀█▄▀▄▀▀▄██▄▀▀████ ▀ ██▄ ▀▄█▄▀▄ ▀██▄█
██  ▀▀▄▄▀ ▄ ▄██▄▀▀█▄▀ █ ▄▄▄     ▄█ ▄  ▀   █▄ ▄ ▀██ █ ██▄▄▀█
█▀▄▀▄█▀▄ ▀▀ █ ▄▀ █▀▀ ▄ █▄ ▄  █▀█▀▀ ▄████▀▄▀▀ ▀███▄ ▀██▄ ▄ █
█ ▀ ▀▀▄▄▄ ██▀▄▀   ▀█▀█ ▀▀█  ▄ ███▀▀▄▄▀ █▀▄█ ▄ █  █▀ ██▀▄  █
███████▄█▀▀▄ ▀▄█ ██ ▀ ▀██▄▀ ▄▄▄ ▀▀███▄  ▄█▀▄▀███▀ ▄▄▄ ▀▀ ██
█ ▄▄▄▄▄ ██ █ █▄█▀█  ▀ ███ ▄ █▄█ █▀▄▀█▀ ▄▄ ▄ ▄▀▄█▄ █▄█ █▀▄▀█
█ █   █ █▀ █▀▄ █▀█ ▀ ▄ █▀▄▀  ▄▄   ▀▀█▀██▄▀█▄▄▄█   ▄▄ ▄▀▄ ██
█ █▄▄▄█ █ █▄▄▄▀▀  ▄▄▄▀▄ ▀ ▀▀█▀██ ▄  ▀ █ ██▄██▄▀▄▀ █▀███▄█▀█
█▄▄▄▄▄▄▄█▄▄▄▄▄▄▄█▄▄██▄▄▄█████▄▄███▄▄▄██▄▄▄▄▄██▄▄▄██▄█▄▄▄███

Please ensure the mobile phone with the phone number +{phone_number} is disconnected from WiFi and is using your mobile data connection.

Then scan the QR code and navigate to the check_url.

Waiting for a PhoneCheck result... done

PhoneCheck Workflow result:
	status:  COMPLETED
	match:  true ✅
```

QR codes in the terminal. Pretty cool, huh!

As well as creating resources you can also query existing ones:

```bash
$ tru phonechecks:list 76a36abb-8495-403a-9f71-531c80c6a26b
check_id                             created_at               status    match charge_currency charge_amount
76a36abb-8495-403a-9f71-531c80c6a26b 2021-02-23T21:08:56+0000 COMPLETED true  API
```

You can also try out `tru phonechecks:list` with flags such as `--search` to add query conditions the API request, `--filter` to filter a result from the API, and `--output` to change the output format e.g. `--output json`.

### SubscriberCheck

The CLI also supports [SubscriberCheck](https://tru.id/docs/subscriber-check), which runs a PhoneCheck but also includes a SIMCheck within the result. We'll leave trying that out to you, but here's the creation command that runs through the QR code workflow:

```bash
$ tru subscriberchecks:create --workflow
```

## What Else Can the CLI Do?

Two other commands worth highlighting are `oauth2` and `coverage`.

### OAuth2

Our APIs use OAuth2 credentials and access tokens for authentication. But we know that sometimes you just want access to an access token without having to concatenate a project `client_id` and `client_secret`, Base 64 encode that value, make a request to the [`/token` endpoint](https://tru.id/docs/reference/api#operation/oauth2-token) to create an access token, and then eventually getting to use it. So, the `oauth2` command makes it a bit easier to create an access token when you're just trying things out.

Note: Running the following command from a directory that contains a `tru.json` project configuration file will use the credentials for the project. If you run the command without a `tru.json` in the `cwd` you'll use the credentials you supplied in the `tru setup:credentials` command.

```bash
$ tru oauth2:token
```

Then you just need to copy the access token and use it:

```bash
access_token
GXuXq1DKa2LdBikD0jC8DenJgJTdgPSONLC0TpYqIzQ.ko9hRxKojOYhSvWkUBsPtHNPSUtB5KMwCqw8_FjUW6c
```

You can also assign the output to a variable and use it either in a mobile client or to try things out via cURL:

```bash
$ TOKEN=$(tru oauth2:token --no-header)
$ curl -s -X GET \
-H "Authorization: Bearer $TOKEN" \
https://eu.api.tru.id/phone_check/v0.1/checks/76a36abb-8495-403a-9f71-531c80c6a26b
{"check_id":"76a36abb-8495-403a-9f71-531c80c6a26b","status":"COMPLETED","match":true,"charge_amount":1.00,"charge_currency":"API","created_at":"2021-02-23T21:08:56+0000","updated_at":"2021-02-23T21:09:26+0000","_links":{"self":{"href":"https://eu.api.tru.id/phone_check/v0.1/checks/76a36abb-8495-403a-9f71-531c80c6a26b"}}}%
```

### Coverage

[Coverage](https://tru.id/docs/reference/api#tag/coverage) provides two endpoints and is thus a ["topic"](https://oclif.io/docs/topics) with two commands in the CLI.

`coverage:country {country_code}` allows you to query if the **tru.ID** platform has coverage for a given country. You can use either a phone number [country code prefix](https://en.wikipedia.org/wiki/List_of_country_calling_codes):

```bash
$ tru coverage:country +44
product_name     network_id network_name currency amount
Phone Check      23410      O2 UK        API      1
Phone Check      23415      Vodafone UK  API      1
Phone Check      23420      3 UK         API      1
Phone Check      23430      EE UK        API      1
Sim Check        23410      O2 UK        API      1
Sim Check        23415      Vodafone UK  API      1
Sim Check        23420      3 UK         API      1
Sim Check        23430      EE UK        API      1
Subscriber Check 23410      O2 UK        API      1
Subscriber Check 23415      Vodafone UK  API      1
Subscriber Check 23420      3 UK         API      1
Subscriber Check 23430      EE UK        API      1
```

Or a [two-letter alpha country code](https://www.iban.com/country-codes):

```bash
$ tru coverage:country CA
product_name network_id network_name currency amount
Phone Check  302220     Telus        API      1
Phone Check  302610     Bell         API      1
Phone Check  302720     Rogers       API      1
```

`coverage:reach` also performs a **tru.ID** platform coverage query but based on the IP address (IPv4 or IPv6) of the device:

```bash
$ tru coverage:reach 213.205.197.123
network_id network_name country_code supported_products
23430      EE UK        GB           Phone Check,Sim Check,Subscriber Check
```

## Try out the CLI and let us know what you think

In this post we've covered a number of the main commands but there's more that the CLI offers. Either install the **tru.ID** CLI (`npm install -g @tru_id/cli`) and `tru --help` to find out more, or take a look at the [CLI Reference docs](https://tru.id/docs/reference/cli) to see what else is possible.

We believe the **tru.ID** CLI offers a good first developer experience of our platform. But we'd love to know what you think via <a href="mailto:feedback@tru.id?subject=CLI Feedback">feedback@tru.id</a>.

If you haven't already, [signup for a **tru.ID** account](https://tru.id/signup), [follow @_tru_id on Twitter](https://twitter.com/_tru_id) and join our mission to reimagine mobile authentication.

As a developer-first and API-first company, we prioritise tools that will make you, the developer, successful. Today we're excited to announce the tru.ID CLI: built on top of our public APIs, open sourced, and your go-to developer tool when building on the **tru.ID** platform.

tru.ID CLI

Today I'd like to introduce you to the tru.ID CLI, built on top of our public APIs, open sourced, and your go-to when developing on the tru.ID platform

Announcing the tru.ID CLI

Parth

Parth Awasthi

Head of Product

__From impersonating a top executive to opening money-laundering bank accounts, deepfake fraud is becoming a growing problem and poses real challenges to businesses.__

‘Deepfakes’ – realistic video or audio manipulations that appear to show real people – have gone from sci-fi to reality and soared in popularity over the past year, with some created simply as jokes and others to spread malicious misinformation. The deepfakes that make headlines are typically those depicting celebrities and politicians, but they also pose real threats to businesses as well as individuals when used for fraudulent purposes – such as major theft, loss of revenue, and damage to your brand.

__Emma Woollacott__ (writer for Forbes, Private Eye, and the BBC), provides detailed insight into the problems resulting from this emerging technology in this extract from the Times [Digital Identity Report 2021…](https://www.raconteur.net/report/digital-identity-2021/ "Digital Identity Report 2021")

## The deepfake threat to businesses
The use of deepfake video and audio technologies could become a major cyberthreat to businesses within the next couple of years, cyber-risk analytics firm CyberCube warns in a recent report.

'Imagine a scenario in which a video of Elon Musk giving insider trading tips goes 	viral, only it’s not the real Elon Musk. Or a politician announces a new policy in a video clip, but once again it’s not real,' says Darren Thomson, head of cybersecurity strategy at CyberCube. 

'We’ve already seen these deepfake videos used in political campaigns; it’s only a matter of time before criminals apply the same technique to businesses and wealthy private individuals. It could be as simple as a faked voicemail from a senior manager instructing staff to make a fraudulent payment or move funds to an account set up by a hacker.'

In fact, such attacks are already starting to occur. In one high-profile example in 2019, fraudsters used voice-generating artificial intelligence software to fake a call from the chief executive of a German firm to his opposite number at a UK subsidiary. Fooled, the UK chief executive duly authorised a payment of $243,000 to the scammers. 

'What we're seeing is these kinds of attacks being used more and more. They're not overly sophisticated, but the amount of money they're trying to swindle is quite high,' says Bharat Mistry, technical director, UK and Ireland, at Trend Micro.

'I was with a customer in the UK and he was telling me he'd received a voicemail, and it was the chief information officer asking him to do something. Yet he knew the CIO of the organisation was on holiday and would never have phoned. There was no distinguishing factor, so you can see how clever it is.'

Attacks such as this follow the same pattern as traditional business email compromise scams, but with vastly more sophistication. 

'We've seen all these cloud technologies, things like analytics, machine-learning and artificial intelligence, and deepfakes are just an extension of that technology, using the tech in an abusive manner,' says Mistry.

![fraudulent fake accounts](//images.ctfassets.net/tqs8s7awhsf8/7nOIybQKsgq4mLtPSPKfVj/9d1739145f597dee81c0619a82e29409/tierra-mallorca-rgJ1J8SDEAY-unsplash.jpg)

## Creating fraudulent accounts
Another emerging type of deepfake fraud is the fraudulent creation of accounts, whether they are bank accounts, foreign exchange dealing accounts or share dealing accounts. These can be used by organised crime for the purposes of money laundering. And with the advent of the coronavirus pandemic, what was previously a gradual shift to remote account creation has now been massively accelerated, along with the potential for fraud.

Setting up an account remotely generally involves a two-step process: first, providing a scan of an identity document and then presenting a selfie. The selfie is often generated by asking the applicant to record a video in which they recite words or numbers, or perhaps through a short video interview with an agent. 

'It's obviously been a good way of protecting against fraud up until now, but now the fraudsters can deepfake themselves to look like the innocent victim,' says Bud. 

'They may have stolen or copied the documents of an innocent victim from some source, and then all they need to do is deepfake the victim's face onto their face and conduct the	interview with the agent, and the agent will be never the wiser.'

In a report late last year, identity verification firm Jumio found selfie-based fraud rates were five times higher than ID-based fraud and particularly prevalent where users are able to upload their own ID images. This means fraudsters can manipulate a legitimate ID or use an image of an ID found on the dark web or from a Google Images search.

Financial institutions are awakening to the risk. In a survey for iProov, three quarters of cybersecurity experts in the financial sector said they were concerned about deepfake fraud and nearly two-thirds said they expected the threat to get worse.

'Banks like ING, Rabobank in the Netherlands, Standard Bank in South Africa and the government of Singapore, which is supplying the financial services industry, these are all aware of the threat of deepfakes and are taking proactive measures,' says Bud.

However, only 28 per cent of survey respondents said they’d put plans in place to protect against deepfakes, with 41 per cent planning to do so in the next two years. With another poll of banking customers revealing most were unconcerned about deepfake fraud, introducing extra security measures can be problematic.

'There's a big difference between how much cybersecurity experts think people care and how much they do care, and that turns into a problem as soon as they try to implement 	intrusive measures,' says Bud.

'There is a risk that if they protect against deepfakes in ways that impact the customer experience, it will be immediately resisted.'

## Reliable protection without friction: tru.ID
Avoid deepfake threats by using a reliable, possession-based authentication solution that’s invisible to users. tru.ID can help you to implement mobile verification based on the SIM card, which can’t be duplicated or faked. 

Our range of API-based products enable you to quickly and easily implement deterministic, secure, frictionless mobile user authentication, reducing fraud and helping you to increase mobile revenues.

<HelloWorldDeviceVideo />

[Instant PhoneCheck](/../products/phone-check "Instant PhoneCheck") provides instant authentication of the mobile number of the connected mobile device, greatly improving the user experience and reducing drop-off rates.

[Strong SubscriberCheck](/../products/subscriber-check "Strong SubscriberCheck") provides real-time verification of the mobile number and SIM card identity, providing a high-security, low-friction mobile authentication solution that also eliminates the risk of SIM Swap fraud.

Or, if you really, really want to stick with SMS OTP, and so need an easy add-on security solution, we offer:

[Active SIMCheck](/../products/sim-check "Active SIMCheck"), which allows you to check that there has not been a SIM swap before you send the SMS OTP to the user. (Of course, there are still [all the other risks related to SMS OTP](/../why-tru/sms "Why tru.ID"), but this is a big improvement and a short-term fix while you plan the full solution.)

## Try us, follow us, join us

- To see our products in action, <CtaTrigger type="SCHEDULE_DEMO">schedule a demo now</CtaTrigger> or <CtaTrigger type="REQUEST_ACCESS">sign up</CtaTrigger> to start testing and integrating our APIs
- Follow us on [LinkedIn](https://www.linkedin.com/company/tru-id-hq) and [Twitter](https://twitter.com/_tru_id)
- Want to [join the team](../../careers)? We’d love to hear from you.

From impersonating a top executive to opening money-laundering bank accounts, deepfake fraud is becoming a growing problem and poses real challenges to businesses.


deepfake challenge

Deepfake identity fraud poses major cybersecurity challenges. Learn how criminals use this technology, and how your business can prevent it. 

Deepfaking it: the new cybersecurity frontier

Paul M

Paul McGuire

Co-founder, CEO at tru.ID

__The future of digital identity looks mobile. A new in-depth report, published this week in The Times, explores the issues with a range of industry experts...__

[tru.ID](/../ "tru.ID - APIs for mobile authentication") is proud to sponsor the [Digital Identity Report](https://www.raconteur.net/report/digital-identity-2021/ "Digital Identity Report"), published this week in The Times, which features all you need to know about digital identity in a mobile-first age. 

Here are just a few of the key takeaways:

- The UK is in urgent need of a form of universal digital identity, but making this suitable for every citizen poses significant challenges

- [Passwordless](/../use-cases/passwordless-onboarding "Passwordless onboarding for every user") login is transitioning from a concept to the stage of early adoption, as increasing numbers of cyberattacks expose the weakness of password-based security 

- As biometric solutions grow, they need to consider disabled accessibility – and the growing problem of deepfakes 

- Data leaks mean trust in technology is at an all-time low: when it comes to identification, businesses should consider linking to tech that users already [trust, like their mobile phone](/../why-tru/tru-identity-paradigm "The tru IDentity Paradigm")

The report features over 25 pages of in-depth commentary, graphics and statistics from across the digital ID space. [Download the Digital Identity Report free here](https://www.raconteur.net/report/digital-identity-2021/ "Digital Identity Report").

## Try us, follow us, join us

- If you’d like to see our products in action, <CtaTrigger type="SCHEDULE_DEMO">schedule a demo now</CtaTrigger> or <CtaTrigger type="REQUEST_ACCESS">sign up</CtaTrigger> to start testing and integrating our APIs
- If you’re interested in finding out more, follow us on [LinkedIn](https://www.linkedin.com/company/tru-id-hq) and [Twitter](https://twitter.com/_tru_id)
- And if you’d like to [join the team](../../careers), we’d love to hear from you.

The future of digital identity looks mobile. A new in-depth report, published this week in The Times, explores the issues with a range of industry experts...

The Times Report - Digital Identity 2021

tru.ID in the Digital Identity Report 2021. A new in-depth report, published this week in The Times, explores the issues with a range of industry experts

The Times Special Report - Digital Identity 2021

Try us, follow us, join us