Read a sample: 1. Reconnaissance Starts With Permission
A request to “see what is on the network” sounds straightforward until you ask which network, which systems, and what kind of seeing the requester has in mind. A network administrator may mean a pair of test machines. A project manager may be thinking about every device in an office. A security practitioner might interpret the same request as permission to send probes across an entire address range.
Those interpretations lead to different activity and different risks. Before you open a terminal, you need a shared understanding of what you may examine and how you may examine it.
Reconnaissance is the process of gathering and interpreting information about an environment. In this book, it means carefully observing hosts, names, network paths, and exposed services within a controlled, explicitly authorized setting. The objective is to understand what can be seen from a particular position—not to gain unauthorized access, disrupt systems, or prove that an exposure can be exploited.
The first practical skill is therefore not a Linux command. It is turning permission into a clear, usable boundary.
Some reconnaissance relies on information already available to you, such as a supplied asset list or a configuration file you are authorized to read. Other techniques send traffic and observe responses. Even a simple request to a host can create log entries, trigger monitoring, or interact with software in an unexpected state.
A DNS query asks a server for information. A reachability check sends a message or attempts a connection. A service probe may cause an application to answer with a banner or protocol response. These actions are useful because they provide observations, but they are not invisible merely because they are exploratory.
Nor is every information-gathering action automatically low impact. A rapid sweep can burden a fragile service or a small network. Repeated requests may fill logs or alert queues. A query sent to an unintended resolver can disclose a name you meant to keep inside the lab. The appropriate safeguard is not to avoid learning; it is to decide in advance what is acceptable, use bounded methods, and stop when the environment behaves unexpectedly.
Throughout this book, the practice environment belongs to the exercise. You will build a small lab, document it, and use it as the basis for discovery. Even there, write down the scope. A lab is easier to learn from when you can distinguish what you intended to test from what your commands actually reached.
Reconnaissance asks questions such as:
- Which approved addresses respond from my workstation?
- Which names does the lab DNS server return?
- Which approved ports appear to accept connections?
- What does a service voluntarily reveal in a limited response?
Exploitation goes further: it attempts to use a weakness or capability to achieve an effect beyond the agreed observation. Examples include bypassing authentication, executing a payload, changing data, obtaining a shell, or extracting information the service was not intended to disclose. Attempting common passwords or submitting suspicious input to trigger an error is not made harmless by calling it discovery.
The boundary is not always defined by a tool’s name. A client used to view a welcome banner might also be capable of sending commands. A scanner can perform a narrowly defined port check or run intrusive tests. What matters is the action, its likely effects, and the permission covering it.
For this book, keep the distinction simple: observe only through the approved methods; do not attempt to exploit what you find. If a service presents a login prompt, recording that the prompt appeared can be within scope. Trying credentials requires separate, explicit authorization and is outside this book’s exercises. If a response reveals sensitive information unexpectedly, do not continue exploring it. Minimize further exposure and follow the agreed reporting procedure.
An invitation from a colleague is not necessarily authorization to test every system that colleague can access. The person granting permission must have authority over the assets and the proposed activity. In a shared environment, that may require coordination among system owners, network operators, and a security team. A contractor’s written request, an informal chat message, or access to a network does not by itself establish that authority.
For your own lab, you may be the owner, operator, and tester. Still, verify that the lab is actually under your control. A virtual machine can have a network adapter connected to an unintended network. A domain name can resolve through a public resolver. An address range that appears private can overlap with a real organization’s network. Owning the virtual machines does not automatically make every network path or DNS service they can reach part of the lab.
In a workplace assessment, obtain approval through the organization’s established process. The scope should identify the approving party and the people responsible for coordinating the work. If authority is unclear, resolve it before sending traffic. Do not treat silence, convenience, or a broad job title as a substitute for approval.
A written scope turns a general request into operating instructions. It does not have to be a lengthy legal document for a small lab, but it must be specific enough that another person can tell what is allowed and when to stop.
At a minimum, record the following:
1. Purpose. State what the discovery is intended to establish and what it will not attempt. 2. Authorized assets. Identify approved hosts, address ranges, names, and DNS servers…