Secure network design is a critical component
Need only quality work and. IT has to be done exactly in the same
sequence as asked below and all the requirements have to be followed (make sure
u do not miss out on anything).
INTRODUCTION
Secure network design is a critical
component for protecting resources, processes, and business continuity.
Effective network design involves evaluating existing network problems and
potential threats, considering secure architectures based on industry best
practices and secure design principles, and proposing secure network design
solutions that address the business needs of the organization.
For this task, you will access the “Performance Assessment Lab Area” within the
course to run Zenmap and OpenVAS. Screenshots saved for submission must include
your name and student ID. Your final network drawing should be saved in *.vsd
format using Microsoft Visio or a similar software tool.
SCENARIO
Company A is a property and casualty
insurer underwriting multiple types of insurance. Company A is acquiring
Company B, a financial services organization, in order to diversify and
increase market share. Company B conducts business in the same geographical
area as Company A and delivers business and individual financial planning
services. Both companies provide services from their respective offices and at
the customer’s site. Both companies use broadband connectivity.
You are the IT director for Company A and will be the chief information officer
(CIO) for the merged organization. You are tasked with analyzing, designing,
and presenting the proposed IT integration project. Company A has clear IT
infrastructure documentation, including a logical diagram, an organizational
chart, and a recent security risk analysis. Company B does not have any IT
infrastructure documentation, and several security and integration issues are
evident. Company B outsources any IT-related needs to a consultant. Leadership
for the merged organization has allocated a limited budget of $35,000 for this
project and will expect justification for recommended expenditures.
Integration project requirements include following secure network design
principles, selecting or repurposing secure network components, assuring secure
communication channels, addressing relevant regulatory compliance, minimizing
potential network problems and security threats, delivering integration cost
savings, and aligning IT to meet the business needs of the post-merger
organization. This post-merger organization will reflect one corporate office
and a branch office.
REQUIREMENTS
Your submission must be your original
work. No more than a combined total of 30% of the submission and no more than a
10% match to any one individual source can be directly quoted or closely
paraphrased from sources, even if cited correctly. The originality report that
is provided when you submit your task can be used as a guide.
You must use the rubric to direct the
creation of your submission because it provides detailed criteria that will be
used to evaluate your work. Each requirement below may be evaluated by more
than one rubric aspect. The rubric aspect titles may contain hyperlinks to
relevant portions of the course.
Tasks may not be
submitted as cloud links, such as links to Google Docs, Google Slides,
OneDrive, etc., unless specified in the task requirements. All other
submissions must be file types that are uploaded and submitted as attachments
(e.g., .docx, .pdf, .ppt).
A. Describe the problems Company A has with network security and
infrastructure using details from one or more of the “Company A Organizational
Chart,” “Company A Risk Analysis,” and “Company A Visio Diagram” supporting
documents.
B. Run Zenmap and OpenVAS on Company B’s network using the
“Performance Assessment Lab Area” web link. Your submission should include the
following documents:
• a screenshot of the completed Zenmap scan—should be taken within
the lab environment and should include your name
• a screenshot of the OpenVAS report result—should be taken within
the lab environment and should include your name
• the completed Zenmap PDF file
• the completed OpenVAS PDF file—should include your name in the
summary of the report
Note: This assessment requires you to submit pictures, graphics, and/or
diagrams. Each file must be a supporting document no larger than 30 MB in size.
Diagrams must be original and may be hand-drawn or drawn using a graphics
program. Do not use CAD programs because the file will be too large.
C. Describe the potential impact of two network
security or infrastructure problems of Company B using details from the outputs
of Zenmap and OpenVas, including rationale for each problem.
1. Explain how correcting each of these problems
will improve the functioning of the merged network.
D. Provide a network topology diagram using Microsoft Visio or a
similar software tool that represents the proposed merging requirements from
the scenario of Company A and Company B, including remediation of all existing
infrastructure problems described in part A and part C.
E. Identify which layer of the OSI model and layer of the TCP/IP
protocol stack apply to each component in the merged network
topology diagram.
F. Justify the retention or deletion of four existing
components as suggested in your proposed network topology diagram. Include
how each component’s retention or deletion and any newly
required additions to the network address both security
concerns and budgetary restrictions found in the scenario.
G. Explain how two secure network design
principles are included in your proposed merged network topology diagram.
H. Describe two secure hardware and/or software
components integrated into the proposed network topology and how each component
will address the security needs of the merged organization.
I. Explain how the proposed network topology diagram for the
merged organization addresses security safeguards based on a regulatory
compliance requirement.
J. Explain a security threat and one potential network problem
that would become a risk as part of the implementation of the proposed network topology
diagram, including why each would become a risk.
1. Explain how the security threat and potential network problem
should each be managed or mitigated as part of the
implementation of the proposed topology diagram.
K. Acknowledge sources, using in-text citations and references,
for content that is quoted, paraphrased, or summarized.
L. Demonstrate professional communication in the content and
presentation of your submission.
File Restrictions
File name may contain only letters,
numbers, spaces, and these symbols: ! - _ . * ' ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt,
pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg,
tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z
RUBRIC
A:COMPANY A’S NETWORK PROBLEMS
|
NOT
EVIDENT The
submission does not describe the network security and infrastructure problems
of Company A. |
APPROACHING
COMPETENCE The
submission describes network security and infrastructure problems of Company
A, but the submission is not accurate or does not use appropriate details
from 1 or more of the “Company A Organizational Chart,” “Company A Risk
Analysis,” and “Company A Visio Diagram.” |
COMPETENT The
submission accurately describes Company A’s security and infrastructure
problems. The submission includes appropriate details of the network security
and infrastructure problems found in the attached “Company A Organizational
Chart,” “Company A Risk Analysis,” and/or “Company A Visio Diagram.” |
B:ZENMAP AND OPENVAS
|
NOT
EVIDENT The
given documents from both ZenMap and OpenVAS are not
provided. |
APPROACHING
COMPETENCE The
given documents for both Zenmap and OpenVAS are provided,
but 1 or more of the document specifications is incomplete or inaccurate. |
COMPETENT The
given documents for both Zenmap and OpenVAS are provided,
including all given specifications. |
C:COMPANY B’S NETWORK PROBLEMS
|
NOT
EVIDENT A description
of 2 of Company B’s network security or infrastructure problems and the
impact of each problem is not provided. |
APPROACHING
COMPETENCE The
description of 2 of Company B’s network security or infrastructure problems
and the impact of each problem does not include logical
rationale for why 1 or more of the 2 problems is a network security or
infrastructure problem for Company B, or the description does not use
appropriate details from the Zenmap and OpenVAS outputs. |
COMPETENT The
description accurately identifies 2 of Company B’s network security or
infrastructure problems and the impact of each problem,
including logical rationale for why each is a network
security or infrastructure problem using appropriate details from the Zenmap
and OpenVAS outputs. |
C1:CORRECTING PROBLEMS AND IMPROVEMENT
|
NOT
EVIDENT The
submission does not explain the potential positive effect(s) caused by the
correction of each problem in part C. |
APPROACHING
COMPETENCE The
submission does not logically or accurately explain the potential positive
effect(s) of correcting 1 or more of the problems in part C for the
functioning of the merged network. |
COMPETENT The
submission logically and accurately explains the potential positive effect(s)
of correcting each of the problems in part C for the
functioning of the merged network. |
D:MERGED NETWORK TOPOLOGY
|
A merged network topology diagram using Microsoft
Visio or a similar software tool is not provided. |
APPROACHING COMPETENCE The merged network topology diagram using Microsoft
Visio or a similar software tool is not accurate or does not represent the
merging requirements from the scenario. Or the merged network topology
diagram does not remediate all existing infrastructure
issues described in part A and part C. |
COMPETENT The merged network topology diagram using
Microsoft Visio or a similar software tool is accurate, represents the
merging requirements from the scenario, and remediates all existing
infrastructure issues described in part A and part C. |
E:OSI MODEL AND TCP/IP PROTOCOL STACK
LAYERS
|
NOT
EVIDENT The
submission does not identify the OSI model layer and TCP/IP protocol stack
layer for each component in the merged network topology
diagram. |
APPROACHING
COMPETENCE The
submission inaccurately identifies the OSI model layer or TCP/IP protocol
stack layer for each component in the merged network
topology diagram. |
COMPETENT The
submission accurately identifies the OSI model layer and TCP/IP protocol
stack layer for each component in the merged network
topology diagram. |
F:JUSTIFICATION OF MERGED NETWORK
TOPOLOGY
|
NOT
EVIDENT A
justification of retention or deletion of 4 existing components is not
provided. |
APPROACHING
COMPETENCE The
justification of retaining or deleting 4 existing components does not
accurately and logically discuss the retention or deletion of 4 existing
components reflected in the candidate’s proposed network topology diagram. Or
the justification does not logically explain how each component’s
retention or deletion, including any newly required additions to the network
as a result of a deletion, addresses both the relevant
security concerns and budgetary restrictions found in the scenario. |
COMPETENT The
justification accurately and logically discusses the retention or deletion of
4 existing components reflected in the candidate’s proposed network topology
diagram. The justification logically explains how each component’s
retention or deletion, including any newly required additions to the network
as a result of a deletion, addresses both the relevant
security concerns and budgetary restrictions found in the scenario. |
G:SECURE NETWORK DESIGN PRINCIPLES
|
NOT
EVIDENT An
explanation of 2 secure network design principles is not provided. |
APPROACHING
COMPETENCE The
explanation of 2 secure network design principles contains inaccuracies or
does not logically discuss how each principle is included in
the proposed merged network topology diagram. |
COMPETENT The
explanation accurately identifies 2 secure network design principles and logically
discusses how each principle is included in the proposed
merged network topology diagram. |
H:SECURE HARDWARE/SOFTWARE COMPONENTS
|
NOT
EVIDENT An
explanation of 2 secure hardware and/or software components is not provided. |
APPROACHING
COMPETENCE The
explanation of 2 secure hardware and/or software components includes 1 or
more components integrated into the proposed network topology diagram, or the
explanation does not logically discuss how each component
will address the security needs of the merged organization. |
COMPETENT The
explanation accurately describes 2 secure hardware and/or software components
that are integrated into the proposed network topology diagram and logically
discusses how each component will address the security needs
of the merged organization. |
I:REGULATORY COMPLIANCE REQUIREMENT
|
NOT
EVIDENT An
explanation of security safeguards based on a regulatory compliance
requirement is not provided. |
APPROACHING
COMPETENCE The
explanation does not accurately identify a relevant regulatory compliance
requirement, or the explanation does not logically discuss how the proposed
network topology diagram for the merged organization addresses security
safeguards based on a regulatory compliance requirement. |
COMPETENT The
explanation accurately identifies a relevant regulatory compliance
requirement and logically discusses how the proposed network topology diagram
for the merged organization addresses security safeguards based on the
identified regulatory compliance requirement. |
J:INTEGRATION PROBLEMS
|
NOT
EVIDENT An
explanation of 1 security threat and 1 potential network problem is not
provided. |
APPROACHING
COMPETENCE The
explanation of 1 security threat and 1 potential network problem does not
accurately describe a security threat and a potential network problem that
would each feasibly become a risk as part of the
implementation of the proposed network topology diagram. Or the explanation
does not logically discuss the risks each would pose,
including logical rationale for why each would become a
risk. |
COMPETENT The
explanation accurately describes 1 security threat and 1 potential network
problem that would become a risk as part of the implementation of the
proposed network topology diagram and logically discusses the risks each would
pose, including a logical rationale for why each would
become a risk. |
J1:MANAGING OR MITIGATING INTEGRATION
PROBLEMS
|
NOT
EVIDENT An
explanation of how to manage or mitigate a security threat or potential
network problem is not provided. |
APPROACHING
COMPETENCE The
submission does not logically explain how both the security
threat and potential network problem from part J should be managed or
mitigated, or a method of management or mitigation proposed is not logical as
part of the implementation of the proposed topology diagram. |
COMPETENT The
submission logically explains how both the security threat
and the potential network problem explained in part J should be managed or
mitigated as part of the implementation of the proposed topology diagram. |
K:SOURCES
|
NOT
EVIDENT The
submission does not include both in-text citations and a reference list for
sources that are quoted, paraphrased, or summarized. |
APPROACHING
COMPETENCE The
submission includes in-text citations for sources that are quoted,
paraphrased, or summarized and a reference list; however, the citations or
reference list is incomplete or inaccurate. |
COMPETENT The
submission includes in-text citations for sources that are properly quoted,
paraphrased, or summarized and a reference list that accurately identifies
the author, date, title, and source location as available. |
|
NOT
EVIDENT Content
is unstructured, is disjointed, or contains pervasive errors in mechanics,
usage, or grammar. Vocabulary or tone is unprofessional or distracts from the
topic. |
APPROACHING
COMPETENCE Content
is poorly organized, is difficult to follow, or contains errors in mechanics,
usage, or grammar that cause confusion. Terminology is misused or
ineffective. |
COMPETENT Content
reflects attention to detail, is organized, and focuses on the main ideas as
prescribed in the task or chosen by the candidate. Terminology is pertinent,
is used correctly, and effectively conveys the intended meaning. Mechanics,
usage, and grammar promote accurate interpretation and understanding. |
USA 
India
Question Attachments
3 attachments —