Assignment
Your proposal will be submitted in three major parts:
• Analysis and Planning (i.e., Part 1)
• Securing Boundary Devices, Hosts, and Software (i.e., Part 2)
• Securing Data at Rest and in Transit (i.e., Part 3)
Each of these parts will be submitted to the LEO Assignments folders and TurnItIn. Each of these parts should be submitted independently of the other parts to TurnItIn. That is, only submit Part 1 to the Part 1 TurnItIn folder, Part 2 to the Part 2 TurnItIn folder, and Part 3 to the Part 3 TurnItIn folder. When submitting Part 1 to the LEO - Assignments - Network Security Proposal Part 1 submission folder, only submit Part 1. When submitting Part 2 to the LEO - Assignments - Network Security Proposal Part 2 submission folder, submit Parts 1 and 2 as a single document. When submitting Part 3 to the LEO - Assignments - Network Security Proposal Part 3 submission folder, submit Parts 1, 2, and 3 as a single document.
To learn how you will be assessed on this assignment, take a moment to review the rubric. The final deliverable should adhere to the following criteria:
• Use this template as a guide while creating your Network Security Proposal (Parts 1-3).
• Include at least two scholarly references in each of the three submissions. Thus, a total of six scholarly references will be included in total. Students may find scholarly sources by visiting UMUC's library and online sources. Students will also include other credible sources as appropriate.
• Use IEEE-style citations. We do not use APA or MLA-style citations. Students should contact UMUC's Effective Writing Center for assistance.
• Use proper terminology and expand acronyms in each paragraph they are used. For example, the first time in a paragraph an acronym is used it should be expanded (e.g., University of Maryland University College (UMUC). Thereafter, and as long as you are in the same paragraph, the acronym (e.g., UMUC) can be used. When starting a new paragraph, the rule begins anew.
• The use of figures and diagrams is encouraged. Students will properly cite the figures and diagrams according to the IEEE-style citation.
• Before submitting each part to the appropriate folder in LEO - Assignments, students will upload to TurnItIn. Students should review the LEO - Announcements for specific instructions or contact the Professor.
Analysis and Planning
In this section, students will address each of the following:
• Define the vulnerability assessment requirement, propose a solution, and justify the solution.
o Students should review the text and example provided but do not include it with their submission. Delete the text and include you own.
• Define the security policy requirement, propose a solution, and justify the solution.
o Students should be specific when defining the overall security outlook for the organization.
• Define the risk management requirement, propose a solution, and justify the solution.
o Students should describe the process, its value to the organization, and use proper terminology.
• Define the business continuity plan requirements, propose a solution, and justify the solution.
o Student should describe the activity in detail, and include each of the plan types.
• Define the access controls requirement, propose a solution, and justify the solution.
o Students should be specific with the type of access control model they select.
Students will find the majority of information working through the TestOut LabSim labs. Students should seek additional information to include in each submission as described in the overview by searching scholarly journals and other credible sources as appropriate. Reputable technical websites can be considered a credible source, but make sure to include at least two scholarly sources for each part of the Network Security Proposal.
Securing Boundary Devices, Hosts, and Software
In this section, students will address each of the following.
Define the physical security requirements, propose a solution, and justify the solution.
At a minimum, students should discuss the three main factors of prevention, detection, and recovery; and include the appropriate control measure.
• Define the physical security requirements, propose a solution, and justify the solution.
o At a minimum, students should discuss the three main factors of prevention, detection, and recovery; and include the appropriate control measure.
• Define the mobile device security requirements, propose a solution, and justify the solution.
o Students should include smartphones, laptops, tablets, or any other mobile device that may be introduced in the UMUC environment. Students should also include the considerations and their implications.
• Define the perimeter defense requirements, propose a solution, and justify the solution.
o Students should consider the different types of attacks, security appliances, and the network configuration to implement.
• Define the network defense requirements, propose a solution, and justify the solution.
o Students should discuss common network devices, their vulnerabilities, and propose defensive solutions.
• Define the host defense requirements, propose a solution, and justify the solution.
o Students should the types of attacks hosts are susceptible to, and proposal defensive solutions.
Securing Data at Rest and in Transit
In this section, students will address each of the following.
• Define the public key infrastructure (PKI) requirements, propose a solution, and justify the solution.
o Students should be specific when discussing the implementation and configuration required for the PKI solution.
• Define the secure protocol implementation requirements, propose a solution, and justify the solution.
o Students should consider data as it is in transit and discuss the numerous scenarios and solutions to protect it.
• Define the file encryption requirements, propose a solution, and justify the solution.
o Students should consider data at rest and discuss the numerous scenarios and solutions to protect it.
• Define the file hashing implementation, propose a solution, and justify the solution.
o Students should consider where hashing should be implemented in the network design and explain what it provides in each instance.
• Define the backup and restoration implementation, propose a solution, and justify the solution.
o Students should explain the process, where it is applicable in the UMUC network scenario, and how it will be achieved (process, hardware, and frequency).