Here you will create a risk management plan at the enterprise level.Your organization: belongs to Hospitality Industry OR Food Processing Industry OR Software Development IndustryProvide a name of your company and the industry it belongs to. Step-1. Find all valuable assets across the organization that could be harmed by threats in a way that results in a monetary loss. Examples: Servers, WebsiteStep-2. Identify potential consequences. Determine what financial losses the organization would suffer if a given asset were damaged. Examples: Data loss, legalStep-3. Identify threats and their level. A threat is anything that might exploit a vulnerability to breach your security and cause harm to your assets. Example: System failureStep-4. Identify vulnerabilities and assess the likelihood of their exploitation. A vulnerability is a weakness that allows some threat to breach your security and cause harm to an asset. Think about what protects your systems from a given threat — if the threat actually occurs, what are the chances that it will actually damage your assets? Vulnerabilities can be physical (such as old equipment), problems with software design or configuration (such as excessive access permissions or unpatched workstations), or human factors (such as untrained or careless staff members).Step-5. Assess risk. Risk is the potential that a given threat will exploit the vulnerabilities of the environment and cause harm to one or more assets, leading to monetary loss. Assess the risk according to the logical formula stated above and assign it a value of high, moderate or low. Then develop a solution for every high and moderate risk, along with an estimate of its cost.Step-6. Create a risk management plan using the data collected. Use the template below.ThreatVulnerabilityAsset and ConsequencesRiskSolutionThreat-1High or Moderate or Low or Very LowVulnerability-1High or Moderate or Low or Very LowAsset name / and related consequences -1Critical or Moderate or MinimumRisk-1High or Moderate or Low or Very LowSolution-1Threat-2High or Moderate or Low or Very LowVulnerability-2High or Moderate or Low or Very LowAsset name / and related consequences -2Critical or Moderate or MinimumRisk-2High or Moderate or Low or Very LowSolution-2Threat-3High or Moderate or Low or Very LowVulnerability-3High or Moderate or Low or Very LowAsset name / and related consequences -3Critical or Moderate or MinimumRisk-3High or Moderate or Low or Very LowSolution-3---------------Threat-nHigh or Moderate or Low or Very LowVulnerability-nHigh or Moderate or Low or Very LowAsset name / and related consequences -nCritical or Moderate or MinimumRisk-nHigh or Moderate or Low or Very LowSolution-nStep-7. Create a strategy for IT infrastructure enhancements to mitigate the most important vulnerabilities and get management sign-off.Step-8. Define mitigation processes. You can improve your IT security infrastructure but you cannot eliminate all risks. When a disaster happens, you fix what happened, investigate why it happened, and try to prevent it from happening again, or at least make the consequences less harmful. For example, here is a sample mitigation process for a server failure:Event (server failure)Response (use your disaster recovery plan or the vendor’s documentation to get the server up and running) Analysis (determine why this server failed) Mitigation (if the server failed due to overheating because of low-quality equipment, ask your management to buy better equipment; if they refuse, put additional monitoring in place so you can shut down the server in a controlled way)Step-9. Risk assessment is not a one-time event. Both your IT environment and the threat landscape are constantly changing, so you need to perform risk assessment on a regular basis. Create a risk assessment policy that codifies your risk assessment methodology and specifies how often the risk assessment process must be repeated.

Team Project ReportAttached Files: project-report-template-601.docx Project Goal: Each team will demonstrate the use of Kali (Linux) in the Infosec Learning virtual lab environment.Step #2:Research the variety of tools available on the Kali Linux distribution for testing. Each team will select a set of tools to research, evaluate and test. Each team member must conduct the testing in their assigned set of VM’s and compare the results with their teammates.Notify the instructor (via email) of the selected tool(s) prior to starting for review and approvalBe prepared to address these questions in your written report and presentation:Why test?Why did your team select the specific testing tools you used for your project?Research and find one alternative to Kali Linux and compare and contrast the two distributions.(NOTE: A possible resource for information is the “MSCYB Toolset Resource-Reference Guide” found in Course Resources | Course Documents folder.)Step #3:Each team member has a cyber sandbox that contains the following VMs (the assigned IP addresses will be different):Using the assigned VMs, each team member will setup and configure their Kali VM to run tests against the target VM’s in their respective environments (OWASP, Windows, Metasploitbale etc) using the selected tool. Team members should be able to identify and inventory the specific set of VMs that will be used in the test (e.g., IP address and OS). Students may choose which tests to run using the selected software tool(s), all of which must be documented in the written report (use the template provided for your written report).Team members should compare the outcomes of each test with their own prior test results and those of the other team members.Important: The virtual machines are non-persistent (data will be lost when the VM is shutdown), make sure you capture screenshots when you conduct testing.Written Report Requirements: An APA formatted template is attached for your convenience, please use it.Use the same font throughout the report, such as 12-point Times New Roman Charts or Tables may use 10-pointNOTE: Full-page illustrations are not counted as a page.Title page:Start page numbering in upper right cornerTitle of paperTeam member names AffiliationCourse number and course nameInstructor nameAssignment Due Date Table of Contents (this is a class requirement)Abstract Page: One paragraph (double spaced)Not indentedNo longer than one page, preferably around 150 wordsMain body (does not include title, abstract, or references):Double spaced (no extra spacing before or after)Research the selected set of tools (below are discussion headings, include others to enhance your report):Introduction (Introduce the report to the reader)Kali LinuxYour ToolsetAlternative to Kali LinuxConclusionLast page(s): List of APA formatted ReferencesBeginning on a new pageListed alphabeticallyMinimum of 10 credible references, at least five published within the last two yearsThere needs to be at least one in-text citation for every reference!Only the PM needs to submit for the team: Click on the "Team Project Report" link above to submit the team's project report, as well to get more information regarding the due date and grading rubric. NOTE: SafeAssign has been activated for this assignment.