{"id":1391,"date":"2023-12-13T01:31:06","date_gmt":"2023-12-13T01:31:06","guid":{"rendered":"https:\/\/260web.com\/news\/mod-fined-after-email-blunder-risked-afghan-interpreters-lives\/"},"modified":"2023-12-13T01:31:06","modified_gmt":"2023-12-13T01:31:06","slug":"mod-fined-after-email-blunder-risked-afghan-interpreters-lives","status":"publish","type":"post","link":"https:\/\/260web.com\/news\/mod-fined-after-email-blunder-risked-afghan-interpreters-lives\/","title":{"rendered":"MoD fined after email blunder risked Afghan interpreters’ lives"},"content":{"rendered":"

MoD fined after email blunder risked Afghan interpreters’ lives<\/p>\n

\n
\n
\"A<\/picture><\/span><\/div>\n<\/figure>\n<\/div>\n
\n
\n
\n
\n
By Liv McMahon & Chris Vallance<\/div>\n
Technology reporters<\/div>\n<\/div>\n<\/div>\n<\/div>\n
<\/div>\n<\/div>\n
\n
\n

The Ministry of Defence (MoD) has been fined \u00a3350,000 over an email blunder that exposed details of interpreters fleeing Afghanistan.<\/b><\/p>\n<\/div>\n<\/div>\n

\n
\n

The 265 people affected had worked with the UK government – some were in hiding when the Taliban seized control.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Lives could have been at risk had data fallen into their hands, the data watchdog said.<\/p>\n<\/div>\n<\/div>\n

\n
\n

The MoD said it recognised the severity of the breach, fully acknowledged the ruling and apologised to the victims.<\/p>\n<\/div>\n<\/div>\n

\n
\n

The information commissioner, John Edwards said the error “let down those to whom our country owes so much”.<\/p>\n<\/div>\n<\/div>\n

\n
\n

He added: “This was a particularly egregious breach of the obligation of security owed to these people, thus warranting the financial penalty my office imposes today,” he added.<\/p>\n<\/div>\n<\/div>\n

\n

Reply all<\/span><\/h2>\n<\/div>\n
\n
\n

The main breach was first revealed by the BBC in September 2021. It occurred when the Afghan relocations and assistance policy team (Arap) sent a mass email to 245 people who had worked with the UK government, who were eligible for evacuation. Most, but not all as interpreters, <\/p>\n<\/div>\n<\/div>\n

\n
\n

In the message, their addresses were put in the “to” field rather than the intended blind carbon copy (Bcc) field – meaning email addresses were visible to all recipients.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Further information about those trying to leave Afghanistan, including one person’s location, was then exposed when two people responded to the email by selecting “reply all”.<\/p>\n<\/div>\n<\/div>\n

\n
\n

A MoD internal investigation found two similar incidents, bringing the total number of people affected to 265, the Information Commissioner’s Office said.<\/p>\n<\/div>\n<\/div>\n

\n
\n

According to the ICO, the Bcc error is one of the top causes of data breaches.<\/p>\n<\/div>\n<\/div>\n

\n

‘Could have cost lives’<\/span><\/h2>\n<\/div>\n
\n
\n

An interpreter affected by the breach, speaking in 2021, told the BBC the mistake “could cost the life of interpreters, especially for those who are still in Afghanistan.”<\/p>\n<\/div>\n<\/div>\n

\n
\n

“Some of the interpreters didn’t notice the mistake and they replied to all the emails already and they explained their situation which is very dangerous. The email contains their profile pictures and contact details.”<\/p>\n<\/div>\n<\/div>\n

\n
\n

Former defence secretary Ben Wallace said at the time it would be an understatement to say he had been angered by the breach.<\/p>\n<\/div>\n<\/div>\n

\n
\n

The incident “let down the thousands of members of the armed forces and veterans,” Mr Wallace told the House of Commons in September 2021.<\/p>\n<\/div>\n<\/div>\n

\n
\n
\n
\n
\n
\n
<\/svg><\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

This video can not be played<\/p>\n

To play this video you need to enable JavaScript in your browser.<\/h2>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/figure>\n<\/div>\n
\n
\n

The ICO’s investigation into the breach found between August and September 2021, the MoD failed to comply with UK data protection requirements for technical processes to safeguard data.<\/p>\n<\/div>\n<\/div>\n

\n
\n

It acknowledged the difficult circumstances under which the incident occurred but “when the level of risk and harm to people heightens, so must the response,” Mr Edwards said.<\/p>\n<\/div>\n<\/div>\n

\n
\n

The watchdog said it had reduced an initial fine of \u00a31m to \u00a3700,000 in recognition of the measures taken by the MoD to report the incident, limit its impact and the difficulties of the situation for teams handling the relocation of staff.<\/p>\n<\/div>\n<\/div>\n

\n
\n

This was cut further to \u00a3350,000 as part of an ongoing effort by the ICO to reduce the impact of government fines on the public.<\/p>\n<\/div>\n<\/div>\n

\n
\n

The MoD said it had “cooperated extensively” with the data watchdog to resolve the breach.<\/p>\n<\/div>\n<\/div>\n

\n
\n

“We recognise the severity of what has happened. We fully acknowledge today’s ruling and apologise to those affected”, a spokesperson said.<\/p>\n<\/div>\n<\/div>\n

\n
\n
\n

Related Topics<\/h2>\n<\/div>\n
\n