Soldato
- Joined
- 4 Nov 2006
- Posts
- 2,752
- Location
- Yorkshire
I've now got Exchange 2010 OWA accessible on the internet for our staff, albeit they don't know yet, it's fully SSL secure and I've had it penetration tested and it passed fine.
One of the main concerns from our information governance team is regarding attachments. For example, a member of staff accesses OWA via their browser on their home PC, opens an attachment that has sensitive data in, which is then stored locally in their temp files, they close OWA down and walk away, leaving that file still lurking until their temp files are cleaned up by their browser. Obviously the same goes for people who save said attachment, but at least then they know that they've done it and can delete the file easily.
Has anyone else faced similar a issue and how did you manage it?
One of the main concerns from our information governance team is regarding attachments. For example, a member of staff accesses OWA via their browser on their home PC, opens an attachment that has sensitive data in, which is then stored locally in their temp files, they close OWA down and walk away, leaving that file still lurking until their temp files are cleaned up by their browser. Obviously the same goes for people who save said attachment, but at least then they know that they've done it and can delete the file easily.
Has anyone else faced similar a issue and how did you manage it?