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

Help for DATA-PROTECTION Archives


DATA-PROTECTION Archives

DATA-PROTECTION Archives


data-protection@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

DATA-PROTECTION Home

DATA-PROTECTION Home

DATA-PROTECTION  November 2008

DATA-PROTECTION November 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Monitoring of encrypted (SSL) data

From:

"[log in to unmask]" <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 24 Nov 2008 13:41:30 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (198 lines)

The trust issues as described are all one way. Putting it simply:-

The organisation has decided not to trust its employees so will 
constantly monitor them (Could effective training be an alternative?); 
The employee’s rationale appears to be that for the good of the 
organisation they will have to trust the organisation;
That means employees trusting other employees, which the organisation 
has shown by its considered actions that it does not do, it monitors 
instead.

If the organisation collectively will not trust its employees, what 
causes the employees to trust other employees within the organisation?

> I use the web at work to log on to my trade union site - 

I do recollect from my experience an instance where an organisation 
was demanding access to computer material, which related to the union 
activity of an employee where even knowing about that particular 
activity would have compromised the organisation in ongoing legal 
proceedings. They were denied that access but at some outward cost of 
trust to the person doing the denial of access. Where information is 
processed within an organisation something more than a surface veneer 
of codes of practice/conduct is required, and it has been my impression 
even those basics are often lacking, dealt with or got around.

> scenario is managed by my employer agreeing not to intercept 
> https: traffic with banking sites. The risk to them is 
> minimal (few banks offer malware or even videos as part of 
> their services!), so the employer can afford to be relaxed 
> about that, and it means that the most obviously tempting 
> information is unavailable, even theoretically, to the 
> sysadmins.

Do organisations take an interest in the financial affairs of 
employees and because of that will they never intercept financial 
information where for some reason it was suspected it would definitely 
be in the organisations interests?
Looking to the practices and actions of head hunters, employment 
agencies and others reveals some answers to that question. Most are 
trusted to find information about prospects in return for a financial 
reward.

Such fundamental value issues are clearly privacy, as well as 
organisational management related and in my view crux in creating an 
informed level of understanding around this area.


Ian W

