External penetration testing plan

Complete the Penetration Testing Plan Template to create a Penetration Testing Plan for the organization you chose.

Research/Consider and include the following:

Pentest Pre-Planning
Engagement timeline: Tasks and who performs them
Team location: Where will the penetration team execute their tests? Team location can be the location of the teams involved with testing such as IT Operations. It's not uncommon for teams to operate in separate locations. Therefore, for this assignment the team location can be San Francisco, CA or it can be at the company headquarters such as Seattle, WA. This part is all fictional data so feel free to complete this portion of the assignment however you like. If you need ideas, you can look at larger public companies such as Amazon, Google, Microsoft, Apple, etc. as they tend to share a good deal of information on their websites about their organizations, office locations, corporate offices, etc.
Organization locations tested: multiple locations, countries (export restrictions and government restrictions). Organization location can be the headquarters of the corporate office (e.g. Seattle, WA).
Which pentest technologies will be used? Consider the following as you research options:
Scanning Tools: Nmap, Nikto
Credential Testing Tools: Hashcat, Medussa, John the Ripper, Cain and Abel
OSINT Tools: Whois, TheHarvester
Wireless Tools: Aircrack-ng, Kismet
Networking Tools: Wireshark, Hping
What client personal are aware of the testing?
What resources provided to pentest team?
Test Boundaries:
What is tested?
Social engineering test boundaries? What is acceptable?
What are the boundaries of physical security tests?
What are the restrictions on invasive pentest attacks?
What types of corporate policy affect your test?
Gain Appropriate authorization (Including third-party authorization)
Pentest Execution Planning: Given the scope and constraints you developed in your Pentest Pre-Plan, plan the following pentest execution activities
Reconnaissance
Scanning
Gaining Access
Maintaining Access
Covering Tracks
Pentest Analysis and Report Planning:
Analyze pentest results
Report pentest results
Project sponsor can be CIO, CISO, CEO, the board, etc.

Business context for penetration test is a business statement for why the test is needed.

Project scope description can be application testing, internal/external network testing, wifi testing, physical security testing, social engineering testing. These are common scopes for real-world penetration testing.