Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: Web access and e-mail gateway policy

Subject: Re: Web access and e-mail gateway policy
Date: Tue, 22 Mar 2005 07:08:12 +0100
Hello Alvin

I'm aware that it covers just 10% of the policy I need. Thats why I post to this list ;) . I also agree that for a final policy I must mention solutions to those tasks but first I must have an idea of the scope or a collection of issues I must take care of.

The policy should be used for work. The way they will be implemented is then something different. Either one chooses an approproate tool for that or as you said, some features must be implemented. But at the time I don't care about this.

The points you mentioned at the end should not be part of a "web access" or "e-mail gateway" policy. They are also importand but they belong to other policies.
What I want to write down are rules to handle the traffic at the gateway either for e-mail or for web.


Thanks!

On Mar 22, 2005, at 4:46, Alvin Oga wrote:


hi ya nik

On Sun, Mar 20, 2005 at 08:52:38PM +0100, Niklaus Schild wrote:

I’m looking for examples and ideas on how to setup some special policies, which I’ve never seen in the web so far. The policies I’m looking for should guide as a reference for configuring web access and an e-mail gateways.

good start for the policy .. but it only covers say 10% of the "email/web" policy that you'd need

more importantly, for each of those items, you will need to implement
a solution to perform that task and another solution to enforce
that rules and deal with violations of the rules/policy

i'm curious .. is this setup for home or work ??

if for work, its lacking .... if its for home ... it might be a good
start

how to implement those rules.... some are "free" and already part
of the distro ... other rules are user defined and you have to add
software/perl/xxx-apps to perform the tasks you specified

more important .... bad-boy-pete decides to bypass your rules ...
now what do you do ?? and how ???

-- the question/problem is that we cannot do those things for you ...

        and i think if you want it solved, either youhave to sit
        down and implement each fo those rules or hire someone
        to implement your "policy rules" for you .. including
        the other 90% of the rules you didn't mention

        - backups, passwds, xxx content, you-been-hacked-now-what,
        people walking out with PC, dhcp, wireless, ...
        firewalls, routers, ... on and on ..

c ya
alvin


The policy should consider the following issues:  

Web access gateway:
-       scanning of downloaded content
-       blocking of certain file types
-       blocking of certain site categories
-       what happens with infected content
-       log and quarantine management
-       alerting
-       configuration responsibilities
-       configuration change procedure 

e-mail gateway:
-       scanning of e-mails and attachments
-       handling of spam
-       restricting attachment size and type
-       handling of infected attachments
-       log and quarantine management
-       alerting
-       configuration responsibilities
-       configuration change procedure

any other ideas, considerations or suggestions? Thanks in advance!

Nik




<Prev in Thread] Current Thread [Next in Thread>