> -----Original Message-----
> From: This list is for those interested in Data Protection 
> issues [mailto:[log in to unmask]] On Behalf Of 
> Ben Plouviez
> Sent: 24 November 2008 09:11
> To: [log in to unmask]
> Subject: Re: [data-protection] Monitoring of encrypted (SSL) data
> 
> 
> Interestingly, the more I've thought about this, the more 
> relaxed about it I am.
> 
> I use the web at work to log on to my trade union site - 
> since personal use for harmless purposes is allowed under my 
> employer's acceptable use policy. That traffic - normal http: 
> traffic - is intercepted by the Blue Coat proxy my employer 
> uses and passed through a virus and content scanner, to make 
> sure I'm abiding by the acceptable use policy, and in 
> particular that I'm not downloading executables or videos, 
> both of which are banned by that policy. If I try to do so, 
> those items will be stopped, and the fact logged. Otherwise, 
> the traffic relating to my actions on my union's site are 
> passed straight through to me. Note that sensitive personal 
> information is involved here (trade union
> membership): if I really didn't want to let my employer know 
> that I was a union member, I would be foolish to log on to 
> that site while at work.
> 
> 
> Now think about the interception of SSL (https:) traffic. My 
> employer is proposing to do pretty much exactly the same 
> thing with that traffic. This will ensure that they know I'm 
> not downloading executables or other banned material through 
> this backdoor (and will stop me if I do). They will not 
> store any other information from the https: stream, any more 
> than they do from the http: stream, but informaiton about my 
> attempts to download naughty stuff will similarly be recorded. 
> 
> So, there are three issues.
> 
> First: is my personal information safe? Well, theoretically, 
> a sysadmin could steal my information while it's on the proxy 
> server network - s/he would, of course, be committing all 
> kinds of offences in doing so. That high risk/high impact 
> scenario is managed by my employer agreeing not to intercept 
> https: traffic with banking sites. The risk to them is 
> minimal (few banks offer malware or even videos as part of 
> their services!), so the employer can afford to be relaxed 
> about that, and it means that the most obviously tempting 
> information is unavailable, even theoretically, to the 
> sysadmins. Without question, some risk to personal data I 
> pass through the network remains (as it does with http: 
> traffic), and good logging and security on the servers is 
> essential, as ever.
> 
> Second: is there a good enough reason for doing this? That is 
> a business judgement about the risks of disruption (caused by 
> malware etc) which could be caused by my using https: traffic 
> to breach the security of the network. We could argue about 
> proportionality here, but in the end it is a business 
> decision and hence up to my employer to decide whether or not 
> the activity is in their legitimate interests.
> 
> Third: do I need to know? I'm already informed by our 
> acceptable use policy that my internet use at work is 
> monitored. If I know a little (but not enough!) about proxy 
> servers and all their ways, I may believe (and did, until 
> last week) that technically this cannot include https: 
> traffic. But I would be foolish to try to take advantage of 
> that supposed fact by doing something that exposed highly 
> sensitive personal information that I really didn't want my 
> employer to know while using my employer's network. And, of 
> course, I would be doubly foolish to rely on the security of 
> https: to break my employer's acceptable use policies - or at 
> least I would have no reason to complain if I got caught. 
> However, since there do seem to be people who believe that 
> internet access comes free from Heaven and that internet 
> privacy is a divine right irrespective of whose internet 
> connection they're (ab)using, it would probably be sensible 
> for my employer to make it clear exactly what they are doing. 
> 
> Sorry about the length of this! But does anyone have any real 
> issue with any of it?
> 
> Ben 
> 
> -----Original Message-----
> From: This list is for those interested in Data Protection 
> issues [mailto:[log in to unmask]] On Behalf Of 
> [log in to unmask]
> Sent: 22 November 2008 18:50
> To: [log in to unmask]
> Subject: Re: [data-protection] Monitoring of encrypted (SSL) data
> 
> *******************************************************************
> This email has been received from an external party and has 
> been swept for the presence of computer viruses.
> *******************************************************************
> 
> There is another aspect which can affect an organisations 
> decision on the risk balances of an ssl proxy.
> 
> Where a site is connected via ssl to a user, that site has 
> access to a user's pc outside many of the controls exerted by 
> a firewall.
> 
> Symantec describes this as: -
> "Some Web sites and email servers use SSL (Secure Sockets 
> Layer) connections to encrypt connections between your 
> computer and the server. Privacy Control cannot block private 
> information sent through SSL connections. However, since the 
> information is encrypted, only the recipient of the email or 
> Web communication will be able to read the message."
> 
> Becoming proactive would not necessarily solve the problems 
> as intelligent consideration of the required growth in 
> organisational management and security to effectively control 
> those areas indicates.
> 
> Trust can be a funny thing. Imagine a savvy, driven, employee 
> (or a corrupt one) setting up their own secure connection at 
> home or utilising one elsewhere, do you live with that 
> singular possibility, or configure systems to stop all 
> potential problems?
> 
> 
> Ian



Money Saving Vouchers - http://www.tiscali.co.uk/shopping

__________________________________________________________

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     All archives of messages are stored permanently and are
      available to the world wide web community at large at
      http://www.jiscmail.ac.uk/lists/data-protection.html
     If you wish to leave this list please send the command
       leave data-protection to [log in to unmask]
All user commands can be found at http://www.jiscmail.ac.uk/help/commandref.htm
 Any queries about sending or receiving messages please send to the list owner
              [log in to unmask]
  Full help Desk - please email [log in to unmask] describing your needs
        To receive these emails in HTML format send the command:
         SET data-protection HTML to [log in to unmask]
   (all commands go to [log in to unmask] not the list please)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 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


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