Networking and Security

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
It seems to me that, depending on your requirements, maybe connecting
an Intranet out to the Internet is unnecessary altogether. If a
company were working on a highly secure project that hackers would be
interested in looking at or stealing, why not completely isolate your
work computers? Period. Allow worker computers to network together to
share files but allow no direct physical Internet access whatsoever,
not even a proxy server. Keep them isolated either in the same room or
in the same building but allow no packets between those workstations
to even enter a DMZ.

It may not be the best example, but I can think of the situation last
year where Valve software had part of its code for "Half Life 2"
stolen by a hacker. To me, for a project of that magnitude, with such
a high profile, it would have been worth it to pay the extra money to
keep employees situated in the same building to work on that project.
The money spent would be an investment and an insurance against
someone coming in to steal code. It probably has cost Valve millions
of dollars because of this theft.

Keep email communications to one workstation not connected to the
Intranet at all and allow employees to send text-only formatted
messages out to the Internet with no attachments allowed. If employees
want to surf the net or email non-work related material they can do it
on their laptops on a wireless connection outside of the office on
their own time. The obvious responses to this would be a Unix, Linux
or Mac-enabled network, which would be less prone to hacking, but why
even allow for the possibility? Depending on the stakes involved it
may not be worth the risk to have direct Internet connectivity on a
secure project. Especially these days. Just my two cents.

Re: Networking and Security

into the usenet group
Quoted text here. Click to load it
Its called an airgap.

Devdas Bhagat

Site Timeline