JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for GP-UK Archives


GP-UK Archives

GP-UK Archives


GP-UK@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

GP-UK Home

GP-UK Home

GP-UK  2004

GP-UK 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: NCRS security

From:

Gavin Jamie <[log in to unmask]>

Reply-To:

GP-UK <[log in to unmask]>

Date:

Tue, 18 May 2004 08:38:37 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (64 lines)

I will not cut and past. Long post and all that.

I have to say that this answered almost none of my concerns about the
systems. It is relatively easy to design a system where users are
authenticated and get access to the correct information. Labour
intensive maybe but not conceptually hard.

Briefly I have two concerns

1. The emphasis of Laurie's post (which is very helpful) is about
security of data in transit. Frankly I always had this as low risk.
Hacking into networks is generally not that easy, and whilst it is nice
to know that attention has been paid to this it was not my top priority.
It is not clear how many people will have access to my record on the
spine. Doctors at my surgery? Within my PCT area? SHA area? All doctors?
All nurses? Role based access is all very well but the role must be
appropriate. HO is not a role. HO to the vascular surgical team at the
Great Western Hospital in Swindon is.

2. There are several obvious failings of the smart card systems as
stated in the original post. First is the issuing process. When I was a
junior doctor (which was not that long ago) no hospital was able to
issue passwords until at least a week had passed in the hospital. With a
more cumbersome process this is likely to be no easier. Even if we
assume a national card system the correct allocation of roles is likely
to be slow. Managing for a hospital will be horrendous (it takes our DGH
four weeks a year to deal with parking passes). The implications of
getting it wrong - even for a day - are severe. A culture of password
and card sharing will develop. The ward PC may have a single nurses
smart card entered at the start of the shift and removed at the end. All
the PKI in the world will not solve that problem.

There was a very good analogy to car keys in the original post. Losing
the card will certainly be inconvenient. That there will be an 'onerous
process' to replace it will actively discourage reporting of loss,
certainly until a time that it will be possible or convenient to undergo
the process. I suspect that what to do at 3am on a Saturday morning will
be to use password sharing again.

Of course when your car keys are stolen then it is not only inconvenient
but the thief can drive your car. This interacts with my first point as
access to the whole database will make the card a more attractive
proposition to a thief. It also interacts with the replacement procedure
at a delay in reporting will allow the thief greater access before
revocation of the card.
Audit trails are all very well, but in this circumstance are as much use
as a tachograph on a stolen truck.

Another attack is the 'royal footman' attack. The simplest way to get
authorisation is to get a job. Getting fired may not be a problem for
these people as this was not their main job anyway but merely a means to
an end. Equally it may merely give good opportunity to observer
passwords and lift PKI cards from pockets.


Summary

There are major security issues with this system. They are complex and
not model has been publish. Shouting 'encryption' a lot merely distracts
from the more likely attacks.

--
Gavin Jamie

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
October 2023
August 2023
June 2023
May 2023
February 2023
June 2022
October 2021
January 2021
October 2020
September 2020
August 2020
July 2020
June 2020
March 2020
January 2020
December 2019
September 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997
1996


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager