[SOLVED] A structured walkthrough penetration test of a fictional company, Artemis, Incorporated | SolutionInn

5. 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. This project is an excellent addition to your portfolio as it demonstrates your understanding of critical security issues and your skills in identifying and analyzing threats and vulnerabilities. The project also allows you to speak knowledgeably about the entire process of performing a pen test, using your project as a reference point. Each phase will include its own deliverable(s). A full description of what is required can be found under each phase. Directions When planning penetration tests, consulting firms always sit down with the client’s key stakeholders to confirm scope and approach, identify the client’s concerns, and set expectations regarding the outcome. To this end, you have been provided with an overview of the client and an overview of the client’s IT environment. This information is critical because all risks must be evaluated within their context. The example below illustrates this concept: Technically Accurate– Artemis’ web application does not restrict or filter user uploads by file type. This is a vulnerability that could allow threat actors to connect remotely, execute arbitrary code, and then elevate their privileges within the application. With context– Artemis’ RFQ/RFP web application does not restrict or filter user uploads by file type. This is a vulnerability that could allow threat actors to connect remotely, execute arbitrary code, and then elevate their privileges within the application. In this instance, the threat actors would be able to view or download sensitive information regarding bids and even gain admin rights within the application. As you can see, the second description indicates the technical aspects and the business impact as well. The next two sections, client overview and technology overview, provide the context you will need to help you with the five phases of your capstone project. Client Overview ARTEMIS GAS, INC. (“Artemis”), based in Paris, France, is present in 40 countries with approximately 30,000 employees and serves more than 1.7 million customers and patients. Oxygen, nitrogen, and hydrogen have been at the core of its activities since its creation in 1922. They own and operate over 1,000 miles of industrial gas pipelines in the U.S., supplying mainly oxygen, nitrogen, hydrogen, and syngas in large quantities from multiple production sources to major customers in the chemicals, petrochemicals, refining, and steel industries. Their pipeline operations and industrial gas production facilities are closely monitored 24/7 within their leading-edge operations control center located in Houston, TX. Their operations control group monitors over 49,000 data points and assists with product supply and coordination. They are constantly optimizing their supply network to provide high reliability and energy efficiencies, allowing Artemis to adjust supply needs more quickly and effectively, thus enabling growth to their customers. Artemis has grown quickly over the past few years, and the need to “make things work” has outpaced the need to “make things work securely.” Some security solutions are fairly mature and effective; some are less so. Among the company’s concerns are: ● Some of the older network hardware that is being phased out is unsupported and may have unpatched vulnerabilities. ● Some of the newer network hardware may not have been configured properly. ● Some business units do not always follow company policy regarding storing data in the cloud, creating websites, or conducting file transfers. ● Some IT admins like to do their own thing because “that’s the way they’ve always done it.” This could be exposing the network to unknown risks. Technology Overview Artemis utilizes a mix of security vendors and technologies. The firewall landscape consists of Cisco, Fortinet, and Palo Alto. They use F5 (Big IP) for load balancing, and for secure remote application access, they use Zscaler. Roughly half of their servers and applications are in the cloud (Amazon Web Services), and the rest are on-premise (on-prem). These on-prem assets are spread out among four major data centers located in Houston, Paris, Cairo, and Singapore. The network is currently transitioning to SD-WAN, so there are still several MPLS links, especially at the smaller, more remote locations. The old Cisco equipment is being phased out in favor of Fortigate devices from Fortinet. Additionally, since the Fortigates can also act as firewalls, the company is considering eliminating the rest of its Cisco gear to cut costs. They are unable to supply a current network diagram. The ones they have are severely out of date and would not be of any use to you. Internally, Artemis utilizes a Single Sign-On (SSO) solution that leverages Microsoft Active Directory to authenticate users to other applications, namely SAP. SAP is the company’s primary ERP system and runs on servers running Linux and Oracle 12c. Messaging is a mix of Exchange Online (via the Office 365 cloud tenant) and on-prem Microsoft Exchange servers. The only other applications of note are the PARS system and the APOLLO system. PARS allows engineers to submit technical information regarding potential patents. If the submission passes legal and technical review, it is forwarded to the Intellectual Property group for submission to either the US Patent Office, the National Institute of Industrial Property INPI) in France, or both. APOLLO is the repository for trade secrets, primarily around manufacturing processes. Project Guidelines This next section will provide you with the goals, procedures, deliverables, and time estimates expected for each phase of the project. Read each of these sections carefully before proceeding to begin on phase 1. Phase 1. Perform Reconnaissance Goal: Build as robust a profile on the target (Artemis) as possible. The profile should include the target’s technology stack, email addresses, phone numbers, resumes, and so on. Procedure: Detail the activities you plan to use to obtain as much publicly available information as you can. Deliverable: Provide a minimum two-page description of all the tools and methods you will use to accomplish this task. Deliverable should cover at least 15 tools/resources. Phase 2. Identify Targets and Run Scans Goal: Identify the tools and techniques to be used to perform host discovery and enumeration. Procedure: List out the tools you plan on using to perform network scans, the purpose for using them, and how you will use them. For example: