Help writing a Cyber Security (Secure Network Design) Paper - 23/06/2024 18:13 EDT
Budget: $30 – $250 USD
SEE RESOURCES & LINKS BELOW ( In order to complete)
- I can send you better screenshots of whats required if you ACCEPT this project
RUBERIC:
A:BUSINESS REQUIREMENTS
NOT EVIDENT
A description of the current network security problems and infrastructure problems for each company is not provided.
APPROACHING COMPETENCE
The submission describes one or more current network security problems and one or more current infrastructure problems for each company, but the description is not in alignment with the given scenario or contains inaccuracies.
COMPETENT
The submission accurately describes 2 or more current network security problems and at 2 or more current infrastructure problems for each company and is aligned with the business requirements given in the scenario.
B1:VULNERABILITIES
NOT EVIDENT
A description of 2 existing vulnerabilities for each company is not provided.
APPROACHING COMPETENCE
The submission describes 1 or more existing vulnerabilities for each company, but 1 or more of the vulnerabilities described are not in alignment with the given network diagram and vulnerability scan or contain inaccuracies.
COMPETENT
The submission accurately describes 2 or more existing vulnerabilities for each company. The vulnerabilities described are in alignment with the given network diagram and vulnerability scan.
B2:IMPACT, RISK, LIKELIHOOD
NOT EVIDENT
An explanation of the impact, risk, and likelihood associated with each described vulnerability from B1 is not provided.
APPROACHING COMPETENCE
The submission explains the impact, risk, or likelihood associated with each described vulnerability from part B1 but does not explain all three concepts for each vulnerability, or the explanation is not in alignment with the given network diagram or vulnerability scan, or the explanation is incomplete.
COMPETENT
The submission explains the impact, risk, and likelihood associated with each described vulnerability from part B1 as it relates to each company. The explanation is complete and in alignment with the given network diagram and vulnerability scan.
C:TOPOLOGY DIAGRAM
NOT EVIDENT
A network topology diagram is not provided.
APPROACHING COMPETENCE
The network topology diagram is provided, but the diagram lacks details of the proposed merged network requirements, or the diagram does not meet the needs provided in the scenario or is incomplete.
COMPETENT
The network topology diagram with the details of the proposed merged network requirements is provided. The diagram is complete and meets the needs provided in the scenario.
D:TOPOLOGY COMPONENTS
NOT EVIDENT
The components of the network topology diagram are not identified.
APPROACHING COMPETENCE
The submission identifies some but not all of the components in the network topology diagram or does not identify some of the OSI or the TCP/IP protocol stack layers. Or the OSI or the TCP/IP layers are not correctly identified.
COMPETENT
The submission correctly identifies the layer for all components in the topology diagram referencing the layers of the OSI and TCP/IP protocol stack.
E:RATIONALE
NOT EVIDENT
An explanation for the rationale for adding or deleting network components is not provided.
APPROACHING COMPETENCE
The submission explains the rationale for adding, deleting, or repurposing network components in the newly merged network topology diagram but does not include the details of how each component addresses budgetary constraints, or the explanation is not in alignment with the given scenario, or the explanation contains inaccuracies.
COMPETENT
The submission explains the rationale for adding, deleting, or repurposing network components in the newly merged network topology diagram and includes the details of how each component addresses budgetary constraints. The explanation is in alignment with the given scenario.
F:SECURE NETWORK DESIGN PRINCIPLES
NOT EVIDENT
An explanation of the secure network design principles is not provided.
APPROACHING COMPETENCE
The submission explains 1 network design principle that is used in the proposed network topology diagram, or the explanation explains 2 or more secure network design principles but does not clearly name the design principle being used, or the design principle is not in alignment with the proposed network topology diagram.
COMPETENT
The submission explains 2 or more secure network design principles that are used in the proposed network topology diagram. The explanation clearly names the secure network design principles being used and how each principle aligns with the proposed network topology diagram.
G:REGULATORY COMPLIANCE
NOT EVIDENT
An explanation of how the proposed merged network topology diagram addresses regulatory compliance requirements is not provided.
APPROACHING COMPETENCE
The submission explains how the proposed merged network topology diagram addresses 1 regulatory compliance requirement or explains 2 or more regulatory compliance requirements, but the explanation does not include all of the listed components, or the requirements are not relevant to the newly merged company, or the explanation contains inaccuracies.
COMPETENT
The submission accurately explains how the proposed merged network topology diagram addresses 2 or more regulatory compliance requirements and includes all of the listed components. The regulatory compliance requirements are relevant to the newly merged company.
H:EMERGING THREATS
NOT EVIDENT
A description of the emerging threats that are applicable to the merged organization is not provided.
APPROACHING COMPETENCE
The submission describes 1 or more emerging threats to the newly merged organization, but the description does not include all of the given points, or the described emerging threats are not applicable to the newly merged company, or the description contains inaccuracies.
COMPETENT
The submission accurately describes 2 or more emerging threats that are applicable to the newly merged organization and includes all the given points.
I:SUMMARY RECOMMENDATIONS
NOT EVIDENT
A summary of recommendations for implementation of the proposed merged network is not provided.
APPROACHING COMPETENCE
The submission summarizes the recommendations for implementation of the proposed merged network, but the recommendations are not in alignment with the scenario and budgetary requirements, or the summary does not include all listed specifications, or the recommendations are illogical based on the given scenario.
COMPETENT
The submission summarizes the recommendations for implementation of the proposed merged network. The summary is logical and in alignment with the scenario and budgetary requirements and includes all listed specifications.
J: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.
K:PROFESSIONAL COMMUNICATION
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.
SUPPORTING DOCUMENTS:
- Company A Network Diagram.docx
file:///C:/Users/Owner/Downloads/Company%20A%20Network%20Diagram.pdf
- Company B Network Diagram.docx
file:///C:/Users/Owner/Downloads/Company%20B%20Network%20Diagram.pdf
- Company B Vulnerability Report and Cybersecurity Tools
https://docs.google.com/document/d/1M4uh1pa9U6PXz3_P2Ldf8ifFy04DQHBQJWzjNia5FlU/edit?usp=sharing
- Company A Risk Analysis
https://docs.google.com/document/d/1c3Gu91SnBSedD4sWA2HFbN9c7BpolEz_ra8wy2P379w/edit?usp=sharing
- I can send you better screenshots of whats required if you ACCEPT this project
RUBERIC:
A:BUSINESS REQUIREMENTS
NOT EVIDENT
A description of the current network security problems and infrastructure problems for each company is not provided.
APPROACHING COMPETENCE
The submission describes one or more current network security problems and one or more current infrastructure problems for each company, but the description is not in alignment with the given scenario or contains inaccuracies.
COMPETENT
The submission accurately describes 2 or more current network security problems and at 2 or more current infrastructure problems for each company and is aligned with the business requirements given in the scenario.
B1:VULNERABILITIES
NOT EVIDENT
A description of 2 existing vulnerabilities for each company is not provided.
APPROACHING COMPETENCE
The submission describes 1 or more existing vulnerabilities for each company, but 1 or more of the vulnerabilities described are not in alignment with the given network diagram and vulnerability scan or contain inaccuracies.
COMPETENT
The submission accurately describes 2 or more existing vulnerabilities for each company. The vulnerabilities described are in alignment with the given network diagram and vulnerability scan.
B2:IMPACT, RISK, LIKELIHOOD
NOT EVIDENT
An explanation of the impact, risk, and likelihood associated with each described vulnerability from B1 is not provided.
APPROACHING COMPETENCE
The submission explains the impact, risk, or likelihood associated with each described vulnerability from part B1 but does not explain all three concepts for each vulnerability, or the explanation is not in alignment with the given network diagram or vulnerability scan, or the explanation is incomplete.
COMPETENT
The submission explains the impact, risk, and likelihood associated with each described vulnerability from part B1 as it relates to each company. The explanation is complete and in alignment with the given network diagram and vulnerability scan.
C:TOPOLOGY DIAGRAM
NOT EVIDENT
A network topology diagram is not provided.
APPROACHING COMPETENCE
The network topology diagram is provided, but the diagram lacks details of the proposed merged network requirements, or the diagram does not meet the needs provided in the scenario or is incomplete.
COMPETENT
The network topology diagram with the details of the proposed merged network requirements is provided. The diagram is complete and meets the needs provided in the scenario.
D:TOPOLOGY COMPONENTS
NOT EVIDENT
The components of the network topology diagram are not identified.
APPROACHING COMPETENCE
The submission identifies some but not all of the components in the network topology diagram or does not identify some of the OSI or the TCP/IP protocol stack layers. Or the OSI or the TCP/IP layers are not correctly identified.
COMPETENT
The submission correctly identifies the layer for all components in the topology diagram referencing the layers of the OSI and TCP/IP protocol stack.
E:RATIONALE
NOT EVIDENT
An explanation for the rationale for adding or deleting network components is not provided.
APPROACHING COMPETENCE
The submission explains the rationale for adding, deleting, or repurposing network components in the newly merged network topology diagram but does not include the details of how each component addresses budgetary constraints, or the explanation is not in alignment with the given scenario, or the explanation contains inaccuracies.
COMPETENT
The submission explains the rationale for adding, deleting, or repurposing network components in the newly merged network topology diagram and includes the details of how each component addresses budgetary constraints. The explanation is in alignment with the given scenario.
F:SECURE NETWORK DESIGN PRINCIPLES
NOT EVIDENT
An explanation of the secure network design principles is not provided.
APPROACHING COMPETENCE
The submission explains 1 network design principle that is used in the proposed network topology diagram, or the explanation explains 2 or more secure network design principles but does not clearly name the design principle being used, or the design principle is not in alignment with the proposed network topology diagram.
COMPETENT
The submission explains 2 or more secure network design principles that are used in the proposed network topology diagram. The explanation clearly names the secure network design principles being used and how each principle aligns with the proposed network topology diagram.
G:REGULATORY COMPLIANCE
NOT EVIDENT
An explanation of how the proposed merged network topology diagram addresses regulatory compliance requirements is not provided.
APPROACHING COMPETENCE
The submission explains how the proposed merged network topology diagram addresses 1 regulatory compliance requirement or explains 2 or more regulatory compliance requirements, but the explanation does not include all of the listed components, or the requirements are not relevant to the newly merged company, or the explanation contains inaccuracies.
COMPETENT
The submission accurately explains how the proposed merged network topology diagram addresses 2 or more regulatory compliance requirements and includes all of the listed components. The regulatory compliance requirements are relevant to the newly merged company.
H:EMERGING THREATS
NOT EVIDENT
A description of the emerging threats that are applicable to the merged organization is not provided.
APPROACHING COMPETENCE
The submission describes 1 or more emerging threats to the newly merged organization, but the description does not include all of the given points, or the described emerging threats are not applicable to the newly merged company, or the description contains inaccuracies.
COMPETENT
The submission accurately describes 2 or more emerging threats that are applicable to the newly merged organization and includes all the given points.
I:SUMMARY RECOMMENDATIONS
NOT EVIDENT
A summary of recommendations for implementation of the proposed merged network is not provided.
APPROACHING COMPETENCE
The submission summarizes the recommendations for implementation of the proposed merged network, but the recommendations are not in alignment with the scenario and budgetary requirements, or the summary does not include all listed specifications, or the recommendations are illogical based on the given scenario.
COMPETENT
The submission summarizes the recommendations for implementation of the proposed merged network. The summary is logical and in alignment with the scenario and budgetary requirements and includes all listed specifications.
J: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.
K:PROFESSIONAL COMMUNICATION
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.
SUPPORTING DOCUMENTS:
- Company A Network Diagram.docx
file:///C:/Users/Owner/Downloads/Company%20A%20Network%20Diagram.pdf
- Company B Network Diagram.docx
file:///C:/Users/Owner/Downloads/Company%20B%20Network%20Diagram.pdf
- Company B Vulnerability Report and Cybersecurity Tools
https://docs.google.com/document/d/1M4uh1pa9U6PXz3_P2Ldf8ifFy04DQHBQJWzjNia5FlU/edit?usp=sharing
- Company A Risk Analysis
https://docs.google.com/document/d/1c3Gu91SnBSedD4sWA2HFbN9c7BpolEz_ra8wy2P379w/edit?usp=sharing