Assignment Task

Assessment and Context

The goal of this assessment is to identify the threats or vulnerabilities in the case scenario described in the associated file, Assessment Initial Case Scenario.docx. NOT all threats or vulnerabilities you “discover” are in the initial case scenario. Discovery of threats is important. For each threat you need to indicate how it would be discovered in a business and in three cases, expand with a viable explanation of discovery, with small relevant details of an interview or survey, etc.

You should use this assessment brief document to guide what to include in this assessment and use the provided case study to help demonstrate understanding of the topic.

Instructions

To successfully complete this assessment, your MIS607 Assessment 2 MUST include: The reportshould have the following heading structure.

Title page

The title page should include subject code and name, assessment number, report title, assessment due date, word count (actual), student name and surname, student ID, Torrens’s email address, learning facilitator name and surname.

Executive Summary

The best time to write the Executive Summary is when you have finished working on your assessment. Top-level executives often only read the executive summary, so it is a brief summary of what was done with a very brief overview of major results.

1. Introduction

Since you already have an executive summary, this can be quite brief. You will need to provide a short description of the case organization. Overall, the introduction section is about “What the assessment is going to be about?”

2. Main Discussion

2.1. Data Flow Diagrams (DFDs)

The DFDs must relate to the business described in the initial case scenario. You must remember that the DFDs are the FIRST step in the “Risk Analysis” process, and so they are not the main output of this assessment. The main output of MIS607 Assessment 2 is the categorized threats (see below).

For the DFD section of your report, you will need to present at least a “Context Diagram” (level-0) and a “Level-1 Diagram” (DFD). You can include further levels of DFD (e.g., Level-2, Level-3, etc.) if you feel they are needed to show a trust boundary, but it’s not necessary.

The level-1 diagram (and further level diagrams, if needed) must not break the rule for proper DFD formation/development. And the DFDs (excluding the Context Diagram) MUST have labelled trust boundaries.

2.2. Threat List, Threat Discovery, and STRIDE Categorisation

For the threat list you should have a table of at least 10 threats with at least the following headings: threat brief name, brief description, brief discovery technique, STRIDE category, trust boundary, and whatever else may be handy. Make the table as readable as possible.

After the table, you need to expand on at least three of the threats (one of these must be the main threat mentioned in the case). These should be related to research material. You should also go into some explanation of how you discovered the threat (as if you found them within the organization).You need to discuss the other seven threats in brief(2-3 lines at least)

3. Conclusion

In this section, you will wrap up your discussion in a clear and simple way. Overall, the conclusion section reminds the reader what the report/assessment has been about. Indicate and discuss the major findings and/or recommendation of your report.