2023 Network Security You have been hired as part of the network security team at UMUC After completing | Assignment Collections
Network Security
You have been hired as part of the network security team at UMUC. After completing orientation and training, your manager calls you into a meeting to discuss your first project.
The university has completed the implementation of the leased building in Adelphi, Maryland. If you recall, this was the Network Design Proposal completed in CMIT 265. The university realizes it needs to secure the faculty, students, and visitors network and data. With your background and skills, the university is looking to you for guidance. In addition to helping the university secure its network, you are required to obtain your CompTIA Security+ certification within 60-days of being hired.
As you will recall, the university leased building in Adelphi, Maryland was designed and implemented via the following layout:
You’ve been asked to perform network security analysis and planning, secure the boundary devices, hosts, and software; and secure the data at rest and in transit. Similar to the Network Design Proposal in CMIT 265, your deliverable should explain the requirement, propose a solution, and justify the solution. You should make use of the TestOut LabSim material to create the task, and study for CompTIA Security+ certification. You should also make use of other sources as required. It is important that your deliverable explain the technical issues in layman’s terms. Before you begin, make sure to review the Network Security Proposal (Parts 1-3).
III. Securing Data at Rest and in Transit
A. Public Key Infrastructure
Requirements
In the requirements section, students will make explicit UMUC’s requirements for remote access and authentication. Given this section requires information related to public key infrastructure, students should review TestOut LabSim section 3 (Cryptography), and use additional resources as necessary.
Proposed Solutions
In the proposed solution section, students will provide details of the proposed solution, based on the technical requirements and assumptions. Student should be specific and use additional resources as necessary. Given this section requires us to understand public key infrastructure, students should review TestOut LabSim section 3 (Cryptography), and use additional resources as necessary.
Justification
This section should be used to justify your proposed solution based on the requirement(s). That is, you are explaining why you proposed the solution in the aforementioned paragraph, based on the requirement you made explicit in aforementioned paragraph. Each section should allow the reader to proceed from requirement, to solution, to justification. Given this section requires us to understand public key infrastructure, students should review TestOut LabSim section 3 (Cryptography), and use additional resources as necessary.
B. Secure Protocol Implementation
Requirements
In the requirements section, students will make explicit UMUC’s requirements for remote access and authentication. Given this section requires information related to secure protocol implementation, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Proposed Solutions
In the proposed solution section, students will provide details of the proposed solution, based on the technical requirements and assumptions. Student should be specific and use additional resources as necessary. Given this section requires us to understand secure protocol implementation, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Justification
This section should be used to justify your proposed solution based on the requirement(s). That is, you are explaining why you proposed the solution in the aforementioned paragraph, based on the requirement you made explicit in aforementioned paragraph. Each section should allow the reader to proceed from requirement, to solution, to justification. Given this section requires us to understand secure protocol implementation, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
C. File Encryption
Requirements
In the requirements section, students will make explicit UMUC’s requirements for remote access and authentication. Given this section requires information related to file encryption, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Proposed Solutions
In the proposed solution section, students will provide details of the proposed solution, based on the technical requirements and assumptions. Student should be specific and use additional resources as necessary. Given this section requires us to understand file encryption, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Justification
This section should be used to justify your proposed solution based on the requirement(s). That is, you are explaining why you proposed the solution in the aforementioned paragraph, based on the requirement you made explicit in aforementioned paragraph. Each section should allow the reader to proceed from requirement, to solution, to justification. Given this section requires us to understand file encryption, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
D. Hashing
Requirements
In the requirements section, students will make explicit UMUC’s requirements for remote access and authentication. Given this section requires information related to hashing, students should review TestOut LabSim section 3 (Cryptography), and use additional resources as necessary.
Proposed Solutions
In the proposed solution section, students will provide details of the proposed solution, based on the technical requirements and assumptions. Student should be specific and use additional resources as necessary. Given this section requires us to understand hashing, students should review TestOut LabSim section 3 (Cryptography), and use additional resources as necessary.
Justification
This section should be used to justify your proposed solution based on the requirement(s). That is, you are explaining why you proposed the solution in the aforementioned paragraph, based on the requirement you made explicit in aforementioned paragraph. Each section should allow the reader to proceed from requirement, to solution, to justification. Given this section requires us to understand hashing, students should review TestOut LabSim section 3 (Cryptography), and use additional resources as necessary.
E. Backup and Restore
Requirements
In the requirements section, students will make explicit UMUC’s requirements for remote access and authentication. Given this section requires information related to backup and restoration, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Proposed Solutions
In the proposed solution section, students will provide details of the proposed solution, based on the technical requirements and assumptions. Student should be specific and use additional resources as necessary. Given this section requires us to understand backup and restoration, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Justification
This section should be used to justify your proposed solution based on the requirement(s). That is, you are explaining why you proposed the solution in the aforementioned paragraph, based on the requirement you made explicit in aforementioned paragraph. Each section should allow the reader to proceed from requirement, to solution, to justification. Given this section requires us to understand backup and restoration, students should review TestOut LabSim section 10 (Data Defenses), and use additional resources as necessary.
Rubric Name: Network Security Proposal Part 3
|
|
|
|
|
|
|
|
Criteria |
|
|
|
|
|
|
|
Provided an excellent description of the technical requirements, proposal, and justification for public key infrastructure (PKI).
|
Provided an outstanding description of the technical requirements, proposal, and justification for public key infrastructure (PKI).
|
Provided a description of the technical requirements, proposal, and justification for public key infrastructure (PKI).
|
Provided a description of the technical requirements and proposal for public key infrastructure (PKI), but lacked an appropriate justification.
|
Identified technical requirements for public key infrastructure (PKI), but the proposal and justification lacked detail and/or was not well supported.
|
The technical requirements, proposal, and justification for public key infrastructure (PKI) were off topic or failed to provide required level of detail.
|
|
Provided an excellent description of the technical requirements, proposal, and justification for the secure protocol implementation.
|
Provided an outstanding description of the technical requirements, proposal, and justification for the secure protocol implementation.
|
Provided a description of the technical requirements, proposal, and justification for the secure protocol implementation.
|
Provided a description of the technical requirements and proposal for the secure protocol implementation, but lacked an appropriate justification.
|
Identified a technical requirement for the secure protocol implementation, but the proposal and justification lacked detail and/or was not well supported.
|
The technical requirements, proposal, and justification for the secure protocol implementation were off topic or failed to provide required level of detail.
|
|
Provided an excellent description of the technical requirements, proposal, and justification for file encryption.
|
Provided an outstanding description of the technical requirements, proposal, and justification for file encryption.
|
Provided a description of the technical requirements, proposal, and justification for file encryption.
|
Provided a description of the technical requirements and proposal for file encryption, but lacked an appropriate justification.
|
Identified a technical requirement for file encryption, but the proposal and justification lacked detail and/or was not well supported.
|
The technical requirements, proposal, and justification for file encryption were off topic or failed to provide required level of detail.
|
|
Provided an excellent description of the technical requirements, proposal, and justification for the hashing method.
|
Provided an outstanding description of the technical requirements, proposal, and justification for the hashing method.
|
Provided a description of the technical requirements, proposal, and justification for the hashing method.
|
Provided a description of the technical requirements and proposal for the hashing method, but lacked an appropriate justification.
|
Identified a technical requirement, but the proposal and justification for the hashing method lacked detail and/or was not well supported.
|
The technical requirements, proposal, and justification for the hashing method were off topic or failed to provide required level of detail.
|
|
Provided an excellent description of the technical requirements, proposal, and justification for the backup and restoration system and processes.
|
Provided an outstanding description of the technical requirements, proposal, and justification for the backup and restoration system and processes.
|
Provided a description of the technical requirements, proposal, and justification for the backup and restoration system and processes.
|
Provided a description of the technical requirements and proposal for the backup and restoration system and processes, but lacked an appropriate justification.
|
Identified a technical requirement for the backup and restoration system and processes, but the proposal and justification lacked detail and/or was not well supported.
|
The technical requirements, proposal, and justification for the backup and restoration system and processes were off topic or failed to provide required level of detail.
|
|
Work contains a reference list containing entries for all cited sources. Reference list entries and in-text citations are correctly formatted using the appropriate IEEE style for each type of resource. The description appropriately used information from 5 or more authoritative sources, i.e. journal articles, industry or trade publications, news articles, industry or government white papers and authoritative Web sites.
|
Work contains a reference list containing entries for all cited sources. One or two minor errors in IEEE format for in-text citations and/or reference list entries. The description appropriately used information from 4 or more authoritative sources, i.e. journal articles, industry or trade publications, news articles, industry or government white papers and authoritative Web sites.
|
Work contains a reference list containing entries for all cited sources. No more than 5 minor errors in IEEE format for in-text citations and/or reference list entries. The description appropriately used information from 3 or more authoritative sources, i.e. journal articles, industry or trade publications, news articles, industry or government white papers and authoritative Web sites.
|
Work contains a reference list containing entries for cited sources. Work contains no more than 5 minor errors in IEEE format for in-text citations and/or reference list entries. The description appropriately used information from 2 or more authoritative sources, i.e. journal articles, industry or trade publications, news articles, industry or government white papers and authoritative Web sites.
|
Work attempts to credit sources but demonstrates a fundamental failure to understand and apply the IEEE formatting standard.
The description appropriately used information from 1 or more authoritative sources, i.e. journal articles, industry or trade publications, news articles, industry or government white papers and authoritative Web sites.
|
Reference list is missing. Work demonstrates an overall failure to incorporate and/or credit authoritative sources for information used in the paper.
|
|
No formatting, grammar, spelling, or punctuation errors.
|
Work contains minor errors in formatting, grammar, spelling or punctuation which do not significantly impact professional appearance.
|
Errors in formatting, spelling, grammar, or punctuation which detract from professional appearance of the submitted work.
|
Submitted work has numerous errors in formatting, spelling, grammar, or punctuation. Work is unprofessional in appearance.
|
Submitted work is difficult to read / understand and has significant errors in formatting, spelling, grammar, punctuation, or word usage.
|
No work submitted for this assignment.
|
|