Access over 20 million homework & study documents

NTC 360 Week 4 -- Network Security -- Team D.

Content type
User Generated
Type
Homework
Rating
Showing Page:
1/8
Network Security 1
Running header: NETWORK SECURITY
Network Security: The Case of Huffman Trucking
Team D: Will Mason, Paul Bropleh II, Detricia Coardes,
Alexander Rodriguez, and Michelle Walker
University of Phoenix
NTC 360
Stephen Omogbehin
February 16, 2007

Sign up to view the full document!

lock_open Sign Up
Showing Page:
2/8
Network Security 2
The Case of Huffman Trucking
Network security is more important today than at any time previously; networks move
larger amounts of data (often secure date), hackers can gain access by various means, and even
employees can compromise the overall security of the network. A company can tighten its
overall security by ensuring that all corporate offices and plants possess the same type of
networking protocols, network operating system (NOS), cabling, and network equipment.
Huffman needs to examine the current state of its networks (both offices and plants), identify
security needs, advantages and disadvantages of various security approaches, and recommend
the optimal combination of cabling, NOS, protocols, and network equipment.
The current state of Huffman Trucking’s network
The current state of the network at Huffman Trucking is a mismatched array of NOS,
protocols, cabling, and networking equipment. The following is a list, by site, of the various
security implementations at Huffman Trucking:
1. California plant – Ethernet network, TCP/IP protocol, Cat 5
cabling, Windows 2000 Server, Windows 2000 Proxy Server,
Bay Networks router and hub
2. California office – TCP/IP protocol, Bus Topology, no routers,
no switches, no hubs, Cat 3 cabling, Windows 3.x and 9.x
environment, stand-alone IIS (Internet Information Services)
server, no firewall, 28.8 Kbps modem
3. Missouri office – Cat 5 cabling, Novell 4.11, Novell Border
Manager, IPX/SPX protocol, Norton Anti-virus Corporate
Edition, Cisco 10 Mb Hub and Switch
4. Missouri plant – TCP/IP protocol, Cisco 10 Mb Hub, Cat 3
cabling, Wyse terminals
5. New Jersey office – Bus Topology, TCP/IP, no routers,
switches or hubs, Cat 3 cabling, stand-alone IIS Web Server, no
firewall, 28.8 Kbps Modem
6. New Jersey plant – Star Topology, dumb terminals, Windows
3.x Central Terminal, ISDN Connection, patch panel at center
of network
7. Cleveland office – Token Ring network, IPX/SPX protocol,
Cisco router, 10 Mb Hub, and Switch; Cat 5 wiring, Novell

Sign up to view the full document!

lock_open Sign Up
Showing Page:
3/8

Sign up to view the full document!

lock_open Sign Up
End of Preview - Want to read all 8 pages?
Access Now
Unformatted Attachment Preview
Running header: NETWORK SECURITY Network Security: The Case of Huffman Trucking Team D: Will Mason, Paul Bropleh II, Detricia Coardes, Alexander Rodriguez, and Michelle Walker University of Phoenix NTC 360 Stephen Omogbehin February 16, 2007 The Case of Huffman Trucking Network security is more important today than at any time previously; networks move larger amounts of data (often secure date), hackers can gain access by various means, and even employees can compromise the overall security of the network. A company can tighten its overall security by ensuring that all corporate offices and plants possess the same type of networking protocols, network operating system (NOS), cabling, and network equipment. Huffman needs to examine the current state of its networks (both offices and plants), identify security needs, advantages and disadvantages of various security approaches, and recommend the optimal combination of cabling, NOS, protocols, and network equipment. The current state of Huffman Trucking's network The current state of the network at Huffman Trucking is a mismatched array of NOS, protocols, cabling, and networking equipment. The following is a list, by site, of the various security implementations at Huffman Trucking: 1. California plant - Ethernet network, TCP/IP protocol, Cat 5 cabling, Windows 2000 Server, Windows 2000 Proxy Server, Bay Networks router and hub 2. California office - TCP/IP protocol, Bus Topology, no routers, no switches, no hubs, ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Anonymous
Great content here. Definitely a returning customer.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Similar Documents