Re: A proactive internal threat mitigation program

[craig wilson <craigjw2006 () googlemail com>]

Hi WALI,

Assuming that you don't have a blanket policy where domain users are
part of local admins I wouldn't concern myself with someone attempting
to access anothers C drive.  Similarly, if your Exchange is correctly
permissed users will not be able to access others mailboxes (calendars
perhaps but that is something the users need to specifically allow so
possibly a user education issue).

More pertinent might be users ability to take data that they
shouldn't, ie pen drives etc.  What sorts of things are you worried
about from an internal perspective?  I'd advise against compacency
from an external view too; if you think users might try to gain access
to others owa then its possible externally too.

Do you have Snort running? Stick it in and get an understanding of
what 'non business' stuff is flying around

Craig

> On Sat, Dec 11, 2010 at 7:27 AM, WALI <hkhasgiwale () gmail com> wrote:
> > Guys
> >
> > I was thinking of implimenting a proactive internal threat mitigation program. Something the sort of SIEM vendors 
> > often talk about but are very lousy in their detail plans.
> >
> > Given the fact that we are not a Banking/ financial institution, the external threats are not something to be 
> > overtly worried about. what I might be worried about would be things like, people trying to log into from other's 
> > workstations and creating account lockout instances, people trying to access C$ shares on others desktops, people 
> > trying to access other's mailboxes by typing other's mailbox name via OWA in the URL field of their browser etc.
> >
> > In an overall Microsoft environment, what other factors would amount to proactive security profiling from internal 
> > malicious threats?
> >
> > Has someone been there and done that?
> >
> > WALI
> >
> > ------------------------------------------------------------------------
> > 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
------------------------------------------------------------------------