Comments on: One in five NHS trusts were hit by Friday’s cyber-attack https://www.digitalhealth.net/2017/05/one-in-five-nhs-trusts-were-hit-by-fridays-cyber-attack/ News | Networks | Intelligence Sat, 23 Jul 2022 04:54:07 +0000 hourly 1 https://wordpress.org/?v=6.2.2 By: Dan https://www.digitalhealth.net/2017/05/one-in-five-nhs-trusts-were-hit-by-fridays-cyber-attack/#comment-2582 Mon, 15 May 2017 13:47:46 +0000 https://www.digitalhealth.net/?p=56988#comment-2582 In reply to Darren.

This isnt true in all cases and depending on the nature of the attack could be subverted as the especailly if the same policies /controls are not enforced locally. Its certainly more than a coincidence.

]]>
By: Darren https://www.digitalhealth.net/2017/05/one-in-five-nhs-trusts-were-hit-by-fridays-cyber-attack/#comment-2576 Mon, 15 May 2017 10:33:10 +0000 https://www.digitalhealth.net/?p=56988#comment-2576 Local email is generally routed via the NHS relays and subject to same mail hygiene systems as NHSmail. Both are managed by NHSD and Accenture.

]]>
By: K https://www.digitalhealth.net/2017/05/one-in-five-nhs-trusts-were-hit-by-fridays-cyber-attack/#comment-2568 Mon, 15 May 2017 06:38:12 +0000 https://www.digitalhealth.net/?p=56988#comment-2568 In reply to Dan.

I think the simple answer is IT/informatics wasn’t given enough priority or was funded adequately.

You don’t have to far back on this site to see common patterns emerging (and these aren’t just IT) in a number of NHS regions and trusts.

]]>
By: Dan https://www.digitalhealth.net/2017/05/one-in-five-nhs-trusts-were-hit-by-fridays-cyber-attack/#comment-2546 Sun, 14 May 2017 12:46:35 +0000 https://www.digitalhealth.net/?p=56988#comment-2546 Here are a few things that I think they will find given my experience of the NHS :

Using local email systems instead of the national system allowing malware through.
Failing to have a proper patch / update regime.
Insufficient network controls/segmentation allowing proliferation.
Failure to properly firewall legacy devices / systems.
Not using least privileges.

]]>