Phase 5: Reporting Goal: Create two mock reports for the client: An Executive Summary for the clients senior management, and a Detailed Technical Report for the clients IT staff and submit them to your boss (in this case, your mentor). Procedure: Create the two reports below: The Detailed Technical Report should contain the scope and approach, reconnaissance activities, vulnerabilities, and an analysis of the threats that Artemis faces based on the current threat environment. Use this resource as your guide and template for creating the Detailed Technical Report: The report should include the following sections: A. A cover page B. A Table of Contents C. Scope of Work D. Project Objectives E. Assumptions F. Timeline G. Summary of Findings H. Recommendations Target report length: We expect the average report to have a minimum of 10 pages. The Executive Summary. The executive summary serves as a high-level view of the business risk in plain English. The purpose is to be concise and clear. Executives dont need (or want) to understand the technology. It is imperative that business leaders grasp whats at stake to make informed decisions for their companies, and the executive summary is essential to delivering that understanding. Visual communication can be tremendously helpful here. Try to use visuals like graphs and charts in communicating the summary data. The de facto approach is to use colors to denote risk severity, specifically, red, yellow and green. If there are four categories, then add orange. Target report length: No more than 2 pages! Check out this example executive summary for some more guidance on what this final deliverable should look like.