Cybersecurity & Information Security

Building a Network Timeline from TCP, DNS, HTTP, and TLS Connections

6 min readPublished: August 5, 2026

Professional visual illustration on Network Timeline in Network Security Monitoring

Quick answer

A Network Timeline is built by mapping flow, times, protocols, DNS/TLS/HTTP, and asset context. A single packet or connection is partial evidence, so a sequence is built and verified against additional sources.

Network traffic provides a perspective that does not solely depend on the endpoint. It allows identifying who communicated with whom, using which protocol, in what order, and at what volume, but requires an understanding of visibility limits and encryption. This article focuses on Network Timeline and is intended for SOC analysts and network investigators. 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 incomplete. Query name, response code, TTL can indicate a direction, but their meaning depends on the time, asset, user, and expected activity. Therefore, we will build the examination around an investigative question, required evidence, and clear completion criteria.

The practical scenario in the article is: a timeline of a Download followed by Beaconing. All examples are lab data or process descriptions. When dealing with Penetration Testing, Web, or Cloud, work only with explicit authorization, defined scope, and the ability to stop the test.

Choosing an Anchor event

The topic 'Choosing an Anchor event' is a central part of working on a Network Timeline. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the goal.

In practice, record the query name, response code, TTL, subdomain entropy, NXDOMAIN ratio, compare it to expected behavior, and define at least one pivot. The result should be verifiable by another analyst, including limitations and next steps.

Time Normalization

To understand the difference in the context of a Network Timeline, it is important to compare goals, not just tools. One option provides breadth or speed, while another provides deep verification or context. The right 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. In case of doubt, use the least intrusive approach and add a complementary source instead of drawing too broad a conclusion.

DNS before Connection

The topic 'DNS before Connection' is a central part of working on a Network Timeline. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the goal.

HTTP/TLS context

The topic 'HTTP/TLS context' is a central part of working on a Network Timeline. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the goal.

Presenting the Findings

The topic 'Presenting the Findings' is a central part of working on a Network Timeline. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool usage without understanding the goal.

Unique Inspection Points

For this topic, it is recommended to build a focused evidence map in advance. The main inspection points are: query name, response code, TTL, subdomain entropy, NXDOMAIN ratio, resolver context. The list is not an automatic checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

query name: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
response code: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
TTL: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
subdomain entropy: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
NXDOMAIN ratio: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.
resolver context: Define the expected value, what would be considered anomalous, and what additional source would verify the finding.

When one of the focus points is unavailable, document the gap and choose an alternative. For example, if a Process identifier is unstable, one can use time, Host, User, and Parent; if the Payload is encrypted, use Metadata, volume, frequency, and TLS/DNS context.

Recommended Work Process

Define a Scope and one working question regarding Network Timeline.
Record the data sources and required evidence: query name, response code, TTL, subdomain entropy.
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.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criteria.

Practical Scenario

The chosen scenario is a Timeline of a Download followed by Beaconing. The purpose of the exercise is not to prove attack capability, but to practice collecting, comparing, and documenting safely. Before starting work, define simulated data, a time window, and an expected outcome.

At the end of the exercise, a deliverable should be submitted that another analyst or tester can review: 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 was not proven.

Stage	What is performed	Output
Preparation	Define Scope, time, and target. Record which fields or evidence from query name, response code, TTL are expected to appear.	Short test plan
Data Generation	Perform a safe and simulated Network Timeline related action, 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 recommendation and Retest.	Documented output

Practical Checklist

Check and document: the five components of the Flow.
Check and document: start time, duration, and volume.
Check and document: DNS name and TLS metadata.
Check and document: HTTP method, host, and URI when visible.
Check and document: TCP flags and stream.
Check and document: Host and Process relationship.
State Time zone, tool version, and collection time.
Save the raw data before filtering or changing.
Write what the finding proves and what is still unknown.
Define owner and next action with a due date.

Common Mistakes

Confusing Capture Filter with Display Filter.
Inferring content when traffic is encrypted.
Analyzing IP without DNS/TLS context.
Ignoring NAT or Proxy.
Focusing on a single Packet.
Not saving original Capture.

Summary and CTA

Building a Network Timeline from TCP, DNS, HTTP, and TLS connections 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 re-tested.

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

FAQ

Does Network Timeline alone prove an attack or vulnerability?

No. It provides a signal or finding that requires context, verification, and an additional source. A professional conclusion relies on a sequence of evidence and conformity to expected behavior.

What to do when some data is missing?

Document the missing data, check for an alternative source, and reduce the confidence level. Do not fill fields based on speculation or present Unknown as normal.

How long should evidence be kept?

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, simulated data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.