Course contentsShow
← Security
Lesson 2088 of 3,05242. Penetration Testing and Red TeamingFree lesson

Common Testing Targets and Scope

Identify typical penetration testing targets including networks, applications, wireless, and physical systems.

Common Testing Targets and Scope

What you'll learn: You'll identify the typical systems and components that penetration testers examine and understand how scope defines the boundaries of an engagement.

When you launch a penetration test, you need to know exactly what you're testing and where you can go. Think of it like a security inspection of a building—you need to know if you're checking just the front door, the entire ground floor, or the whole property including the parking lot.

Typical Testing Targets

Networks: The infrastructure connecting systems—routers, switches, firewalls, VPNs, and network segmentation. Testers look for misconfigurations, weak access controls, and vulnerable protocols.

Applications: Web applications, mobile apps, APIs, and desktop software. This is often the most visible attack surface, where testers hunt for injection flaws, broken authentication, and business logic errors.

Wireless Systems: Wi-Fi networks, Bluetooth implementations, and RF communications. These tests examine encryption strength, authentication mechanisms, and unauthorized access points.

Physical Systems: Building access controls, badge readers, server room security, and even social engineering vectors like tailgating or dumpster diving.

Defining Scope

Scope defines the boundaries of your testing engagement. It specifies:

  • In-scope targets: IP ranges, domain names, specific applications, facilities
  • Out-of-scope items: Production databases, third-party services, certain time windows
  • Authorized actions: Can you perform denial-of-service tests? Social engineering? Physical intrusion?

Poor scoping leads to missed vulnerabilities (too narrow) or legal trouble (too broad). Always get written authorization before testing—a "get out of jail" letter that clearly states what you can test, when, and how.

Key Takeaway: Penetration testing targets include networks, applications, wireless systems, and physical infrastructure; proper scope definition with written authorization ensures comprehensive yet legal testing that protects both tester and organization.