Order Number |
65775436486234 |
Type of Project |
ESSAY/DISERTATION |
Writer Level |
PHD/MASTERS CERTIFIED |
Format |
APA/MLA/HARVARD/OXFORD |
Academic Sources |
10 -20 |
Page Count |
4-8 PAGES |
Incident Report Components
Overview In the last module, you worked on incident response strategies to implement during an event. Now you will be assessing a realworld breach while working on components of an incident report. While following response plans, you may be required to generate incident reports on the entirety or part of an incident. This is challenging because there are many times when an incident strays off on tangents and moves away from the root cause. Therefore, it is important to be able to identify the components of an incident report before you have to generate the final output.
Proper documentation is a necessity when trying to document incidents as they are happening and after the fact. This documentation may include identification of the issue, assets involved, and effects of the incident. Many organizations have their own templates on how an incident response will be documented. It is important to find a reporting mechanism that works for your organization. It should not impede the process but facilitate it. If, at any point, the documentation becomes confusing and cannot be used to learn from the situation, then the type of documentation should be revisited. Once a root cause is identified, it should be shared with all members of your organization. This will promote a stronger awareness of identifying the same type of issue as soon as possible.
As you read through the articles for this assignment, consider the complexity involved in continuing to provide aid during an active breach with weak data protection processes. Guidelines and protections exist to prevent this type of incident, but how do you best deal with it in the middle of a crisis? As you think about root cause, remember that it often entails many contributing factors and no single easy fix.
Prompt From the Module Three Reading and Resources, review “A ‘Major Privacy Incident’ at FEMA Exposes Personal Information of 2.5 Million Disaster Survivors,” “FEMA OIG: Agency Mistakenly Shared Data on 2.3M Hurricane, Fire Victims,” and “Management Alert— FEMA Did Not Safeguard Disaster Survivors’ Sensitive Personally Identifiable Information (REDACTED).” You will use the viewpoints presented in both articles, along with the CIS Controls document, to develop components of an incident report that includes contributing factors to the root cause of the incident.
You must address the critical elements listed below.
https://www.chicagotribune.com/nation-world/ct-fema-privacy-data-breach-20190322-story.html
FEMA OIG: Agency Mistakenly Shared Data on 2.3M Hurricane, Fire Victims
https://www.oig.dhs.gov/sites/default/files/assets/2019-03/OIG-19-32-Mar19.pdf
RUBRIC | |||
Excellent Quality
95-100%
|
Introduction
45-41 points The context and relevance of the issue, as well as a clear description of the study aim, are presented. The history of searches is discussed. |
Literature Support
91-84 points The context and relevance of the issue, as well as a clear description of the study aim, are presented. The history of searches is discussed. |
Methodology
58-53 points With titles for each slide as well as bulleted sections to group relevant information as required, the content is well-organized. Excellent use of typeface, color, images, effects, and so on to improve readability and presenting content. The minimum length criterion of 10 slides/pages is reached. |
Average Score
50-85% |
40-38 points
More depth/information is required for the context and importance, otherwise the study detail will be unclear. There is no search history information supplied. |
83-76 points
There is a review of important theoretical literature, however there is limited integration of research into problem-related ideas. The review is just partly focused and arranged. There is research that both supports and opposes. A summary of the material given is provided. The conclusion may or may not include a biblical integration. |
52-49 points
The content is somewhat ordered, but there is no discernible organization. The use of typeface, color, graphics, effects, and so on may sometimes distract from the presenting substance. It is possible that the length criteria will not be reached. |
Poor Quality
0-45% |
37-1 points
The context and/or importance are lacking. There is no search history information supplied. |
75-1 points
There has been an examination of relevant theoretical literature, but still no research concerning problem-related concepts has been synthesized. The review is just somewhat focused and organized. The provided overview of content does not include any supporting or opposing research. The conclusion has no scriptural references. |
48-1 points
There is no logical or apparent organizational structure. There is no discernible logical sequence. The use of typeface, color, graphics, effects, and so on often detracts from the presenting substance. It is possible that the length criteria will not be reached. |
Place the Order Here: https://standardwriter.com/orders/ordernow / https://standardwriter.com/
Incident Report Components