This is a research proposal paper
Paper Title: Cloud computing challenges in the federal government:
Task: prepare a research proposal paper that discusses the Information Assurance issues associated with the use of CLOUD COMPUTING in the federal government. (The paper/proposal is intended to inform policy-makers at the highest level about the challenges of employing cloud computing.)
Paper should be APA Style 12 Times Romans and should include an
Executive Summary and address all the part below in the table of contents.
1) Assets of Value
This section should specify Assets of Value (sensitive information that is stored, processed, and communicated/transmitted via our information systems and networks AND the components of the infrastructure that would be subjected to the IA analysis). This section should:
• Specify Assets of Value.
• Employ terminology from NSIT terms like Controlled Unclassified Information (CUI) / Sensitive But Unclassified (SBU) and the different types that are included.
• Employ definitions of such terms from credible sources to include US law.
• Discuss other components of the infrastructure which are critical to mission / proposal such that, if vulnerabilities exist, and if they are exploited, would have a detrimental impact on success.
2) Facets / Goals / Services of Information Assurance
This section should subject Assets of Value to critical analysis from the perspective of each of these concepts. Alternatively, since the Cloud will contain sensitive, government information, Confidentiality should be considered. Discussion of these facets of IA should be discussed in real terms, with real information types based on policy.
• Address potential credible Threats poised to exploit Vulnerabilities you plan to discuss. For ex, identity thieves can be a Threat poised to exploit Vulnerability of poor training, and thereby cause a failure of Confidentiality. Notice the chain of logic between the Assets of Value, the Vulnerability, and the Threat, linked to (in this ex) Confidentiality. You should address a variety of credible threat actors (e.g., natural/environmental and human)
• Discuss threat motivation (intent) and capability (knowledge, skills, ability, and access).
• Address Vulnerabilities (or “Weaknesses”) in the system. These will include People, Process, and Technology (PPT) vulnerabilities. For ex, weak encryption will be an ex of a Technology Vulnerability, whereas poor training of authorized users will be an ex of a People Vulnerability.
• Vulnerabilities discussed MUST have substantive evidence / reference citation and critical analysis to support any claims.
• Vulnerabilities discussed MUST apply specifically to your technology of choice. For ex, while items such as poor training are fine, you would want to seek out those vulnerabilities which are especially important / specific to your technology.
(a) Identify and list at least two (2) specific People, Process, AND Technology vulnerabilities.
A minimum of six (6) vulnerabilities are required.
(b) Within each subsection, include citation per APA to the specific references which support this selection. Make sure that specific page numbers are included.
Identified vulnerabilities must be supported by at least two (2) references.
• Address Impact (or “Consequence”) that will result if the stated Threat were to exploit the stated Vulnerability. For ex, there can be serious health consequences, might be death, to a victim if a hacker changed a person’s medical information on the RFID. Similarly, sensitive military information might be disclosed if someone hacked into the Cloud.
• Be certain to discuss impact in terms of mission and resources (human and non-human). See various publications (e.g., NIST FIPS 199) that could assist you in providing criteria (e.g., degradation in mission capability, damage to organizational assets, financial loss, and harm to individuals) for impact / risk ratings.
6) INITIAL RISK
• Discuss the Initial Risk. Impact, when combined with the credibility of Threat and degree of Vulnerability, yields a Risk level (High, Medium, or Low). You must state the Risk for each area (CIAAN) and provide an overall initial risk rating.
• Be certain to discuss the initial risk in terms of expected loss to mission and resources (human and non-human). Please see various publications (e.g., NIST FIPS 199) that can assist you in providing criteria for risk ratings.
RECOMMENDATIONS FOR CONTROLS (COUNTERMEASURES / SAFEGUARDS)
• Analyze your Recommendations for Security Controls (Countermeasures/Safeguards). Understanding Risk enables us to make intelligent, and defensible, Recommendations for Security. Therefore, this Risk Analysis becomes the driver, and support, for your Recommendations of Security Controls (Safeguards and Countermeasures) designed to Protect, Detect, and Correct. Be certain to discuss your controls using the PDC or PPT frameworks.
• Controls discussed MUST apply specifically to your technology of choice. For ex, while items such as training or various NIST SP800-53 controls are fine, you will want to seek out those controls that are especially important / specific to your technology.
• Controls must consider the status of past and current efforts underway within the organization discussed (e.g., U.S. Government, international community, etc.). The intent is to identify what controls need to be implemented in the current and future environments considering what has been or is planned or completed.
(a) Identify and list at least two (2) specific People, Process, AND Technology (or Protective, Detective, and Corrective) controls that relate to the aforementioned vulnerabilities.
A minimum of six (6) controls are required.
(b) Within each subsection, include citation per APA to the specific references in the Reference List that support this selection. Ensure that specific page numbers are included.
Identified controls must be supported by at least two (2) references.
1. Ryan, D. and Ryan, J. (1995). Risk Management and Information Security. Presented at the 11th Computer Security Applications Conference. New Orleans, Louisiana. (Attached in this post).
2. Zack Phillips. (GovExec.com). (2007, August 1). Security Theater.Retrieved from http://www.govexec.com/story_page.cfm?filepath=/features/0807-01/0807-01s3.htm.
1) Implementation Plan to Reform Federal Information Technology Management. Retrieved at http://www.dhs.gov/sites/default/files/publications/digital-strategy/25-point-implementation-plan-to-reform-federal-it.pdf (586.035 Kb) (Shifted the USG to a "Cloud First" Policy)
2) Federal Cloud Computing Strategy.Retrieved at https://cio.gov/building-a-21st-century-government/cloud/.
3) NIST Cloud Relevant Special Publications
SP 800-125, Guide to Security for Full Virtualization Technologies
SP 800-144, Guidelines on Security and Privacy in Public Cloud Computing.
SP 800-145, NIST Definition of Cloud Computing.
4) DOD Policy
DOD.(2012). Cloud Computing Strategy. Retrieved at http://www.defense.gov/news/DoDCloudComputingStrategy.pdf