RE: Height of paranoia

Sometimes info can leak through simple and ancient techniques.

As an IT guy, I know about all of my execs passwords. Who knows who else does. So, having them change their passwords would be my first thought.

Second, you might check the Exchange permissions inside their AD account to see who else has access to their email account. I have seen some weird stuff before - a client who was going thru a divorce had info leaking, come to find out somehow his ex-wife's name had full permission to his mailbox and she was loading his account up in her Outlook.

Also keep in mind that the Administrator account probably has access to their email as well, it's as simple as File > Open > Other Users Folder. So check the permissions just to make sure nothing obvious is jumping out at you.

The other suggestions are all good too. I just think it's good to start with the basic obvious stuff - you can lock down the network all you want but if someone owns the password, they pretty much own the user.

Scott

-----Original Message-----
From: listbounce@xxxxxxxxxxxxxxxxx [mailto:listbounce@xxxxxxxxxxxxxxxxx] On Behalf Of Adam Pal
Sent: Thursday, August 28, 2008 1:48 AM
To: security-basics@xxxxxxxxxxxxxxxxx
Cc: hkhasgiwale@xxxxxxxxx
Subject: Re: Height of paranoia

Hi Wali

As a fist measurement, i would separate the executive managers network, move the stations to another/new network segment. There you can also enable a different set of ACL rules.

As a 2nd measurement i would use point-to-point encryption, high confidential emails should be encryptet however so that would be a good time to apply it.
There are a lot of tools, but you can pick one which is costs-effective and easy to implement in outlook.


regards

Adam Pal


-------- Original-Nachricht --------
Datum: Wed, 27 Aug 2008 19:55:14 +0400
Von: "WALI" <hkhasgiwale@xxxxxxxxx>
An: security-basics@xxxxxxxxxxxxxxxxx
Betreff: Height of paranoia

It's a given that all workstations have XP firewall enabled, an enterprise
grade antivirus and Windows defender installed. I am the security guy.

The need is that there are a couple top management executives that have
highly confidential data/emails residing on their desktops, and quite a
few
times, the information seems to have leaked out.

Discounting the 'word of mouth' of their secretaries or the end recipients
of that information, I want to take as many precautions from the IT
security
perspective as possible and even bring our domain admins and helpdesk
personnel into the realm of doubt.

We have a Windows 20003/exchange 2003 environment of about a 2000 users.
Here's what I have thought:

1. If I detach these executive PCs from the domain. Mails will stop
landing
in MS Outlook. Is there a way around? Also DNS security doesn't register
any
PC unless it's joined to a domain. I thought of this to make it out of
bounds by system/domain admins. I have a feeling that their port 3389 gets
accessed when they aren't around.

2. Alternatively, create a private vlan on the core switch and make these
PCs as it's members. Put an ACL and deny everything except ports required
to
authenticate to AD and exchange and few other web applications. Monitor
port
memberships regularly.

3. How to secure their emails from exchange admins (it's the height, I
know).

Pls advise!!

--
Psssst! Schon das coole Video vom GMX MultiMessenger gesehen?
Der Eine für Alle: http://www.gmx.net/de/go/messenger03

Relevant Pages

  • Re: Some new SSH exploit script?
    ... So for those small sites or sites only allowing ssh in for specific persons such as a few admin and perhaps a few application maintainers, and even a vendor or two, we find it easier to maintain the standard port and restrict access in the firewall and tcpd to specific addresses, and on occasion users via sshd_config settings as well. ... Log cruft is a pretty lame reason and rational for making a choice to implement a non-standard port setting, admins should have the skills to filter and parse logs in a manner such that the cruft does not interfere with their daily log monitoring chores, else they have likely a lot of other cruft that must as well be driving them to near madness as well not relating to sshd and the kiddie brute-forcing tool of the week. ... I believe in security in-depth, but this depth is so superficial, I ... Download FREE whitepaper on how a managed service can ...
    (Pen-Test)
  • RE: [Full-Disclosure] RE: MS SQL WORM IS DESTROYING INTERNET BLOCK PORT 1434!
    ... > a normal port for SQL server *until* MSDE came out. ... Paul -- what ever happened to the first rule (maybe its the second ... Perhaps some of the .edu admins need to first ... design concepts and security. ...
    (Full-Disclosure)
  • Re: ID-ing Hackers
    ... I'm using my sonicwall firewall to trace the incoming connections ... port 25 and cross referencing them to my security log and the blocking IP ... I took everyone's advice from here and boosted my passwords to 15 digits. ... That log is an attempt on port 25... ...
    (microsoft.public.windows.server.sbs)
  • Re: ID-ing Hackers
    ... I'm using my sonicwall firewall to trace the incoming connections to ... port 25 and cross referencing them to my security log and the blocking IP ... I took everyone's advice from here and boosted my passwords to 15 digits. ... That log is an attempt on port 25... ...
    (microsoft.public.windows.server.sbs)
  • Re: Possible attack?
    ... That's also why the USB dongle only provides part of the ... non-standard port. ... are getting more concerned with 'homeland security' idiots than we used ... Well, after all, we're asking them to remember reusable passwords too, ...
    (comp.os.linux.security)