CIS534 WEEK 10 TERM PAPER Designing a Secure Network

Points: 190

Term Paper Project: Designing a Secure Network

Criteria

Unacceptable Below 70% F

Fair 70-79% C

Proficient 80-89% B

Exemplary 90-100% A

Part 1

1ai. Create a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you follow the access, core, distribution layer model using Visio or its open source alternative. Weight: 5%

Did not submit or incompletely created a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you followed the access, core, distribution layer model using Visio or its open source alternative.

Partially created a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you followed the access, core, distribution layer model using Visio or its open source alternative.

Satisfactorily created a diagram showing the overall network you’<="" p="">

Thoroughly created a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you followed the access, core, distribution layer model using Visio or its open source alternative.

1aii. Create a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you include at a minimum authentication server, routers, switches, local users, remote users, workstations, file share, mail server, Web servers, firewalls, Internet cloud, Web proxy, email proxy, and FTP server using Visio or its open source alternative. Weight: 5%

Did not submit or incompletely created a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you included at a minimum authentication server, routers, switches, local users, remote users, workstations, file share, mail server, Web servers, firewalls, Internet cloud, Web proxy, email proxy, and FTP server using Visio or its open source alternative.

Partially created a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you included at a minimum authentication server, routers, switches, local users, remote users, workstations, file share, mail server, Web servers, firewalls, Internet cloud, Web proxy, email proxy, and FTP server using Visio or its open source alternative.

Satisfactorily created a diagram showing the overall network you’ ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you included at a minimum authentication server, routers, switches, local users, remote users, workstations, file share, mail server, Web servers, firewalls, Internet cloud, Web proxy, email proxy, and FTP server using Visio or its open source alternative.

Thoroughly created a diagram showing the overall network you’ve designed from the user or endpoint device to the Internet cloud, and everything in between, in which you included at a minimum authentication server, routers, switches, local users, remote users, workstations, file share, mail server, Web servers, firewalls, Internet cloud, Web proxy, email proxy, and FTP server using Visio or its open source alternative.

1b. Explain each network device’s function and your specific configuration of each networking device. Weight: 5%

Did not submit or incompletely explained each network device’s function and your specific configuration of each networking device.

Partially explained each network device’s function and your specific configuration of each networking device.

Satisfactorily explained each network device’s function and your specific configuration of each networking device.

Thoroughly explained each network device’s function and your specific configuration of each networking device.

1c. Design and label the bandwidth availability or capacity for each wired connection. Weight: 5%

Did not submit or incompletely designed and labeled the bandwidth availability or capacity for each wired connection.

Partially designed and labeled the bandwidth availability or capacity for each wired connection.

Satisfactorily designed and labeled the bandwidth availability or capacity for each wired connection.

Thoroughly designed and labeled the bandwidth availability or capacity for each wired connection.

Part 2

2ai. Document and label the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the emailing scenario. Weight: 5%

Did not submit or incompletely documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the emailing scenario.

Partially documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the emailing scenario.

Satisfactorily documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the emailing scenario.

Thoroughly documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the emailing scenario.

2aii. Include path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the emailing scenario. Weight: 5%

Did not submit or incompletely included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the emailing scenario.

Partially included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the emailing scenario.

Satisfactorily included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the emailing scenario.

Thoroughly included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the emailing scenario.

2aiii. Show user authentication when necessary for the emailing scenario. Weight: 5%

Did not submit or incompletely showed user authentication when necessary for the emailing scenario.

Partially showed user authentication when necessary for the emailing scenario.

Satisfactorily showed user authentication when necessary for the emailing scenario.

Thoroughly showed user authentication when necessary for the emailing scenario.

2bi. Document and label the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the file transfer scenario. Weight: 5%

Did not submit or incompletely documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the file transfer scenario.

Partially documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the file transfer scenario.

Satisfactorily documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the file transfer scenario.

Thoroughly documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the file transfer scenario.

2bii. Include path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the file transfer scenario. Weight: 5%

Did not submit or incompletely included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the file transfer scenario.

Partially included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the file transfer scenario.

Satisfactorily included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the file transfer scenario.

Thoroughly included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the file transfer scenario.

2biii. Show user authentication when necessary for the file transfer scenario. Weight: 5%

Did not submit or incompletely showed user authentication when necessary for the file transfer scenario.

Partially showed user authentication when necessary for the file transfer scenario.

Satisfactorily showed user authentication when necessary for the file transfer scenario.

Thoroughly showed user authentication when necessary for the file transfer scenario.

2ci. Document and label the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the VPN connection scenario. Weight: 5%

Did not submit or incompletely documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the VPN connection scenario.

Partially documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the VPN connection scenario.

Satisfactorily documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the VPN connection scenario.

Thoroughly documented and labeled the diagram showing protocols and path of the data flow as data traverses through your network from source to destination for the VPN connection scenario.

2cii. Include path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the VPN connection scenario. Weight: 5%

Did not submit or incompletely included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the VPN connection scenario.

Partially included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the VPN connection scenario.

Satisfactorily included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the VPN connection scenario.

Thoroughly included path lines with arrows showing directions and layer 1, 2, 3, 4, 5, 6, and 7 (OSI) protocols that are used for each flow for the VPN connection scenario.

2ciii. Show user authentication when necessary for the VPN connection scenario. Weight: 5%

Did not submit or incompletely showed user authentication when necessary for the VPN connection scenario.

Partially showed user authentication when necessary for the VPN connection scenario.

Satisfactorily showed user authentication when necessary for the VPN connection scenario.

Thoroughly showed user authentication when necessary for the VPN connection scenario.

2d. Explain how your overall design protects the organization from both inside and outside attacks. Give examples. Weight: 5%

Did not submit or incompletely explained how your overall design protects the organization from both inside and outside attacks. Did not submit or incompletely gave examples.

Partially how your overall design protects the organization from both inside and outside attacks. Partially gave examples.

Satisfactorily how your overall design protects the organization from both inside and outside attacks. Satisfactorily gave examples.

Thoroughly how your overall design protects the organization from both inside and outside attacks. Thoroughly gave examples.

2e. Explain how your layered design compensates for possible device failures or breaches in network security. Weight: 5%

Did not submit or incompletely explained how your layered design compensates for possible device failures or breaches in network security.

Partially explained how your layered design compensates for possible device failures or breaches in network security.

Satisfactorily explained how your layered design compensates for possible device failures or breaches in network security.

Thoroughly explained how your layered design compensates for possible device failures or breaches in network security.

2f. Determine whether any possible bottlenecks exist in your design. Weight: 5%

Did not submit or incompletely determined whether any possible bottlenecks exist in your design.

Partially determined whether any possible bottlenecks exist in your design.

Satisfactorily determined whether any possible bottlenecks exist in your design.

Thoroughly determined whether any possible bottlenecks exist in your design.

2g. Explain how to make the file transfer process more secure. Weight: 5%

Did not submit or incompletely explained how to make the file transfer process more secure.

Partially explained how to make the file transfer process more secure.

Satisfactorily explained how to make the file transfer process more secure.

Thoroughly explained how to make the file transfer process more secure.

Part 3

3. 3 references Weight: 5%

No references provided

Does not meet the required number of references; some or all references poor quality choices.

Meets number of required references; all references high quality choices.

Exceeds number of required references; all references high quality choices.

4. Clarity, writing mechanics, and formatting requirements Weight: 10%

More than 6 errors present

5-6 errors present

3-4 errors present

0-2 errors present