If you are only going to lock down the system and executables and not the
network, then how would you tackle traffic from the Java-based AIM client
(http://www.aim.com/get_aim/express/aim_expr.adp) and other similar
applications (IRC applets, etc.)?

Locking down the workstations and using products like SecureEXE may help,
but if you are serious about clamping down on this you'll need to use the
"total package" because as dumb as we like to think the users are - if they
want to do something they will do all they can to find a way around the
security/obscurity.

Eric

----- Original Message -----
From: "Kurt Seifried" <bugtraqseifried.org>
To: <focus-idssecurityfocus.com>
Sent: Friday, January 04, 2002 3:46 PM
Subject: Re: how can I track networked games

> Seriously, these application level issues are best handled at the
> applicaiton level. Enforce what users can install/run on their systems
(i.e.
> block them from doing so unless they must). Windows nt/2000 has support
for
> policies/etc to accomplish this, on WIndows 9X there are options as well.
>
> <commercial>SecureEXE from SecureWave will accomplish this.
> www.securewave.com. In my opinion that is the right approach to this, not
> fiddling with the network (which is doomed to fail, peer to peer file
> sharing for example uses ports all over the map, new apps you never heard
of
> come out, etc. SecureEXE will fix this.</commercial>.
>
>
> Kurt Seifried, kurtseifried.org
> A15B BEE5 B391 B9AD B0EF
> AEB0 AD63 0B4E AD56 E574
> http://www.seifried.org/security/
>
>
>
>
>
>
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]