Cyber risk specialist David McIlwaine of Pinsent Masons, the law firm behind Out-Law, said: "Whilst the fine has reduced from £183m, as outlined in the notice of intent, to £20m, only £4m of that reduction has been specifically attributed to Covid-19. It is hard to think of an industry that has been affected more by the pandemic than the airline industry, so clearly organisations should not expect significant leniency during these times."
Data protection law specialist Claire Edwards, also of Pinsent Masons, said the approach the ICO had taken in the BA case, as well as in the case of the Marriott data breach, had been controversial and that the outcomes would be of interest to all businesses given the heightened cyber risk they face.
Edwards said: "The reduction in the fine is certainly interesting from a number of angles with BA challenging the way the ICO originally calculated the figures, the way the ICO had interpreted its enforcement powers, how the fine compared to other fines issues by European supervisory authorities where lower amounts were imposed for bigger breaches, and the assessment of the level of actual harm caused. Whilst the ICO strongly defended its original assessment, actions and processes, it seems that making a challenge to an ICO enforcement notice or notice of intent is certainly commercially worthwhile."
"Clearly there will be interest in the future of the Marriott penalty which is still pending and should this, as expected, be significantly reduced from the original estimate of £99 million then the question is whether we have a pragmatic regulator ready to listen and apply penalties which act as a proportionate deterrent or whether the ICO will capitulate from original proposed penalties that cannot be justified," she said.
In its monetary penalty notice, the ICO explained that it had dropped initial plans to impose a fine on BA over a failure to implement data protection by design and default, which is a requirement enshrined in Article 25 of the GDPR.
BA had challenged the plans on the basis that its systems for data processing had been designed prior to the GDPR taking effect. However, while the ICO rejected the basis of BA's argument, and stressed that Article 25 "'applies at the time of the processing itself' as well as at the point at which the system is designed", it decided only to make findings of infringement in relation to data security obligations under Article 5(f) and Article 32 of the GDPR.
The ICO said it was "satisfied that BA failed to put in place appropriate technical or organisational measures to protect the personal data being processed on its systems, as required by the GDPR".