How to create shared services that two different parties can use

How to create shared services that two different parties can use

I manage the computer systems for a university. We have a local Win2k network domain with an intranet Web site and Exchange 5.5 Server running on it. Sometimes our students try to hack into the teachers' computers. In an effort to prevent this, I want to set up another domain for the students, but still allow them to access the intranet and Exchange mail system when their teachers are monitoring them. How can I accomplish this?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

You're facing a problem common to educational institutions. I would strive to isolate student and administrative networks as much as possible. It's extremely difficult to secure environments where users have two different security levels (e.g. students and teachers) on the same network, regardless of their domain membership.

It's entirely possible to implement shared services, such as the mail and Web services you mentioned. I suggest using a four-interface firewall to create separate zones for students, teachers, shared services and the Internet. The Web server and intranet server would then live in the shared services zone or DMZ and benefit from the protection of the firewall's rulebase.

This was first published in August 2006