[SOLVED] A structured walkthrough penetration test of a fictional company, Artemis, Incorporated | SolutionInn
- Tool: Nmap. Purpose: Obtain information on hosts and the services and operating systems they are running.
Commands:
Deliverable: What are the tools you plan on using for the network scans, your reasoning for selecting them, and how they will be used. Be sure to include any challenges and potential drawbacks or limitations. Deliverable should cover at least 5 tools/resources. Course content reference: There are two optional labs, Reconnaissance from the WAN and Scanning the Network on the LAN, that may help you with this step. NOTE: Kali is not a tool; it is a Linux distribution or collection of tools, so do not include it in your list. Phase 3. Identify Vulnerabilities Goal: Identify the tools and techniques to be used to scan for vulnerabilities. Procedure: List out the tools you plan on using to perform vulnerability scanning and how you will use them. Include both Tenable Nessus and OpenVAS. Remember to include tools designed to look for vulnerabilities within specific technologies or platforms, such as Cisco devices, remote access services, and web applications (e.g., Burp Suite). Follow the same documentation procedure you performed in the previous step. Include screenshots of such tools showing configuration options and settings. Finally, list the pros and cons of each tool. Deliverable: Provide a minimum 2-page description of the tools you plan on using for the vulnerability scans, how you will use them, screenshots of the tools with configuration options and settings, and the pros and cons of each tool. Deliverable should cover at least 5 tools. Phase 4. Threat Assessment Goal: Create a hypothetical threat assessment based on vulnerabilities you expect to f ind when you perform your actual scans against the client’s network. Procedure: Assume the scenarios below are what you are most likely to encounter when you begin your actual work.
Scenario 1: Unpatched RDP is exposed to the internet
Scenario 2: Web application is vulnerable to SQL Injection
Scenario 3: Default password on Cisco admin portal
Scenario 4: Apache web server vulnerable to CVE-2019-0211
Scenario 5: Web server is exposing sensitive data
Scenario 6: Web application has broken access control
Scenario 7: Oracle WebLogic Server vulnerable to CVE-2020-14882
Scenario 8: Misconfigured cloud storage (AWS security group misconfiguration, lack of access restrictions)
Scenario 9: Microsoft Exchange Server vulnerable to CVE-2021-26855
Deliverable: Provide a spreadsheet or document showing the following items. Make sure you factor in the appropriate context. For example, if you think you might be able to penetrate the APOLLO system, evaluate those risks according to that system’s sensitivity and criticality. ● Description of the vulnerability ● Operating systems/versions affected ● Risks of attempting to exploit (e.g., might crash the host or lock out an account) ● Risk (what could you or a threat actor do upon successful exploitation)? ○ Identify as many attack vectors as you can. Examples: launch an attack on internal systems, obtain password hashes, crack passwords, access other systems, move laterally, and so on). ○ Identify potential blocking mechanisms such as AV software or IDS/IPS, and how you might try to bypass them. ○ Document how you plan on cracking passwords. This will depend on the source system’s course, but you should be ready for whatever you run into. Include online tools as well. ● Remediation action ● CVSS score Course content reference: You may need to refer back to the unit on risk assessment to analyse the vulnerabilities and assess what threat they pose to Artemis. In addition, review the two videos: Vulnerability Management: Assessing the Risks with CVSS v3.1 and Implementing the NIST Risk Management Framework in the Audit and Risk Management subunit. Remember: The threat depends on the likelihood and impact of the vulnerabilities being exploited and requires a review and knowledge of the current threats. Include all the information and risk ratings to determine the threat profile for Artemis. Phase 5: Reporting Goal: Create two mock reports for the client: An Executive Summary for the client’s senior management, and a Detailed Technical Report for the client’s 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
● 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 don’t need (or want) to understand the technology. It is imperative that business leaders grasp what’s 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. Step by Step Solution
3.48 Rating (158 Votes )
There are 3 Steps involved in it Get step-by-step solutions from verified subject matter experts