Conducting Penetration Test Exercises CIO-IT Security-11-51

Total Page:16

File Type:pdf, Size:1020Kb

Conducting Penetration Test Exercises CIO-IT Security-11-51 IT Security Procedural Guide: Conducting Penetration Test Exercises CIO-IT Security-11-51 Revision 4 January 18, 2018 Office of the Chief Information Security Officer CIO-IT Security-11-51, Revision 4 Conducting Penetration Test Exercises VERSION HISTORY/CHANGE RECORD Change Person Posting Page Number of Change Reason for Change Number Change Change Revision 1 – April 30, 2012 Bo Berlas Clarified guidance relating to Penetration testing shall occur performance of penetration against production environments 1 testing against development to ensure testing activities reflect 8 environments. the risks of the system under review. Revision 2 – December 11, 2014 Bo Berlas Changed requirement for Focuses penetration testing penetration testing from ALL activities at areas of greatest risk. systems (i.e., FIPS PUB 199 Aligns with updated Low, Moderate and High) to requirements in GSA IT Security 1 Pages 4 and 8 FIPS PUB 199 Low and Procedural Guide 06-30, Moderate Internet accessible "Managing Enterprise Risk". systems and All FIPS PUB 199 High. Bo Berlas Changed references to Office Administrative to reflect changes of the Senior Agency in office name and CISO title as a Information Security Officer result of IT and IT Security (OSAISO) and Senior Agency consolidation. Information Security Officer 2 Numerous (SAISO) to Office of the Chief Information Security Officer (OCISO) and Chief Information Security Officer (CISO) Blanche Heard Updated to reflect references Organization titles and 3 to comply with ADM O responsibilities Numerous 5440.667 Revision 3 – December 1, 2015 Bo Berlas Updated Reporting Template Updated to reflect changes to 1 and associated references NIST SP 800-53 Rev 4 and reflect Pages 9 and 20 process updates William Updated Reporting Template, Reflect changes to OWASP, NIST Salamon Rules of Engagement SP 800-15 recommendations, Pages 11-12, 16- 2 Template, and updated incorporate cloud computing 17, 21-22 several sections concepts, and other process updates Revision 4 – January 18, 2018 Dean/Feliksa/ Revised to reflect current Revised to reflect how GSA Klemens/ GSA processes and conducts penetration tests based Newsome procedures for conducting on Federal policies, NIST controls 1 penetration tests. with GSA parameters, and GSA Throughout processes and procedures. Updated to current guide structure and format. U.S. General Services Administration CIO-IT Security-11-51, Revision 4 Conducting Penetration Test Exercises APPROVAL IT Security Procedural Guide: Conducting Penetration Test Exercises, CIO-IT Security-11-51, Revision 4, is hereby approved for distribution. 1/18/2018 X Kurt Garbars Kurt Garbars CISO Signed by: KURT GARBARS Contact: GSA Office of the Chief Information Security Officer (OCISO), Policy and Compliance Division, at [email protected]. U.S. General Services Administration CIO-IT Security-11-51, Revision 4 Conducting Penetration Test Exercises Table of Contents 1 Introduction ...............................................................................................................................1 1.1 Purpose ......................................................................................................................................... 1 1.2 Scope ............................................................................................................................................ 1 1.3 Policy ............................................................................................................................................. 2 1.4 References .................................................................................................................................... 2 2 Penetration Testing Overview .....................................................................................................2 2.1 Penetration Testing Approaches .................................................................................................. 4 2.2 Defining the Scope and Test Boundary ........................................................................................ 5 2.3 Threat Modeling ........................................................................................................................... 5 2.4 Exploiting Vulnerabilities .............................................................................................................. 6 3 GSA Penetration Testing Process .................................................................................................6 3.1 Planning Phase .............................................................................................................................. 7 3.2 Defining the Rules of Engagement ............................................................................................... 8 3.3 Penetration Testing Authorization ............................................................................................... 9 3.4 Test Phases ................................................................................................................................... 9 3.5 Additional Considerations .......................................................................................................... 11 4 Incident Response Procedures .................................................................................................. 11 5 Points of Contact ...................................................................................................................... 11 Appendix A: Penetration Test Rules of Engagement Template ........................................................... 12 Appendix B: Authorization Memorandum Template ......................................................................... 13 Appendix C: Penetration Test Findings Template .............................................................................. 14 Appendix D: Penetration Test Report Template ................................................................................ 15 Appendix E: Penetration Test Tools .................................................................................................. 16 Table of Figures and Tables Table 1-1: Impact Risk Rating Calculation Table ......................................................................................... 5 U.S. General Services Administration i CIO-IT Security-11-51, Revision 4 Conducting Penetration Test Exercises 1 Introduction A penetration test is an authorized simulation of a cyber attack which is used to identify security weaknesses by way of technical flaws, misconfigurations, software vulnerabilities, and/or business logic. A penetration tester will attempt to exploit weaknesses to gain access, modify functionality, and/or corrupt the business logic of the target system without creating additional risk to the agency or organization. The penetration tester will attempt to perform activities of a malicious agent; however, such activities will be conducted ethically and with the permission of the General Services Administration (GSA) Office of the Chief Information Security Officer (OCISO) Information System Security Officer (ISSO) Support Division (IST) Division prior to execution. Keeping the best interests of the organization/agency in mind, the penetration tester will not introduce new vulnerabilities into the target environment. A penetration test exercise supports the overall security process by identifying security risks and demonstrating exploitability of findings that may not be readily apparent when performing a security review. A penetration test can be performed with or without knowledge of the system, and involves the execution of a scenario and abuse cases that focus on violating technical, administrative, and management controls to gain access to the system or data. Penetration tests can be used to verify and prove scan results that are false positives or false negatives. Penetration tests, as opposed to vulnerability scans, should not have false positive findings since they report only on found vulnerabilities. Penetration tests while capable of verifying or proving a specific false negative finding, are not exhaustive and therefore cannot prove there are no vulnerabilities to a system. The test processes described in this document are used for measuring, evaluating, and testing the security posture of an information system, but test findings should not be used to the exclusion of other security processes (e.g., architecture analyses, configuration checks.) 1.1 Purpose This procedural guide provides guidance for performing penetration test exercises against GSA applications, infrastructure, and systems. It provides GSA associates and contractors with significant security responsibilities as identified in the current GSA Order CIO 2100.1, “GSA Information Technology (IT) Security Policy,” and other IT personnel involved in penetration testing exercises on GSA IT resources, an independent repeatable framework for conducting penetration test activities. 1.2 Scope The requirements outlined within this guide apply to and must be followed by all GSA Federal employees and contractors who are involved in penetration testing of GSA information systems and data. U.S. General Services Administration 1 CIO-IT Security-11-51, Revision 4 Conducting Penetration Test Exercises 1.3 Policy Penetration testing is addressed in CIO 2100.1 as stated in the following paragraphs: Chapter 3, Paragraph 2.b(6): All Internet accessible information systems, and all FIPS 199 High impact information systems are required to complete an
Recommended publications
  • Kali Linux Penetration Testing Bible
    Telegram Channel : @IRFaraExam Table of Contents Cover Title Page Introduction What Does This Book Cover? Companion Download Files How to Contact the Publisher How to Contact the Author CHAPTER 1: Mastering the Terminal Window Kali Linux File System Managing Users and Groups in Kali Files and Folders Management in Kali Linux Remote Connections in Kali Kali Linux System Management Networking in Kali Linux Summary CHAPTER 2: Bash Scripting Basic Bash Scripting Printing to the Screen in Bash Variables Script Parameters User Input Functions Conditions and Loops Summary CHAPTER 3: Network Hosts Scanning Basics of Networking Network Scanning DNS Enumeration Telegram Channel : @IRFaraExam Summary CHAPTER 4: Internet Information Gathering Passive Footprinting and Reconnaissance Summary CHAPTER 5: Social Engineering Attacks Spear Phishing Attacks Payloads and Listeners Social Engineering with the USB Rubber Ducky Summary CHAPTER 6: Advanced Enumeration Phase Transfer Protocols E‐mail Protocols Database Protocols CI/CD Protocols Web Protocols 80/443 Graphical Remoting Protocols File Sharing Protocols Summary CHAPTER 7: Exploitation Phase Vulnerabilities Assessment Services Exploitation Summary CHAPTER 8: Web Application Vulnerabilities Web Application Vulnerabilities Summary CHAPTER 9: Web Penetration Testing and Secure Software Development Lifecycle Web Enumeration and Exploitation Secure Software Development Lifecycle Summary CHAPTER 10: Linux Privilege Escalation Telegram Channel : @IRFaraExam Introduction to Kernel Exploits and Missing Configurations
    [Show full text]
  • Network Security & Penetration Testing
    TEL3214 Computer Communication Networks Lecture 10 Network Security Diarmuid Ó Briain CEng, FIEI, FIET, CISSP [email protected] Lab Exercise Using the Kali Linux image provided install VirtualBox, build the .ova image, install and run. Login to the image with the default root username (root) and password (toor). Diarmuid Ó Briain What is Penetration testing Penetration testing (also called pen testing) is the practice of testing a computer system, network or Web application to find vulnerabilities that an attacker could exploit. Proactive Authorised Evaluation of IT infrastructure Safely attempting to exploit system Vulnerabilities Improper configurations Risky end-user behaviour. Diarmuid Ó Briain What steps are used to carry out pen test Planning and Preparation Information Gathering and Analysis Vulnerability Detection Penetration attempt Analysis and Reporting Cleaning up Diarmuid Ó Briain Planning and Preparation Kick-off meeting Clear objective for pen-test Timing and duration allowed for the pen-tests Personnel involved Are staff being informed of the tests? Network and Computers involved Operational requirements during the pen-test How the results are to be presented at the conclusion of the test. Diarmuid Ó Briain Planning and Preparation Penetration Test Plan Detailed plan Confidentiality Statement Acceptance Sign-off Sheet Diarmuid Ó Briain Information gathering and analysis Gathering of as much information as possible as a reconnaissance is essential. What does the network look like? What devices are on the network? Who works at the company? What does the organogram of the company look like? Diarmuid Ó Briain Vulnerability detection Once a picture of the target organisation has been compiled a scan of vulnerabilities is the next step.
    [Show full text]
  • Positioning of Penetration Testing and IT Risk Management Frameworks Investigated
    Positioning of Penetration Testing and IT Risk Management Frameworks investigated September 2013 Scriptienummer 1090 Jip Hogenboom MSc Nick Peterman MSc Thesis EDP Audit, Vrije Universiteit Amsterdam September 2013 “If you don’t invest in risk management, it doesn’t matter what business you’re in, it’s a risky business” Gary Cohn Jip Hogenboom MSc i Nick Peterman MSc Thesis EDP Audit, Vrije Universiteit Amsterdam September 2013 1 Preface This document is the thesis of the postgraduate study programme on EDP auditing at the Vrije Universiteit Amsterdam. This thesis covers the positioning of penetration testing within IT risk management frameworks and the relationship between IT risk management and penetration testing. We would like to express our thanks to Dr. René Matthijsse RE, our supervisor at the Vrije Universiteit, for his support and criticism. Additionally, we would like to express our thanks to Mr. Michiel van Veen MSc RE and ir. Peter Kornelisse for their support during the course of the project. We would not have come this far without them. Furthermore, we would like to thank the participants to our case study interviews for their time and availability to express their opinion and share their experience on this subject. Last but not least we would like to thank our families for their support and their patience with us during our study. Without them we definitely would not have made it. Jip Hogenboom Nick Peterman Amstelveen, September 2013 Jip Hogenboom MSc ii Nick Peterman MSc Thesis EDP Audit, Vrije Universiteit Amsterdam September 2013 2 Abstract Risk management is an important step within each business process and project to minimise, monitor, and control the probability and/or impact of unfortunate events or to maximise the realisation of opportunities.
    [Show full text]
  • A Guide for Running an Effective Penetration Testing Programme
    A guide for running an effective Penetration Testing programme April 2017 A guide for running an effective Penetration Testing programme Published by: CREST Tel: 0845 686-5542 Email: [email protected] Web: http://www.crest-approved.org/ Principal Author Principal reviewer Jason Creasey, Ian Glover, President, CREST Managing Director, Jerakano Limited DTP notes For ease of reference, the following DTP devices have been used throughout the Penetration Testing Guide. Acknowledgements CREST would like to extend its special thanks to those CREST member organisations who took part in interviews and to those clients who agreed to be case studies. Warning This Guide has been produced with care and to the best of our ability. However, CREST accepts no responsibility for any problems or incidents arising from its use. A Good Tip ! A Timely Warning An insightful Project Finding Quotes are presented in a box like this. © Copyright 2013. All rights reserved. CREST (GB). 2 A guide for running an effective Penetration Testing programme Contents Part 1 – Introduction and overview • About this Guide ................................................................................................................................................4 • Purpose ..............................................................................................................................................................4 • Scope .................................................................................................................................................................5
    [Show full text]
  • Always On. Always Secure. the Ultimate Handbook to Penetration Testing
    THE ULTIMATE HANDBOOK TO PENETRATION TESTING ALWAYS ON. ALWAYS SECURE. THE ULTIMATE HANDBOOK TO PENETRATION TESTING 9 CREATING A BRIEF FOR A 14 PENETRATION TESTING PENETRATION TEST CHECKLIST 10 PENETRATION TESTING 15 TAKE THE NEXT STEP STRATEGIES 11 LIFE-CYCLE OF A PENETRATION TEST 3 ABOUT THIS GUIDE 12 WHAT SHOULD YOUR PEN 4 ABOUT COMTACT LTD TEST REPORT CONTAIN? 5 OUR EXPERTISE 6 WHAT’S THE DIFFERENCE? 16 RESOURCES 7 WHY & WHEN IS A PENETRATION TEST NEEDED? 8 TYPE OF PENETRATION 13 QUESTIONS TO ASK YOUR TEST PEN TEST PROVIDER ABOUT THIS GUIDE Penetration testing is a critical part of an on-going cyber assessment programme and is one of the common tools at your disposal, providing a real-world test of your cyber security defences. Often referred to as ethical hacking, penetration testing uses all the tips and WHAT YOU’LL LEARN tricks available to real-world hackers, but performed in agreement with the company being tested, to a pre-defined scope. Gain a greater understanding of the various The goal of a penetration test is to: penetration testing aspects • Identify security weaknesses • Prove these weaknesses through How to determine the right kind/s of penetration exploitation tests suited to your specific business context • Provide guidance on the remediation required Guidance on the end-to-end process to achieve real value and full benefit from penetration testing results This handbook is aimed at people who need to procure, plan and manage the life How and why penetration testing is a fundamental cycle of a penetration testing project. component to any risk management programme 3 // THE ULTIMATE HANDBOOK TO PENETRATION TESTING ABOUT COMTACT LTD.
    [Show full text]
  • CSC347 Tutorial 1 -‐ Penetration Testing, Basics
    CSC347 Tutorial 1 - Penetration testing, Basics Before anything else! • cd /virtual • mkdir <utorids> • cd <utorids> • unzip ../a2/kali.zip • This takes nearly 5 minutes. Try to use the same computer each time we use kali. LATER! When you first open the vm, BEFORE starting it • Edit Virtual settings • Network Adaptor • Custom – change it so vmnet8 Choose “I copied it” when asked Intended Outcomes: At the end of this tutorial, you should: Understand the relevance of the steps in a Penetration Test Have gathered information about the localhost or your own laptop Be able to gather information on your own home network, or your own personal business network. Source for this tut: Book: A Hands-On Introduction to Hacking by Georgia Weidman (Who mentions Penetration Testing Execution Standard (PTES): http://www.pentest-standard.org/ ) Stages of the Penetration Testing 1. Pre-engagement 2. Information Gathering 3. Threat Modeling 4. Vulnerability Analysis 5. Exploitation 6. Post Exploitation 7. Reporting In more detail 1. Pre-engagement Critical: Scope NDA Reporting Never do anything you do not have an agreement for (get out of Jail-Free-Card) What are the client’s goals – why do they want a pentest What data are important to the client/ what matters most to them? ** Do they know what a pentest is, what is required to do one properly? ** Do they understand a pentest could crash a system? Who do you contact / what times of the day can you do the work? 2. Information Gathering - What has the client told you ** think social engineering - What is available publically * LinkedIn; job adverts; social sites - What would a hacker find to allow them to attack the system - http://www.netcraft.com/ - whois <url> - nslookup / dig / host -t ns url - Can you get dns records? Eg - host -l zoneedit.com ns2.zoneedit.com - email records.
    [Show full text]
  • External Penetration Testing External Penetration Testing Checklist
    External Penetration Testing External Penetration Testing Checklist Jose croons his lacquerers bathed vitalistically, but uncanonical Wolfie never reword so nowhere. Ceramic and debilitative Carlie never desquamated fadedly when Wes coning his dogmatizer. Jared footslogs his strake girding incontestably or wooingly after Morley foreshows and gesticulating mythologically, hectographic and malicious. This checklist helps a client has a kb during transmission between scanner would buy anything but not working, external penetration testing external penetration testing checklist can then gathered as reverse dns. OS which is basically an OS which pull both a command line interface and a graphical user interface! Pull ntlm hashes in externally available in reverse engineering or external penetration testing external penetration testing checklist. These are the imminent deal, inside target corporations institutions even perceive the government. In integrity lightning and tamper evidence testing, we say that the application does that allow users to destroy cell integrity of big part of grey system adjust its data. Assessors should use range limitations into consideration when scoping this gleam of scanning. Trying the request a zone transfer for owasp. Badge usage refers to a physical security method that involves the colonel of identification badges as these form account access control. There that many options for a hacking laptop. Basic allows us to define the ivy itself. LF sequence in it. This guide allows organizations to compare yourself against industry peers, to till the pure of resources required to test and maintain water, or even prepare how an audit. In mind that has specific exploits stopping testing checklist is enforced, external penetration testing checklist.
    [Show full text]
  • Introduction: Penetration Testing & Ethical Hacking
    Penetration Testing 1.0.1 Introduction: Penetration Testing & Ethical Hacking CIRCL TLP:WHITE [email protected] Edition 2021 Overview 0. Setup your personal Penetration-Lab 1. Physical access 2. Introduction into Pentesting 3. Reconnaissance / Information Gathering 4. Scanning 5. Exploiting 6. Password Cracking 7. Web Hacking 8. Post Exploitation 9. Supporting Tools and Techniques 2 of 153 0. Setup your personal Penetration-Lab 3 of 153 0.1 Penetration-Lab considerations Virtual environment advantages: ◦ Cheap and flexible ◦ Portable Why "Host-only" network: • Don't want to expose vulnerable systems • Typos happen during the tests Attacking system: Kali Linux Target systems: Metasploitable 2 WinXP or Windows 7 Linux server Example: VirtualBox 4 of 153 0.2 Prepare a virtual network - VirtualBox Example - Create a "Host-only" network: 1. In VirtualBox select 'File/Host Network Manager... ' to open the preferences window 2. Create a new 'Host Network' 3. Set network parameter which don't conflict with you real networks and press 'Apply' 5 of 153 0.3 Get your attacking system ready Get Installer and Live image of: Kali Linux ! https://www.kali.org/downloads/ $ t r e e ./2021 CIRCL PenLab / +−− k a l i / +−− hdd/ +−− i s o / +−− k a l i −l i n u x −2021.1− i n s t a l l e r −i 3 8 6 . i s o +−− k a l i −l i n u x −2021.1− l i v e −i 3 8 6 . i s o Create your virtual attacking system 6 of 153 0.3 Get your attacking system ready Connect the network adapter to the "Host-only" network Connect the optical drive to the Kali iso image file 7 of 153 0.3 Get your attacking system ready Boot the virtual PC and install Kali linux Optimize the installation options for your needs 8 of 153 0.3 Get your attacking system ready The attacking system should now be part of the 'Host-only' network For Internet (Updates/Tools/Exercises) temporary enable a NAT adapter 9 of 153 0.4 Target system: MSF Download and unpack: Metasploitable 2 ! https://www.kali.org/downloads/ $ t r e e ./2021 CIRCL PenLab / +−− metasploitable −l i n u x −2.0.0.
    [Show full text]
  • Backtrack System: Security Against Hacking
    International Journal of Scientific and Research Publications, Volume 5, Issue 2, February 2015 1 ISSN 2250-3153 BackTrack System: Security against Hacking Munir A. Ghanem Information Technology Department, Northern Border University Abstract- Hacking became one of the world's most famous Lastly, our research presentation in front of the discussion information technology problem. It's the work of whom doesn't committee, will be followed by a practical application to show has a work, a work to gain more money, a work to harm others, the security tools of BackTrack. and a work for many other purposes. Almost every week, if it is not every day, we hear about hacking attacks that hits many significant sites in the country, such as: Ministries, Banks, II. PROBLEM DEFINITION Uniform sites and many other important persons accounts on the Problem that imposes to write this research can be social network sites. Fortunately, not all the hackers are summarized as follows: professional in hacking, but they trained them self on one or 1. Clear increase of hacking attacks without any deterrent more of such programs for one of the previous purposes. On the or knowing how to stop it. other side, the secret of success in such hacking attacks is that the 2. Unawareness of many individuals on how to secure intended attacked targets did not take the proper precautionary their computers. measures to protect themselves from such attacks. 3. Raise people knowledge on e-piracy culture, and In this research, I am focusing on "BackTrack System" and consequently raising knowledge of information security.
    [Show full text]
  • 'SAMPLE+Security+Testing+Findings'
    PENETRATION TEST REPORT Prepared by PrimoConnect Prepared for: SAMPLECORP LTD v1.0 September | 30 | 2018 SampleCorp LTD PrimoConnect Email: [email protected] - Web: www.primoconnect.co.uk Phone: 0800 464 0131 SampleCorp – Penetration Test Report PrimoConnect 0800 464 0131 www.primoconnect.co.uk SAMPLECORP LTD 123 North Street London, N1 2AB 01234 567 890 www.samplecorp.com No warranties, express or implied are given by PrimoConnect with respect to accuracy, reliability, quality, correctness, or freedom from error or omission of this work product, including any implied warranties of merchantability, fitness for a specific purpose or non-infringement. This document is delivered "as is", and PrimoConnect shall not be liable for any inaccuracy thereof. PrimoConnect does not warrant that all errors in this work product shall be corrected. Except as expressly set forth in any master services agreement or project assignment, PrimoConnect is not assuming any obligations or liabilities including but not limited to direct, indirect, incidental or consequential, special or exemplary damages resulting from the use of or reliance upon any information in this document. This document does not imply an endorsement of any of the companies or products mentioned. ©2018 PrimoConnect. All rights reserved. No part of this document may be reproduced, copied or modified without the express written consent of the authors. Unless written permission is expressly granted for other purposes, this document shall be treated at all times as the confidential and
    [Show full text]
  • Penetration Testing Is Focused Test with an Objective to Expose One Or Two of Internal Systems
    QUICK GUIDE A HOLISTIC APPROACH TO CONTINUOUS SECURITY TESTING WHY PENETRATION TESTS ARE INADEQUATE To protect valuable computer systems, we build layers of security around A penetration test is them. The layers comprising your security perimeter need to be tested to usually carried out as make sure they can really protect against the relevant threats. a “black box” exercise, with no knowledge Penetration testing is focused test with an objective to expose one or two of internal systems. possible ways of reaching the protected system. Uncovering even a single Therefore, it may not hole in the perimeter is considered a successful penetration test. identify issues which While penetration tests are valuable for organizations and security teams, may be obvious to they overlook two major factors: anyone with access to • The network infrastructure internal networks and devices. • Networking blind spots In addition, penetration tests are valid only for a limited period of time, and the result does not remain true after making changes to the network configuration or policies. It is a time-bound snapshot of an organization’s security posture, which constantly evolves. 26601 Agoura Road | Calabasas, CA 91302 USA | Tel + 1-818-871-1800 | www.ixiacom.com Page 1 915-8099-01 Rev A A MORE HOLISTIC APPROACH Ixia offers a holistic approach for security testing, which concentrates on exposing the chinks in your perimeter armor, and can expose many more security holes throughout the network. The tests are repeatable, and can easily be turned into a continuous, ongoing process. Every time the network changes, after any network or policy changes, the tests may re-run automatically to see if the network is still secure.
    [Show full text]
  • External Penetration Test Report 2021
    External Penetration Test Report 2021 January 15, 2021 Sample Project Authored by: Freddie Fakename Table of Contents Disclaimer ........................................................................................................................................ 5 Scope ............................................................................................................................................... 6 Testing Objective ................................................................................................................ 6 Risk Classification ................................................................................................................ 6 External Penetration Test Results ................................................................................................... 7 Summary of Vulnerabilities ............................................................................................................. 8 1. Communication is not secure ..................................................................................................... 9 2. CKEditor 4.10.1 has 3 vulnerabilities ........................................................................................ 10 3. Jquery 3.4.1 has 2 vulnerabilities .............................................................................................. 10 MacGuyverTech Inc. – Sample Report Page 2 Date: January 15, 2021 To: Sample Project Management Re: Internal Network Penetration Test Report 2021 MacGuyverTech is pleased to present the following
    [Show full text]