Fwd: Monitoring emails.

[Peter Odigie <peterodigie () gmail com>]

---------- Forwarded message ----------
From: Peter Odigie <peterodigie () gmail com>
Date: Mon, Jun 13, 2011 at 12:04 PM
Subject: Re: Monitoring emails.
To: Sebastien MAHIEUX <sebastien.mahieux () gmail com>
Cc: security-basics () securityfocus com




On Mon, Jun 13, 2011 at 10:32 AM, Sebastien MAHIEUX
<sebastien.mahieux () gmail com> wrote:
> Hi,
> My questions are :
> What do you need to record (Sender, Receiver, body, subject) ? The cost and the infrastructure will depend on the 
> volume of informations stored.

****I will need to record Sender, Receiver and subject at least. Body
is optional.

> What do you mean by "the system does not has to be always on.". Does it will used for audit on demand ?

****I mean that at the end of office hours they will shutdown the
system and start it again the next day. But when it starts,  it should
be ****able to pull all the messages that was sent when it was
offline.
> There are some DLP solution which can help you, I can define with you regarding the response at the questions. For 
> the avaibility you can use the MX for the failover.

****Thanks Sebastien
> Regards.
> Sebastien.
> 2011/6/12 <peterodigie () gmail com>
> > Hi all!
> >
> > I am seeking for ideas. A firm will want to monitor the emails of its staff,
> > knowing all the mails that pass through its domain. They have a domain with
> > email accounts registered and hosted by an independent body. Staff access
> > their email account within and outside the internal network (using their
> > Blackberry and other networks). Part of the issue at hand is how can you
> > affirm that a particular mail got to another staff. Some staff affirm that
> > they have sent a mail to another staff and while that other staff denies it.
> >
> >
> > One option is for them to speak with the domain registrar and set up a
> > monitoring account but they want something in house - within their internal
> > network. A system that collects all the mails that pass through their
> > domain; the system does not has to be always on.
> >
> > F1!!!!!
> >
> > Thanks.
> >
> > Peter
> >
> >
> > ------------------------------------------------------------------------
> > Securing Apache Web Server with thawte Digital Certificate
> > In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, 
> > how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, 
> > purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for 
> > set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital 
> > certificates.
> >
> > http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
> > ------------------------------------------------------------------------

------------------------------------------------------------------------
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, how 
it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, 
install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are 
highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
------------------------------------------------------------------------