Cybersecurity & Information Security

Enumeration: How to Map Services and Users in a Lab Environment

6 min readPublished: August 5, 2026

Professional visual illustration of enumeration in penetration testing in the field of Penetration Testing

Quick answer

Enumeration in penetration testing must only be performed within an approved Scope and Rules of Engagement. The process includes information gathering, controlled verification, evidence, risk assessment, remediation, and retest.

Professional penetration testing is an authorized and defined process, not a collection of commands. Scope, Rules of Engagement, evidence, risk assessment, remediation, and retest are an integral part of the work. This article focuses on enumeration in penetration testing and is intended for PT students. The goal is to provide a working methodology that can be applied in practice, during professional interviews, and in a work environment, without settling for a dictionary definition.

The main challenge is that data is almost always partial. Services, versions, and users can indicate a direction, but their significance depends on time, asset, user, and expected activity. Therefore, we will build the test around an investigative question, required evidence, and a clear criterion for completion.

The practical scenario in the article is: enumeration of two authorized lab machines. All examples are lab data or descriptions of processes. When dealing with Penetration Testing, Web, or Cloud, one must only work with explicit authorization, a defined scope, and the ability to stop the test.

Discovery vs. Enumeration

To understand the difference in the context of enumeration in penetration testing, it is important to compare goals, not just tools. One option provides breadth or speed, while another provides deep verification or context. The correct choice depends on the question: Is discovery, investigation, impact proof, containment, or reporting required?

A professional comparison table should include at least: input type, certainty level, operational cost, potential impact, limitations, and required follow-up. When in doubt, use the less intrusive approach and add a supplementary source instead of drawing too broad a conclusion.

Service banners and Versions

The topic 'Service banners and Versions' is a central part of working on enumeration in penetration testing. It is recommended to break it down into three questions: What is the input, what decision do you want to make, and what evidence is sufficient to justify it? These questions prevent automatic tool use without understanding the objective.

In practice, record services, versions, users, shares, trusts, compare to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Authentication surfaces

In enumeration during penetration testing, identity and authorization are two different questions: who is the client, and what is it allowed to do on the resource? Roles, Claims, Session, Object ownership, and changes throughout the lifecycle are examined, and it is not enough to conclude that the user is 'logged in'.

A test matrix includes an anonymous user, a regular user, an object owner, another user, and an administrator. For each action, the Response and server-side impact are compared. Changing an identifier or Header is only a testing means; the evidence is that the server approved or rejected an action contrary to policy.

Users, Shares and Directories

The topic 'Users, Shares, and Directories' is a central part of working on enumeration in penetration testing. It is recommended to break it down into three questions: What is the input, what decision do you want to make, and what evidence is sufficient to justify it? These questions prevent automatic tool use without understanding the objective.

Documentation and Follow-up Decision

Documentation of enumeration in penetration testing should allow a person who did not participate in the work to understand what happened and reproduce the conclusion. Facts, interpretations, assumptions, and decisions are separated, and each claim is linked to evidence, a query, or a screenshot.

A useful structure includes Summary, Scope, Timeline, Evidence, Impact, Actions, Limitations, and Next steps. In a PT report, Remediation and Retest are added; in an investigation, Containment, Recovery, and Lessons learned are added.

Unique Test Foci

In this topic, it is recommended to build a focused evidence map in advance. The main test foci are: services, versions, users, shares, trusts, evidence. The list is not an automatic checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

services: Define the expected value, what will be considered unusual, and what additional source will verify the finding.
versions: Define the expected value, what will be considered unusual, and what additional source will verify the finding.
users: Define the expected value, what will be considered unusual, and what additional source will verify the finding.
shares: Define the expected value, what will be considered unusual, and what additional source will verify the finding.
trusts: Define the expected value, what will be considered unusual, and what additional source will verify the finding.
evidence: Define the expected value, what will be considered unusual, and what additional source will verify the finding.

When one of the foci is unavailable, the gap must be documented and an alternative chosen. For example, if a Process identifier is unstable, time, Host, User, and Parent can be used; if a Payload is encrypted, Metadata, volume, frequency, and TLS/DNS context are used.

Recommended Workflow

Define a Scope and one working question regarding enumeration in penetration testing.
Record the data sources and required evidence: services, versions, users, shares.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal test in a lab environment and save time, input, and output.
Build a Timeline or comparison table and separate fact from interpretation.
Perform a Pivot to an additional source to confirm or refute the initial explanation.
Summarize a decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is the enumeration of two authorized lab machines. The purpose of the exercise is not to prove attack capability, but to practice safe collection, comparison, and documentation. Before starting work, mock data, a time window, and an expected outcome are defined.

At the end of the exercise, a deliverable that another analyst or tester can review should be submitted: a screenshot or export of the evidence, a short Timeline, an initial hypothesis, corroborating evidence, a limitation, and a recommendation. When there is insufficient evidence, the correct conclusion is that the scenario has not been proven.

Stage	What is performed	Deliverable
Preparation	Define Scope, time, and objective. List which fields or evidence from services, versions, users are expected to appear.	Short test plan
Data Creation	Perform a safe and simulated action related to enumeration in penetration testing, without real information or impact on a production system.	Controlled event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Verify Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what is the possible legitimate explanation.	Interim conclusion
Completion	Choose closure, escalation, Finding or Tuning; add a recommendation and Retest.	Documented deliverable

Practical Checklist

Check and document: Scope and ROE.
Check and document: Test time and source.
Check and document: Request/Response or tool output.
Check and document: Proven impact in the lab.
Check and document: Risk rating.
Check and document: Remediation and Retest.
State Time zone, tool version, and collection time.
Save the raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and follow-up action with due date.

Common Mistakes

Starting a test without a signed Scope.
Using an aggressive Exploit by default.
Not saving Evidence.
Reporting only CVSS without context.
Not offering a feasible remediation.
Not performing a Retest.

Summary and CTA

Enumeration: How to map services and users in a lab environment is a topic that combines technical knowledge with work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and retested.

In HPI's Cybersecurity & AI track, these principles are practiced using systems, logs, and labs. A natural continuation is to move on to the linked articles, perform the lab exercise, and save the output as part of a professional portfolio.

FAQ

Is it permissible to perform enumeration testing on a public website?

Not without explicit authorization from the system owner. Even a seemingly simple test can alter data, trigger defense mechanisms, or be considered unauthorized access.

What to do when some data is missing?

Document the missing data, check an alternative source, and reduce the level of confidence. Do not fill in fields with assumptions or present Unknown as valid.

How long should evidence be retained?

The time depends on policy, regulation, cost, and event type. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without risking a real system?

Use virtual machines, mock data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.