The document provides instructions for developing a high-level implementation plan to address vulnerabilities and convergence issues identified in a recommendation memo and network diagram. The plan should include all system development life cycle gates and tasks, describe the implementation solution while relating it to confidentiality, integrity and availability, and incorporate people, processes, and technology. A template is provided that requires an introduction, goals and objectives, scope, projected expenses, assumptions, constraints, and a minimum 5-page paper in APA format with 5 references.

1. Using the recommendation memo and network diagram, develop
a high-level plan for implementing the changes and mitigating
vulnerabilities and convergence issues. The high-level plan
should include all the system development life cycle (SDLC)
gates/decision points and all relevant tasks. Describe and relate
the implementation solution to CIA and incorporate, people,
processes and technology to this plan.
This is a combination of a paper and a detailed list of steps and
resources that you would follow to implement and complete this
project. Think about all of the actions, resources, and tasks that
you would need in order to effect a successful implementation.
These should also be included as part of the plan. The instructor
may provide a template to use with this assignment. The
minimum structure for this assignment is below:
INTRODUCTION
Purpose of Plan
GOALS AND OBJECTIVES
Business Goals and Objectives
Project Goals and Objectives
SCOPE
Scope Definition
Items Beyond Scope
PROJECTED EXPENSES
System Development Life Cycle/Schedule
Milestones
ASSUMPTIONS
Project Assumptions
CONSTRAINTS
Project Constraints
Critical Project Barriers
The Plan will be a minimum 5 page, double-spaced paper using
Times New Roman 12 font and APA style formatting for
citations and references. It will also include a minimum of 5
references. The Title/Cover page, illustrations

2. (tables/charts/graphs), network diagram, and references are not
part of the page count but are required for the assignment. The
grading rubric provides additional details as to what should be
included in the paper. Your instructor may provide an APA
style template to use for this paper.
*** Make sure that you include in detail the steps you would
take to secure the project.
Expertly defines goals and objectives
identifies goals and objectives in a manner that reflects a
general understanding of overall effort
identifies goals and objectives in a manner that reflects a basic
understanding of overall effort
identifies goals and objectives in a manner where some aspects
are missing or incomplete.
does not identify goals and objectives in a manner that reflects a
general understanding of overall effort.
Clearly describes and relates information security and other
technology issues. Synthesizes and applies material and
document relationships.
Basically describes and relates information security and other
technology issues. Synthesizes and applies some material and
document relationships.
Weakly describes and relates information security and other
technology issues. Some synthesizing and application or applies
material and document relationships.
Little description and relating information security and other
technology issues. Little synthesizing or application of material
and document relationships.
No description or relationship of information security or other
technology issues. Doesn’t synthesize or apply material and
document relationships.
Project Expenses
Clearly identifies and articulates the cost of overall security
solution.

3. Basically identifies and articulates the cost of overall security
solution.
Weakly identifies and articulates the cost of overall security
solution.
Little identification or articulation of the costs regarding
technology solution. May not link any costs to technologies
identified.
No identification or articulation of the costs regarding
technology solution. No link of any costs to technologies
identified.
Synthesizes and applies logical SDLC processes and schedule to
overall solution deployment.
Basically Synthesizes and applies logical SDLC processes and
schedule to overall solution deployment.
Weakly Synthesizes and applies logical SDLC processes and
schedule to overall solution deployment.
Little synthesis or application of logical SDLC processes and
schedule to overall solution deployment.
No synthesis or application of logical SDLC processes and
schedule to overall solution deployment.
Solution
Diagram and Illustration
Network diagram and accompanying illustration are strongly
linked to proposed solution and content
Network diagram and accompanying illustration are generally
linked to proposed solution and content
Network diagram and accompanying illustration are weakly
linked to proposed solution and content

4. Network diagram and accompanying illustration are haphazardly
linked to proposed solution and content
Network diagram and accompanying illustration are not linked
to proposed solution and content
Security Strategy
Each defined milestone is directly related to overall
strategy/solution and clearly mitigates the risk or issue.
Most milestones are related to overall strategy/solution and
clearly mitigates the risk or issue.
Milestones are weakly related to overall strategy/solution and
clearly mitigates the risk or issue.
Milestone are haphazardly related to overall strategy/solution
and clearly mitigates the risk or issue.
No milestones are directly related to overall strategy/solution
and clearly mitigates the risk or issue.
Clearly identifies security solutions and assumptions that
consist of people, processes and technologies that relate to the
risks. Covers all three requirements.
Basically identifies security solutions and assumptions that
consist of people, processes and technologies that relate to the
risks. Covers at least two of the three requirements.
Weakly identifies security solutions and assumptions that
consist of people, processes and technologies that relate to the
risks. Covers at least one of the requirements.
Little identification of security solutions and assumptions that

