Cybersecurity & Networking Guides

What are the ByteBreach field guides?

The guides are long-form, independently readable references on the networking and security topics that come up most often in the labs. Each one is written to be read on its own, without an account, without the learning-path machinery, and without you having to work through the curriculum in order first. If you arrive from a search engine with a specific problem, the guide should answer it and then tell you where to go next.

Every guide follows the same structure, and the structure is the point: the symptom you will observe, the causes that are most likely to produce it, how to confirm which cause you actually have, the fix, and the verification step that tells you it worked. Consistent structure is what makes a reference usable under time pressure, which is when most people actually open one.

Which topics the library covers

The library is growing, but it is deliberately narrow rather than broad. Every guide in it addresses something a ByteBreach maintainer has actually had to diagnose, or a technique that a learner has actually misunderstood.

• Networking foundations: IPv4 subnetting, mask arithmetic, and the addressing mistakes that cause routing failures weeks after they are introduced.
• Packet analysis: a careful Wireshark workflow, from capture filtering through stream reassembly to reading a suspicious conversation end to end.
• Routing and switching: layered troubleshooting for OSPF neighbour states, and the 802.1Q trunking failures that are responsible for a disproportionate share of network outages.
• Responsible security: defining an authorised scope in writing before any testing begins, which is the single control that keeps technical work lawful.
• Offensive reconnaissance: a scanning methodology for authorised auditors, with an emphasis on rate control, false positives, and documentation.
• Privilege escalation and defence: auditing SUID binaries and sudoers policy on Linux, and understanding what each finding actually grants an attacker.
• IPv6 and modern networking: address architecture, SLAAC, and the operational differences that surprise engineers arriving from an IPv4 background.

How to read a guide effectively

Read the symptom section first and check that your problem genuinely matches what is described. If it does not, the guide will not help you, and the most likely cause is something upstream of the topic covered here; the Related Material section at the end of each guide points at the neighbouring subjects. If it does match, work through the confirmation steps before applying the fix, because the fixes for different causes of the same symptom look identical until you actually test for them.

Treat the examples as examples rather than as copy-and-paste input. They are simplified to make the reasoning visible, and a real topology will have additional detail that changes the correct answer. Where a command matters, run it on the simulated device or on a lab you control before you rely on it in production.

How the guides are reviewed and corrected

Guides are written and reviewed by the same engineers who maintain the curriculum and the lab environment, following the academy's editorial policy. Each guide carries a category, a reading time, and a last-reviewed date. We cite primary references where a claim rests on a standard or a specification, so you can check our reasoning rather than take it on trust.

Corrections are handled on the same rule used across the site: if a fix changes a command, a value, or a conclusion, the guide is materially revised and re-dated; a typographical fix that does not change meaning is applied without re-dating. If you find an error, send the URL and a description through the contact page and we will review it.