e-mail attachments and security

[d.auclair at utoronto.ca (David Auclair)]

Have you looked at SecureZip?

http://www.pkware.com/software-data-security

It looks like it provides good security and is easy to use...

Here's a detailed review:
http://blogs.techrepublic.com.com/security/?p=1838

The only catch is that it's payware, although they have a free decrypt-only version that the recipients can use.

-Dave


> -----Original Message-----
> From: pauldotcom-bounces at pdc-mail.pauldotcom.com [mailto:pauldotcom-bounces at pdc-mail.pauldotcom.com]
> On Behalf Of Bert Van Kets
> Sent: Wednesday, January 27, 2010 9:30 AM
> To: PaulDotCom Security Weekly Mailing List
> Subject: Re: [Pauldotcom] e-mail attachments and security
>
> My brother is an independent doctor. He's not working for a hospital. He
> has to examine employees for companies and send reports to the other
> doctors in different locations. There is no governing organization in
> this whole process except for the UK government. IMHO it's my brother's
> solitary responsibility to make sure the medical data is not getting
> into the wrong hands.
> This means he (ie me) has to find a solution that is applicable to all
> the people at the receiving end.
>
> Jim Halfpenny wrote:
> > Hi all,
> > I don't think that healthcare professionals are the right people to be
> > deciding how to transfer confidential files. Where there is a need for
> > this then the IT department of the healthcare organisation ought to
> > make provision for this. That said, I doubt if they do offer this
> > whether  through lack of resource, lack of expertise or infosec policy
> > violation.
> >
> > The underlying issus is the use and control of confidential
> > information. Do all the recipients subscribe to the same information
> > security and confidentiality policy as you? Who is liable for data
> > breaches? Again, where there is a need to share provision should be
> > made for this. There are some good suggestions in this thread but I
> > don't trust doctors to securely administer and implement them (no
> > offense intended).
> >
> > Jim
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Pauldotcom mailing list
> > Pauldotcom at mail.pauldotcom.com
> > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> > Main Web Site: http://pauldotcom.com
>
> _______________________________________________
> Pauldotcom mailing list
> Pauldotcom at mail.pauldotcom.com
> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> Main Web Site: http://pauldotcom.com