5. consist of people, processes or technologies that relate to the
risks. May not cover one of the requirements.
Doesn’t identify security solutions or assumptions that consist
of people, processes or technologies that relate to the risks.
Doesn’t cover any of the three requirements.
Clearly describes the linkage and constraints associated with
solution
Basically describes the linkage and constraints associated with
solution
Weakly describes the linkage and constraints associated with
solution
Little description of the linkage and constraints associated with
solution
No description of any linkage or constraints associated with
solution
Timeline
Clear and detailed SDLC tasks that logically leads to the
proposed solutions
Basic SDLC tasks are provided that generally lead or infer how
the proposed solution will be realized
Weak and poorly detailed SDLC tasks are provided that
minimally lead or infer how the proposed solution will be
realized
Haphazard and poorly detailed SDLC tasks that minimally lead
or infer how the proposed solution will be realized

6. No SDLC tasks are provided that lead or infer how the proposed
solution will be realized
No clear and defined tasks for each solution.
Major tasks are clearly prioritized according their importance to
mitigating the risks and issues found.
Major tasks basically prioritized according their importance to
mitigating the risks or issues found.
Major tasks weakly prioritized according their importance to
mitigating the risks and issues found.
Few tasks prioritized according their importance to mitigating
the risks or issues found.
No tasks prioritized according their importance to mitigating
the risks or issues found.
Clearly defined people resources (by type) that support each
task in the timeline.
Basically defined people resources (by type) that support each
task in the timeline.
Weakly defined people resources (by type) that support each
task in the timeline.
Little defined people resources (by type) that support each task
in the timeline.
No defined people resources (by type) that support each task in
the timeline.
Finds and Applies Knowledge
Used at least 5 authoritative or scholarly sources in paper. No

7. APA style errors in sources.
Used at least 3 authoritative or scholarly sources in paper. No
more than 1 APA errors in sources.
Used at least 2 authoritative or scholarly sources in paper. No
more than 2 APA errors in sources.
May have used 1 authoritative or scholarly source in paper. May
not have used APA style formatting.
No authoritative or scholarly sources used in paper.
All sources cited. No errors in citing material in paper.
All but 1 source cited. Had no more than 5 citing errors in
paper.
All but 2 sources cited. Had no more than 10 citing errors in
paper.
All but 3 sources cited. Had less than 15 APA citing errors in
paper.
No sources cited or had more than 15 APA citing errors in
paper.
Organization, Execution and Appearance
Prepared MS Word document, used consistent formatting,
section subheadings, submitted one file, used instructor
provided template, correct coversheet and separate reference
page and meets minimum page count of 5 pages.
MS Word document didn’t follow up to two (2) of the
following: used consistent formatting, section subheadings,
submitted one file, used instructor provided template, correct

8. coversheet and separate reference page and meets minimum
page count of 5 pages.
MS Word document didn’t follow up to four (4) of the
following: used consistent formatting, section subheadings,
submitted one file, used instructor provided template, correct
coversheet and separate reference page and meets minimum
page count of 5 pages.
MS Word document followed only one (1) of the following:
used consistent formatting, section subheadings, submitted one
file, used instructor provided template, correct coversheet and
separate reference page and meets minimum page count of 5
pages.
Non MS Word document didn’t any of the following: used
consistent formatting, section subheadings, submitted one file,
used instructor provided template, correct coversheet and
separate reference page and meets minimum page count of 5
pages.
No grammar errors, use of first/second person, spelling or
punctuation errors.
Less than 5 grammar errors, use of first/second person, spelling
or punctuation errors.
Less than 10 grammar errors, use of first/second person,
spelling or punctuation errors.
Less than 15 grammar errors, use of first/second person,
spelling or punctuation errors.

9. More than 15 grammar errors, use of first/second person,
spelling or punctuation errors.
Overall Score