Home labs & practical projects

Explain an unusual outbound connection from a packet trace

A project to do with your own tools, with guidance on what to create and capture.

Local lab Suggested time: 2–3 hoursYour own authorised environment

What you could create

An analyst receives a small packet capture with an unfamiliar outbound session. The question is what the network evidence can actually establish.

Example evidence format

Project evidence map (example)

Annotated packet walkthroughScope and inputs

Network hypothesis and evidence requestDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Annotated packet walkthrough	Show the inputs, scope and decisions behind this record. The report states visibility limits, including encrypted traffic.
Network hypothesis and evidence request	Include the evidence supporting your conclusion. Every factual assertion can be traced to a packet or capture property.

What you'll need

Local lab

Capture your own harmless traffic between lab machines, including DNS and a test HTTP exchange. Record capture location and clock settings.

Project record

Keep the working files for annotated packet walkthrough and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Uses your own computer. Confirm hardware capacity, software licences and download terms before setup.

Use disposable VMs, containers or a simulator. Keep the lab separate from your everyday machine and work network.

Suggested milestones

1
Plan and investigate
Reconstruct endpoints, protocol negotiation and timing.
2
Develop your approach
Separate directly observed payload details from inferred application behaviour.
3
Verify and explain
Write a hypothesis and identify the host or proxy evidence needed to confirm it.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Annotated packet walkthrough
Show the inputs, scope and decisions behind this record. The report states visibility limits, including encrypted traffic.
2
Network hypothesis and evidence request
Include the evidence supporting your conclusion. Every factual assertion can be traced to a packet or capture property.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your annotated packet walkthrough needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

GIAC official practice tests (2 included with exam)

Check relevance, platform versions and current access terms.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Capture your own harmless traffic between lab machines, including DNS and a test HTTP exchange. Record capture location and clock settings.

What a good result looks like

The report states visibility limits, including encrypted traffic.
Every factual assertion can be traced to a packet or capture property.

Finish the project

Save sanitised evidence, then remove the lab instances or revert to the clean snapshot. Remove temporary accounts and credentials.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.