Joltlined

Notes & literary analysis

Business & technology competitions

FBLA Study Plan

One study system, four events. Use explanations to understand a topic, recall practice to remember it, and applied tasks to use it without help. Start with one topic and a practice attempt; explore the source references when more detail is needed.

Study resources: 44 two-page reference sheets with practice questions and labs. The website can be used on its own; an optional 654-card Anki package supports additional recall practice. Use practice results to decide what to study next.

Start here: one topic, one practice attempt

  1. Choose an event below. On its course page, select one sheet from the contents. Read its two pages, or try the practice first if the topic is already familiar.
  2. Open “Sources, practice, lab and scope notes” beneath that sheet. Attempt the questions before expanding their answers. The same module lab can appear under several related sheets; you do not need to repeat an identical lab for each sheet.
  3. Check recall without the notes. Explain the idea aloud or answer a practice question. If using the companion Anki package, select the matching event subdeck and use Browse to find topic words. The card order is not a lesson sequence, and cards are not mapped one-to-one to sheets.
  4. Apply the idea without the answer in view. Complete the suggested lab or scenario. For Network Design and Sales, also practice aloud using the rehearsal guidance below.
  5. Write down what went wrong privately. Revisit that explanation, then try a different question or scenario later. Remembering the original answer is not the same as solving a new problem.

New to a topic? Read the sheet and work through its examples before attempting practice. Already familiar with it? Try practice first, skim material you can explain and apply, and focus on gaps. Choose a starting point that fits current knowledge rather than a fixed order.

Website: understand and apply

The event pages contain concise reference sheets, expandable practice answers and lab instructions. Plain and colored downloads contain the same notes; choose whichever is easier to read.

Optional Anki: remember

If a copy of the companion FBLA.apkg is available, import it into Anki. The 654 cards are not embedded in this website. Without the package, use the practice questions for recall. When updating an existing deck, preserve its learning progress.

Rehearsal: perform

Use unfamiliar cases, your own presentation and audience feedback to practice decisions and delivery. The website does not track your scores or synchronize your Anki progress.

Complete event study courses

Choose the event you are working on today. Networking Infrastructures and Cybersecurity emphasize written knowledge; Network Design adds a spoken case response; Sales requires your own interactive presentation.

Networking Infrastructures

14 two-page sheets · 192 Anki cards.

Open Networking Infrastructures course

Connect your networking knowledge to the detailed objectives; test unfamiliar addressing, protocol, media, and troubleshooting decisions.

National 2026–27 format and test weighting

Official CONNECT guideline PDF

Test items by knowledge area in that document:

  • Networking basics: 20 of 100
  • Topologies and architecture: 20 of 100
  • Network security: 25 of 100
  • Protocols and standards: 20 of 100
  • Hardware and connectivity: 15 of 100

Cybersecurity

13 two-page sheets · 194 Anki cards.

Open Cybersecurity course

Distinguish similar controls and attacks. Explain why a protection works, its limits, and which evidence would change your response.

National 2026–27 format and test weighting

Official CONNECT guideline PDF

Test items by knowledge area in that document:

  • Fundamentals: 15 of 100
  • Threats and vulnerabilities: 20 of 100
  • Security and design: 20 of 100
  • Network and data security: 15 of 100
  • Operations and management: 10 of 100
  • Protocols and threat mitigation: 20 of 100

Network Design

12 two-page sheets · 180 Anki cards.

Open Network Design course

Practice the technical test and spoken recommendations separately: requirements, alternatives, implementation, costs, recovery, and verification.

National 2026–27 format and test weighting

Official CONNECT guideline PDF

Test items by knowledge area in that document:

  • Installation and configuration: 25 of 100
  • Security and recovery: 20 of 100
  • Administration: 20 of 100
  • Planning: 15 of 100
  • Protocols, services, and access: 20 of 100

Sales Presentation

5 two-page sheets · 88 Anki cards.

Open Sales Presentation course

Develop a complete, truthful pitch: discover needs, demonstrate relevant value, handle objections, explain scope and costs, and request an appropriate next step.

National 2026–27 format and test weighting

Official CONNECT guideline PDF

Interactive presentation: discovery, product knowledge, objections, related offerings, closing, follow-up, organization, delivery and interaction.

Reading the notes

Color reference

Two independent layers: section headings and their matching Overview entries use varied palettes for navigation. Body terms keep one fixed color across every sheet, page, and event: LAN is always dark blue in the body, even under a differently colored heading. Light blue identifies the overall sheet title.

The groupings below describe the current organization, not a universal conceptual taxonomy. Red includes both attacks and defensive controls; yellow includes both wireless terms and ROI. Learn the named term, rather than assuming that a color alone defines its meaning.

Scroll the table horizontally to see all columns on a narrow screen.

Current organization of the FBLA note colors
Color / inkMain groupingsExamples in the notes
Dark blue#173f88Selected network identifiers, trust principles, and toolsLAN, MAC, Zero Trust, DNS, gateway, ping
Medium blue#287db3IP addressing, hardware forms, and selected infrastructure termsIP, IPv4, subnet, mask, octet, DSL
Light green#79c900Switching, recovery, and selected performance vocabularyIPv6, DHCP, switch, fiber, latency, dual stack
Orange#e67e22Routing, provider access, and permission vocabularyWAN, routers, NAT, ISP, modem, cellular
Purple#883ac2Segmentation, endpoints, and presentation criteriaVLAN, VMs, endpoint, rubric, eye contact, criteria
Light pink#ed8eb4Selected networking/application protocols and business termsOSI, TCP, HTTPS, ARP, SaaS, consent
Dark pink#ec228cAuthentication, secure-access vocabulary, and selected namesTLS, VPN, MFA, certificates, passwords, Windows
Dark green#168438Recovery, cryptography, and measured performanceRAID, backups, encryption, patching, throughput, hashes
Yellow#ebc600Wireless vocabulary and selected namesWi-Fi, WPA3, SSID, 5G, BitLocker, ROI
Red#df3034Attacks, weaknesses, ciphers, and selected controlsDoS, phishing, IDS, IPS, cipher, firewalls
Light blue#59b8e7Overall sheet titlesOverall sheet display titles; not assigned to body terms.

Unregistered prose stays pencil. Every registered body term retains its assigned ink, including when several differently colored terms occur on the same line. Color supplements the wording; plain-text downloads are available on every event page.

Full body-term index (255 registered forms)
Dark blue
LAN, LANs, MAC, MACs, Zero Trust, least privilege, least-privilege, SQL, IaaS, AWS, ipconfig, tracert, traceroute, ping, nslookup, DNS, MIB, NAS, OSPF, P2P, PoE, SAN, spectrum, gateway, gateways
Medium blue
IP, IPv4, CIDR, subnet, subnets, subnetting, cloud, packet, packets, NIST, accounting, rack, blade, blades, chassis, copper, coax, single-mode, multimode, backhaul, mask, octet, octets, DSL, broadcast, network adapter
Light green
IPv6, DHCP, DHCPv6, switch, switches, switching, frame, frames, feature, features, recovery, PHY, fiber, capacity, latency, Neighbor Discovery, dual stack
Orange
WAN, WANs, router, routers, routing, NAT, PAT, BGP, Ethernet, PaaS, Azure, OWASP, claim, claims, cost, costs, permission, permissions, cellular, ISP, modem, ONT, optical network terminal, peering, point-to-point
Purple
MAN, MANs, VLAN, VLANs, VM, VMs, virtual machine, virtual machines, hypervisor, hypervisors, container, containers, IoT, segmentation, RBAC, role-based access control, DAC, discretionary access control, authorization, Active Directory, priority, priorities, endpoint, endpoints, follow-up, rubric, eye contact, projection, poise, fluency, criterion, criteria
Light pink
OSI, TCP, HTTP, HTTPS, SMTP, POP3, IMAP, FTP, FTPS, SFTP, TCO, SaaS, FTC, consent, ARP
Dark pink
UDP, SSH, TLS, VPN, NAC, MFA, RADIUS, ACL, ACLs, certificate, certificates, authentication, authenticator, authenticators, attestation, password, passwords, FBLA, Windows, Windows Server, close, closing
Dark green
RAID, UPS, backup, backups, BCP, DRP, RTO, RPO, confidentiality, integrity, availability, nonrepudiation, encryption, decryption, cryptography, AES, SHA-256, SHA-512, hash, hashes, hashing, blockchain, Merkle, public key, public-key, private key, Linux, benefit, benefits, patch, patches, patching, throughput
Yellow
Wi-Fi, WLAN, WLANs, WPA2, WPA3, WEP, SSID, SSIDs, OFDM, MIMO, 5G, IEEE, Cisco, BitLocker, ROI, access point, access points
Red
DoS, DDoS, malware, virus, viruses, worm, worms, Trojan, Trojans, ransomware, phishing, phishing-resistant, smishing, vishing, exploit, exploits, vulnerability, vulnerabilities, injection, buffer overflow, race condition, zero-day, threat actor, threat actors, firewall, firewalls, NGFW, WAF, SELinux, mandatory access control, objection, objections, IDS, IPS, Caesar, cipher, ciphers, substitution, binary, decimal, hex, hexadecimal, dotted-decimal

Build a study schedule

Adapt these stages to the time available, current knowledge and chosen events. They can span weeks or months; they are not an official schedule. Check regional competition, registration and submission deadlines before planning backward from a target event.

  1. Find gaps. Sample practice across the chosen events, identify unfamiliar topics and begin spoken practice early. Use the sheets to repair weaknesses rather than rereading everything equally.
  2. Connect and apply. Work through weak areas, use recall practice regularly, and complete relevant labs or tabletop exercises.
  3. Add time pressure. Mix topics, change the numbers or scenario, and practice cases and presentations without reading the model answer.
  4. Run full simulations. Use the applicable official timing and rating sheet. Ask a partner or adviser for specific feedback, especially on reasoning and questions.
  5. Build consistency. Retest recurring weaknesses with new tasks, rehearse interruptions and equipment failures, and confirm logistics.

A useful weekly rhythm: several short recall sessions, focused work on weak topics, an application or lab, and a spoken rehearsal for each performance event you are preparing. Adjust the workload to your actual results; finishing a card count is not the goal.

17 skills to practice through scenarios and presentations

Use this checklist to practice 8 Network Design skills and 9 Sales Presentation skills. These involve applying knowledge, explaining decisions and interacting with an audience. They are not 17 additional official requirements or 17 separate assignments; several skills can be practiced in one session.

A full Network Design role-play can exercise its seven presentation criteria together, and a Sales run-through can cover several sales skills. Choosing a recovery plan is a scenario-based technical skill, not an eighth role-play rubric criterion. The reference IDs connect each skill to the course material; they do not need to be memorized.

Network Design: 8 skills to practice
  1. Choose a recovery plan for the situation

    Given an outage or disaster scenario, choose prevention, continuity and recovery measures. Explain the likely data loss, downtime and how you would test recovery.

    Open the related study sheet · Study reference: ND-NSR-02

  2. Identify the real problems

    Summarize an unfamiliar case in your own words. Separate stated facts from assumptions and prioritize the problems you need to solve.

    Open the related study sheet · Study reference: ND-RP-01

  3. Compare feasible alternatives

    Compare at least two plausible approaches against the same requirements. Explain their costs, advantages, risks and limitations rather than listing products.

    Open the related study sheet · Study reference: ND-RP-02

  4. Defend a solution and implementation plan

    Recommend an approach and explain the implementation order, people and resources needed, validation checks and rollback plan.

    Open the related study sheet · Study reference: ND-RP-03

  5. Apply technical knowledge to the case

    Explain why the networking and security choices fit this case. Check the addressing, access, capacity and recovery assumptions relevant to your proposal.

    Open the related study sheet · Study reference: ND-RP-04

  6. Organize the spoken recommendation

    Give a clear briefing that moves from the problem to alternatives, your recommendation, implementation and verification. Ask a listener to summarize your recommendation.

    Open the related study sheet · Study reference: ND-RP-05

  7. Deliver it clearly and confidently

    Record a run-through or ask someone to observe your pace, projection, posture and audience engagement. Identify one specific change for the next attempt.

    Open the related study sheet · Study reference: ND-RP-06

  8. Handle judge questions during delivery

    Have a partner interrupt with unfamiliar questions. Listen, clarify when needed, explain your reasoning and acknowledge uncertainty before returning to the briefing.

    Open the related study sheet · Study reference: ND-RP-07

Sales Presentation: 9 skills to practice
  1. Open naturally

    Create your own greeting and opening, then move smoothly into discovering the customer's needs rather than reciting a generic script.

    Open the related study sheet · Study reference: SP-R-01

  2. Discover needs and listen

    Role-play with someone whose answers you do not know in advance. Ask open questions, follow up and confirm what matters before recommending an offer.

    Open the related study sheet · Study reference: SP-R-02

  3. Explain and demonstrate the offer

    Use your actual product or service to explain relevant benefits, evidence, costs and limits. Verify the claims and practice the demonstration with an offline fallback.

    Open the related study sheet · Study reference: SP-R-03

  4. Respond to objections

    Ask a partner to vary concerns about price, suitability or risk. Clarify the concern, answer honestly and check whether your response addressed it.

    Open the related study sheet · Study reference: SP-R-04

  5. Make an appropriate close

    Make a clear, timely request for the sale or an appropriate next step. Respond to the customer's answer without pressure or invented promises.

    Open the related study sheet · Study reference: SP-R-06

  6. Build the relationship and follow through

    Practice a useful recap and follow-up agreement with a partner. Confirm responsibilities, timing and permission to contact them; do not promise customer loyalty.

    Open the related study sheet · Study reference: SP-R-07

  7. Keep the presentation organized and on time

    Run your actual presentation aloud, including team handoffs if applicable. Check that a listener can follow the offer, costs and next step within the event timing.

    Open the related study sheet · Study reference: SP-R-08

  8. Deliver with confidence and clarity

    Record a complete run-through and get feedback on pace, projection, posture and audience engagement. Practice recovering from a missed line or a demonstration problem.

    Open the related study sheet · Study reference: SP-R-09

  9. Answer interactive questions

    Have a partner ask unpredictable questions during the pitch. Listen fully, answer the actual question, state factual limits and return naturally to the conversation.

    Open the related study sheet · Study reference: SP-R-10

How to rehearse: read the related sheet, attempt the task without the model answer, and have a partner note what you explained well, what you missed and how you handled questions. If practicing alone, record a first attempt; later use a partner for unpredictable interaction. Repeat the weak part, then try a new scenario.

Timing in the National 2026–27 guides: Network Design uses 20 minutes of preparation and a 7-minute presentation. Sales uses 3 minutes of setup and a 7-minute presentation. Questions can occur during either presentation; there is no separate Q&A segment. Confirm the format used at your competition.

Practice beyond this checklist. Related-product suggestions, event protocols and technical troubleshooting also need application. Use the event courses and official guidelines to plan broader preparation; this list is a set of practice prompts, not a complete measure of readiness.

Before competition: confirm the rules

These materials follow the National 2026–27 guides. Check the applicable state or regional FBLA association and ask an adviser about qualification, entry limits, deadlines and conference-specific rules. Studying four events does not establish eligibility to enter all four.

Ask for clarification on the Network Design guide's conflicting visual-aid language and undefined “SMP,” and the Sales guide's conflicting final-round electricity statements. Do not assume a permitted visual aid or power supply; prepare an appropriate contingency.

National event resources · Source details and limitations

Optional worked example: the subnetting lesson below demonstrates the read → recall → apply loop. Skip it if you can already solve and explain these problems; it is not the required first lesson.

Download printable plain-text note · Open plain-text source

IPv4 subnetting and VLSM — optional worked example

Purpose: practice the subnetting portions of Networking Infrastructures NI-NB-07 and Network Design ND-NIC-07. These are locally assigned study IDs, not official FBLA identifiers. This is an original note, not an official guide or a complete treatment of either objective.

Edition and scope

The Networking Infrastructures and Network Design scope follows the National 2026–27 CONNECT guidelines. This worked example covers subnetting portions of the study objectives, not either entire event. Use the event courses for broader preparation and confirm division-specific requirements with an adviser.

IPv4 foundations

An IPv4 address is 32 bits. A subnet mask marks the network prefix with 1 bits and the host portion with 0 bits. CIDR /n means n leading network bits; the dotted mask is a readable form of those bits. Example: /26 = 255.255.255.192 because the final octet mask is 11000000.

Classful networking divided historical address ranges into fixed Class A/B/C network sizes. Modern routing uses classless CIDR prefixes: the prefix length, not an address's first octet class, defines the network boundary. Do not infer a subnet mask from an address's old class.

For an ordinary subnet, network address has all host bits zero; directed broadcast has all host bits one. Usable host range lies between them. Conventional usable count is 2^(32-prefix)-2, except special cases such as /31 point-to-point links (RFC 3021) and /32 host routes.

Worked example: /26

Given 192.0.2.77/26, mask is 255.255.255.192. Block size in final octet = 256 - 192 = 64. Blocks start 0, 64, 128, 192; 77 belongs to block 64. Network 192.0.2.64; broadcast 192.0.2.127; usable hosts 192.0.2.65–192.0.2.126 (62 conventional hosts). Check: bitwise IP address AND mask gives the network address; setting all host bits to one gives the broadcast address.

Worked VLSM plan

Allocate from 192.0.2.0/24, largest host requirement first. Need 100, 50, and 20 hosts. A /25 has 126 conventional hosts; assign 192.0.2.0/25 (usable .1–.126, broadcast .127). A /26 has 62; assign 192.0.2.128/26 (usable .129–.190, broadcast .191). A /27 has 30; assign 192.0.2.192/27 (usable .193–.222, broadcast .223). Remainder is 192.0.2.224/27. No ranges overlap; each start aligns to its block size. VLSM uses different prefix lengths within the parent block.

Special cases and traps

/31 is valid for a two-endpoint point-to-point link under RFC 3021: both addresses are endpoints, with no separate network/broadcast address convention. Do not apply the ordinary minus-two rule there. /32 denotes one exact IPv4 address, commonly a host route; it is not an ordinary multi-host LAN. Confirm platform and context before applying special cases.
Common traps: subtracting two for every prefix; choosing blocks in small-to-large order; confusing mask value with block size; forgetting boundary alignment; including network/broadcast as ordinary host assignments; calling CIDR “classful”; allowing VLSM overlaps; and using public-looking real addresses in examples. 192.0.2.0/24 is TEST-NET-1 documentation space (RFC 5737), not a deployable public allocation.

Retrieval practice — answer before opening answers

  1. For 198.51.100.139/27, find mask, network, broadcast, usable range, and conventional host count.
  2. Why does /26 use a block size of 64 in the final octet?
  3. Allocate requirements 60, 25, and 10 hosts from 203.0.113.0/24 using VLSM; show prefix, range, and broadcast.
  4. Explain why a /31 point-to-point link is not handled by the normal minus-two rule.
  5. What does /32 represent, and why is it not a normal LAN subnet?

Application questions

A small office has a lab allocation of 192.0.2.0/24. Segments need 90, 40, 12, and 2 assigned addresses, including any gateway/router interfaces. Propose a largest-first VLSM allocation, state assumptions about the two-address link, and prove there is no overlap or out-of-parent allocation.
An engineer says 198.51.100.139 historically falls in Class C and therefore must use /24. Correct the reasoning and explain what information actually determines the subnet.

Answer key — reveal after attempting the questions

Answer key

1. /27 mask 255.255.255.224, block 32. Network 198.51.100.128; broadcast .159; usable .129–.158; 30 hosts.
2. 256 minus the final-octet mask value 192 equals 64 addresses per subnet.
3. 60: 203.0.113.0/26 (hosts .1–.62, broadcast .63); 25: .64/27 (hosts .65–.94, broadcast .95); 10: .96/28 (hosts .97–.110, broadcast .111). Remaining .112–.255 is unallocated.
4. RFC 3021 assigns both /31 addresses to the two link endpoints; no network or directed-broadcast address is reserved for that link convention.
5. /32 has zero host bits and identifies one address, often used for a route to one host.
Office: 90 needs /25 at .0–.127; 40 needs /26 at .128–.191; 12 needs /28 at .192–.207; two endpoint addresses can use .208/31 only if a point-to-point link and supporting equipment are intended. Otherwise allocate /30 (.208–.211), leaving .212–.255. All are aligned, disjoint, and within /24.
Classful reasoning is obsolete for modern subnet selection. The configured/advertised CIDR prefix determines the boundary; 10.4.8.9 alone does not.

Packet Tracer lab

  1. Represent three LANs sized for 100, 50, and 20 assigned addresses from the worked 192.0.2.0/24 block. Use one PC and switch per LAN; you do not need to place 170 devices. Add a router with three usable Ethernet interfaces, or an equivalent routed-VLAN design. Keep this documentation-only lab disconnected from public networks.
  2. Use .1/25, .129/26, and .193/27 as the router's LAN gateways. Use .2/25, .130/26, and .194/27 on the respective PCs, each with its matching gateway. The required address counts include gateway interfaces.
  3. Verify each PC can ping its local gateway, then ping PCs across LANs. In the router CLI inspect interfaces and routes; use Simulation mode to observe ARP and ICMP.
  4. Deliberately configure one host with a wrong mask, then wrong gateway. Record the distinct symptom, restore settings, and retest. Verify no host uses a network or broadcast address and no subnet overlaps.
  5. Save the .pkt locally. This learning note does not ask you to publish personal progress or lab files.

Companion Anki prompts

The following prompts support subnetting practice for study references NI-NB-07 and ND-NIC-07. If using the companion FBLA package, locate the exact prompt in the named event subdeck through Anki Browse. Without the package, use these as additional recall questions. They address parts of the two objectives, not their full scope.

  • Networking Infrastructures: "What does an IP prefix length distinguish within an address?" — prefix versus host bits.
  • Networking Infrastructures: "How many conventional usable host addresses are in 192.0.2.0/26?" — ordinary host-count arithmetic.
  • Networking Infrastructures: "What is the network address of 192.0.2.77/26?" — block alignment and network address.
  • Networking Infrastructures: "The dotted-decimal subnet mask equivalent to /27 is ____." — prefix-to-mask conversion.
  • Networking Infrastructures: "On a supporting two-endpoint IPv4 point-to-point link, how many usable endpoint addresses does a /31 provide?" — scoped /31 exception.
  • Networking Infrastructures: "How many exact IPv4 addresses does 198.51.100.7/32 identify?" — single-address /32 prefix.
  • Network Design: "Why put largest subnets first when planning a VLSM allocation?" — aligned, non-overlapping allocation reasoning.

After recall, solve retrieval questions with new values and complete the lab. Record mistakes privately, then revisit the relevant prompt. Matching a card to a subskill does not certify full guide coverage, technical performance in a lab, or personal mastery.

Sources and verification

Primary standards: RFC 4632, Classless Inter-domain Routing (CIDR), https://www.rfc-editor.org/rfc/rfc4632; RFC 3021, Using 31-Bit Prefixes on IPv4 Point-to-Point Links, https://www.rfc-editor.org/rfc/rfc3021; RFC 5737, IPv4 Address Blocks Reserved for Documentation, https://www.rfc-editor.org/rfc/rfc5737. Cisco, Subnetting a Class C Network (legacy class terminology; use its arithmetic examples, not classful assumptions): https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13788-3.html
The 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 examples are documentation-only TEST-NET ranges. This flowing worked example differs from the event courses' fixed-length colored sheets. In the companion Anki package, search for tag:Networking_Infrastructures or tag:Network_Design tag:Test to locate subnet and prefix questions. Tags help navigation; they do not measure mastery or establish complete objective coverage. The linked references explain the technical background and should be consulted for their full scope and qualifications.

Sources and coverage — reference, not a study checklist

Use this reference section when checking a topic or exploring it further. It connects the 44 sheets with 160 learning objectives and rating criteria. These mappings organize the material; they are not personal scores or separate assignments. Reference IDs are course labels, not official FBLA numbering.

These are independent study materials, not official FBLA questions or a guarantee of competition results. Source notes describe the relevant sections and limits of each reference; a citation does not mean every statement has been independently verified. Consult the applicable official guidelines for event requirements.

JSON ledger · Printing this page includes the worked-example answers and rehearsal lists. Expand the ledger first to include its full records in the printout.

Show 176 coverage mappings and 121 source records

Coverage and supporting sources

  1. ni-basics-models, LAN scale and purpose · lines 5–13 · NI-NB-01 · The OSI Model
  2. ni-basics-models, SOHO, enterprise and datacenter · lines 15–24 · NI-NB-01 · The OSI Model
  3. ni-basics-models, Encapsulation across a connection · lines 29–37 · NI-NB-05 · The OSI Model, RFC 791: Internet Protocol
  4. ni-basics-models, Switch and router forwarding · lines 39–48 · NI-NB-05 · The OSI Model, RFC 791: Internet Protocol
  5. ni-basics-forwarding, OSI: physical and data link · lines 5–13 · NI-NB-02 · The OSI Model
  6. ni-basics-forwarding, OSI: network through application · lines 15–24 · NI-NB-03, NI-NB-04 · The OSI Model, RFC 791: Internet Protocol
  7. ni-basics-forwarding, Network troubleshooting model · lines 29–37 · NI-NB-02, NI-NB-03, NI-NB-04 · The OSI Model
  8. ni-basics-forwarding, LAN design in context · lines 39–48 · NI-NB-01, NI-NB-05 · The OSI Model
  9. ni-basics-addressing, From device to ISP · lines 5–13 · NI-NB-06 · RFC 791: Internet Protocol
  10. ni-basics-addressing, ISP chain and local limits · lines 15–24 · NI-NB-06 · RFC 791: Internet Protocol
  11. ni-basics-addressing, IPv4 and IPv6 formats · lines 29–37 · NI-NB-08 · RFC 791: Internet Protocol, RFC 8200: IPv6 Specification
  12. ni-basics-addressing, Subnet calculation example · lines 39–48 · NI-NB-07 · RFC 4632: Classless Inter-domain Routing, Configure IP Addresses and Unique Subnets
  13. ni-addressing-calculations, IP and MAC addressing · lines 5–13 · NI-NB-07 · RFC 791: Internet Protocol, The OSI Model
  14. ni-addressing-calculations, Subnet purpose and CIDR · lines 15–24 · NI-NB-07, NI-NB-09 · RFC 4632: Classless Inter-domain Routing, Configure IP Addresses and Unique Subnets
  15. ni-addressing-calculations, Historical IPv4 address classes · lines 29–37 · NI-NB-09 · Configure IP Addresses and Unique Subnets, RFC 4632: Classless Inter-domain Routing
  16. ni-addressing-calculations, Addressing and planning limits · lines 39–48 · NI-NB-07, NI-NB-08 · RFC 4632: Classless Inter-domain Routing, RFC 8200: IPv6 Specification
  17. ni-topologies, Peer-to-peer and client-server · lines 5–13 · NI-NTA-01 · The OSI Model
  18. ni-topologies, Choose a service architecture · lines 15–24 · NI-NTA-01 · The OSI Model
  19. ni-topologies, Star and bus topologies · lines 29–37 · NI-NTA-03, NI-NTA-04 · The OSI Model
  20. ni-topologies, Ring and mesh topologies · lines 39–48 · NI-NTA-03, NI-NTA-04 · The OSI Model
  21. ni-topology-choices, LAN, MAN and WAN scope · lines 5–13 · NI-NTA-02 · The OSI Model, RFC 791: Internet Protocol
  22. ni-topology-choices, WAN implications and scale · lines 15–24 · NI-NTA-02 · RFC 791: Internet Protocol, The OSI Model
  23. ni-topology-choices, Choose topology for requirements · lines 29–37 · NI-NTA-03, NI-NTA-04 · The OSI Model
  24. ni-topology-choices, Wireless network size options · lines 39–48 · NI-NTA-05 · IEEE 802.11 Working Group, The OSI Model
  25. ni-wireless-cloud, Cloud definition and service models · lines 5–13 · NI-NTA-06 · NIST Definition of Cloud Computing
  26. ni-wireless-cloud, Service model use and responsibility · lines 15–24 · NI-NTA-06 · NIST Definition of Cloud Computing
  27. ni-wireless-cloud, Radio frequency and attenuation · lines 29–37 · NI-NTA-08 · IEEE 802.11 Working Group
  28. ni-wireless-cloud, Wireless speed and reliability · lines 39–48 · NI-NTA-08 · IEEE 802.11 Working Group
  29. ni-wireless-performance, Cloud benefits and operating costs · lines 5–13 · NI-NTA-07 · NIST Definition of Cloud Computing
  30. ni-wireless-performance, Cloud risks and planning · lines 15–24 · NI-NTA-07 · NIST Definition of Cloud Computing
  31. ni-wireless-performance, Wireless LAN and cellular options · lines 29–37 · NI-NTA-05, NI-NTA-08 · IEEE 802.11 Working Group
  32. ni-wireless-performance, 5G system and service families · lines 39–48 · NI-NTA-09 · 5G System Overview
  33. ni-security-controls, Risk and Security Goals · lines 5–13 · NI-NS-01, NI-NS-02, NI-NS-07 · CISA phishing and DoS guidance, NIST SP 800-63-4 Digital Identity Guidelines
  34. ni-security-controls, Controls and Malware Defense · lines 15–24 · NI-NS-03, NI-NS-04, NI-NS-08 · NIST SP 800-63-4 Digital Identity Guidelines, CISA phishing and DoS guidance
  35. ni-security-controls, Availability and Attack Paths · lines 29–37 · NI-NS-05, NI-NS-06 · CISA phishing and DoS guidance
  36. ni-security-controls, Integrity, Identity, and Recovery · lines 39–48 · NI-NS-07, NI-NS-09, NI-NS-10 · NIST FIPS 180-4 Secure Hash Standard, NIST SP 800-63-4 Digital Identity Guidelines, RFC 8446 TLS 1.3, RFC 2865 RADIUS, RFC 8907 TACACS+
  37. ni-security-threats, Malware and Social Engineering · lines 5–13 · NI-NS-02, NI-NS-04, NI-NS-06 · CISA phishing and DoS guidance
  38. ni-security-threats, Resilient Defensive Layers · lines 15–24 · NI-NS-03, NI-NS-04, NI-NS-08 · CISA phishing and DoS guidance, NIST SP 800-63-4 Digital Identity Guidelines
  39. ni-security-threats, DoS Mechanics · lines 29–37 · NI-NS-05 · CISA phishing and DoS guidance
  40. ni-security-threats, Mitigation and Residual Risk · lines 39–48 · NI-NS-05, NI-NS-06, NI-NS-08 · CISA phishing and DoS guidance
  41. ni-protocols-services, File and Mail Protocols · lines 5–13 · NI-NPS-01, NI-NPS-07 · RFC 959 FTP, RFC 4217 Securing FTP with TLS, RFC 5321 SMTP
  42. ni-protocols-services, DNS, DHCP, and IP · lines 15–24 · NI-NPS-02, NI-NPS-07 · RFC 1035 DNS, RFC 2131 DHCP
  43. ni-protocols-services, Transport and Port Defaults · lines 29–37 · NI-NPS-05, NI-NPS-07 · RFC 9293 TCP, RFC 768 UDP
  44. ni-protocols-services, NAT and Secure Service Use · lines 39–48 · NI-NPS-01, NI-NPS-08 · RFC 3022 Traditional NAT, RFC 8446 TLS 1.3, RFC 4217 Securing FTP with TLS
  45. ni-protocols-routing-media, Wireless Generations and Bands · lines 5–13 · NI-NPS-03 · Cisco Wireless RF Reference Guide
  46. ni-protocols-routing-media, Wireless Range and Throughput · lines 15–24 · NI-NPS-03 · Cisco Wireless RF Reference Guide
  47. ni-protocols-routing-media, Ethernet PHY and Medium · lines 29–37 · NI-NPS-04 · Cisco Ethernet 10BaseT and 100BaseTX Cable Specs, Cisco Nexus 7000 Transceiver Specifications, CommScope Category 6A Cables
  48. ni-protocols-routing-media, Routing and Wireless Protection · lines 39–48 · NI-NPS-06, NI-NPS-09 · RFC 4271 BGP-4, RFC 2328 OSPFv2, RFC 7868 EIGRP, Cisco Catalyst 9800 WPA3 Configuration Guide
  49. ni-hardware-links, From provider to host · lines 5–13 · NI-NHC-01, NI-NHC-06 · Cisco: What Is Ethernet?
  50. ni-hardware-links, Network adapters and local traffic · lines 15–24 · NI-NHC-01, NI-NHC-02, NI-NHC-06 · Cisco: What Is Ethernet?
  51. ni-hardware-links, Copper media · lines 29–37 · NI-NHC-03 · Cisco: What Is Ethernet?
  52. ni-hardware-links, Fiber and link compatibility · lines 39–48 · NI-NHC-03, NI-NHC-04 · Cisco: What Is Ethernet?, Corning: Heat-Cure Connector, LC
  53. ni-hardware-infrastructure, Rack and blade server forms · lines 5–13 · NI-NHC-05 · Cisco UCS 5100 Series Blade Server Chassis Data Sheet
  54. ni-hardware-infrastructure, Chassis power and connectivity · lines 15–24 · NI-NHC-05, NI-NHC-06 · Cisco UCS 5100 Series Blade Server Chassis Data Sheet, Cisco: What Is Ethernet?
  55. ni-hardware-infrastructure, File and block storage · lines 29–37 · NI-NHC-07 · Microsoft Learn: Storage Spaces Direct fault tolerance
  56. ni-hardware-infrastructure, RAID and fault tolerance · lines 39–48 · NI-NHC-07 · Red Hat Enterprise Linux 9: Managing RAID, Microsoft Learn: Storage Spaces Direct fault tolerance
  57. cs-fundamentals-trust, CIA and Zero Trust · lines 5–13 · CS-SF-01, CS-SF-04, CS-SF-07 · NIST SP 800-207: Zero Trust Architecture, OWASP SQL Injection Prevention Cheat Sheet
  58. cs-fundamentals-trust, Identity, Attestation, and AAA · lines 15–24 · CS-SF-02, CS-SF-03 · NIST SP 800-63A-4: Identity Proofing and Enrollment, NIST SP 800-63B-4: Authentication and Authenticator Management, NIST CSRC Glossary: Attestation
  59. cs-fundamentals-trust, Nonrepudiation and Least Privilege · lines 29–37 · CS-SF-02, CS-SF-07 · NIST SP 800-63A-4: Identity Proofing and Enrollment, NIST SP 800-63B-4: Authentication and Authenticator Management, OWASP SQL Injection Prevention Cheat Sheet
  60. cs-fundamentals-trust, Binary, Decimal, and Hex · lines 39–48 · CS-SF-06 · RFC 6962: Certificate Transparency
  61. cs-fundamentals-controls, Proofing, Factors, and Device Trust · lines 5–13 · CS-SF-02, CS-SF-03 · NIST SP 800-63A-4: Identity Proofing and Enrollment, NIST SP 800-63B-4: Authentication and Authenticator Management, NIST CSRC Glossary: Attestation
  62. cs-fundamentals-controls, AAA, MFA, and Zero Trust · lines 15–24 · CS-SF-03, CS-SF-04 · NIST SP 800-63B-4: Authentication and Authenticator Management, NIST SP 800-207: Zero Trust Architecture
  63. cs-fundamentals-controls, Least Privilege · lines 29–37 · CS-SF-07 · OWASP SQL Injection Prevention Cheat Sheet
  64. cs-fundamentals-controls, Honeypots, Honeynets, and Honeyfiles · lines 39–48 · CS-SF-05 · NIST CSRC Glossary: Honeypot
  65. cs-threats-software, Threat Actors and Motives · lines 5–13 · CS-CTV-02 · 2026-2027 FBLA Cybersecurity Guidelines
  66. cs-threats-software, Virus Varieties and Other Malware · lines 15–24 · CS-CTV-03, CS-CTV-07 · 2026-2027 FBLA Cybersecurity Guidelines
  67. cs-threats-software, Vulnerabilities and Exploit Classes · lines 29–37 · CS-CTV-01, CS-CTV-04 · 2026-2027 FBLA Cybersecurity Guidelines, OWASP SQL Injection Prevention Cheat Sheet
  68. cs-threats-software, Reduce Exposure · lines 39–48 · CS-CTV-01, CS-CTV-04, CS-CTV-07 · OWASP SQL Injection Prevention Cheat Sheet, 2026-2027 FBLA Cybersecurity Guidelines
  69. cs-threats-human-crypto, Social Engineering · lines 5–13 · CS-CTV-05, CS-CTV-02 · 2026-2027 FBLA Cybersecurity Guidelines, NIST SP 800-63B-4: Authentication and Authenticator Management
  70. cs-threats-human-crypto, DoS and DDoS Mechanics · lines 15–24 · CS-CTV-06 · CISA: Understanding Denial-of-Service Attacks
  71. cs-threats-human-crypto, Hash Collisions and Birthday Effect · lines 29–37 · CS-CTV-08 · RFC 6962: Certificate Transparency
  72. cs-threats-human-crypto, Downgrades and Wireless Weaknesses · lines 39–48 · CS-CTV-08, CS-CTV-09 · RFC 9325: Recommendations for Secure Use of TLS/DTLS, 2026-2027 FBLA Cybersecurity Guidelines
  73. cs-design-platforms, Cloud responsibility and service models · lines 5–13 · CS-SD-01 · AWS Security and Compliance: Shared Responsibility
  74. cs-design-platforms, Cloud choices, effects, and shared duties · lines 15–24 · CS-SD-01 · AWS Security and Compliance: Shared Responsibility
  75. cs-design-platforms, Microservices and API security · lines 29–37 · CS-SD-02 · NIST SP 800-204, Security Strategies for Microservices-based Application Systems
  76. cs-design-platforms, Distributed policy and complexity · lines 39–48 · CS-SD-02 · NIST SP 800-204, Security Strategies for Microservices-based Application Systems
  77. cs-design-isolation, Segmentation and trust boundaries · lines 5–13 · CS-SD-03 · NIST SP 800-207, Zero Trust Architecture
  78. cs-design-isolation, Test segment policy and verify boundaries · lines 15–24 · CS-SD-03 · NIST SP 800-207, Zero Trust Architecture
  79. cs-design-isolation, Virtual machines and containers · lines 29–37 · CS-SD-04 · Docker Docs: What is a container?
  80. cs-design-isolation, IoT risks and safer deployment · lines 39–48 · CS-SD-04, CS-SD-05 · Docker Docs: What is a container?, NISTIR 8259A IoT Device Cybersecurity Capability Core Baseline
  81. cs-design-resilience, Backup methods and recovery · lines 5–13 · CS-SD-06 · NIST SP 800-34 Rev. 1, Contingency Planning Guide
  82. cs-design-resilience, RAID, UPS, and CIA design cases · lines 15–24 · CS-SD-06, CS-SD-07 · NIST SP 800-34 Rev. 1, Contingency Planning Guide
  83. cs-design-resilience, Security testing and architecture · lines 29–37 · CS-SD-08 · NIST SP 800-204, Security Strategies for Microservices-based Application Systems
  84. cs-design-resilience, Evidence, remediation, and retesting · lines 39–48 · CS-SD-08, CS-SD-06 · NIST SP 800-204, Security Strategies for Microservices-based Application Systems, NIST SP 800-34 Rev. 1, Contingency Planning Guide
  85. cs-data-cryptography, Symmetric and public-key cryptography · lines 5–13 · CS-NDS-01, CS-NDS-02 · NIST SP 800-57 Part 1 Rev. 5, Key Management
  86. cs-data-cryptography, Signatures, exchange, and key limits · lines 15–24 · CS-NDS-01, CS-NDS-02 · NIST SP 800-57 Part 1 Rev. 5, Key Management
  87. cs-data-cryptography, Caesar and substitution ciphers · lines 29–37 · CS-NDS-03 · Harvard CS50x: Caesar
  88. cs-data-cryptography, Hashing, blockchain, and trust limits · lines 39–48 · CS-NDS-07, CS-NDS-01 · NIST CSRC Hash Functions, NIST: Blockchain, RFC 9162: Certificate Transparency Version 2.0
  89. cs-data-access, Three states of data · lines 5–13 · CS-NDS-04 · NIST SP 800-57 Part 1 Rev. 5, Key Management
  90. cs-data-access, MAC, DAC, and RBAC models · lines 15–24 · CS-NDS-05 · NIST CSRC Glossary: Mandatory Access Control, NIST CSRC Glossary: Discretionary Access Control, NIST CSRC Glossary: Role-Based Access Control
  91. cs-data-access, Authentication and MFA · lines 29–37 · CS-NDS-06 · NIST SP 800-63-4, Digital Identity Guidelines
  92. cs-data-access, Certificates, tokens, and policy · lines 39–48 · CS-NDS-06, CS-SD-02 · NIST SP 800-63-4, Digital Identity Guidelines, NIST SP 800-204, Security Strategies for Microservices-based Application Systems
  93. cs-operations-policy, Policies and recovery plans · lines 5–13 · CS-SOM-01, CS-SOM-02 · NIST SP 800-34 Rev. 1 Contingency Planning Guide, NIST SP 800-53 Rev. 5 Controls Catalog
  94. cs-operations-policy, Recovery targets and exercise · lines 15–24 · CS-SOM-02 · NIST SP 800-34 Rev. 1 Contingency Planning Guide
  95. cs-operations-policy, Secure messaging and email · lines 29–37 · CS-SOM-05 · RFC 8446 TLS 1.3, CISA et al. Phishing Guidance: Phase One, NIST SP 1800-16 TLS Server Certificate Management
  96. cs-operations-policy, Data minimization and change control · lines 39–48 · CS-SOM-05, CS-SOM-06 · NIST SP 800-188 De-Identifying Government Datasets, NIST CSRC Glossary: Masking, NIST SP 1800-16 TLS Server Certificate Management, NIST SP 800-128 Security-Focused Configuration Management
  97. cs-operations-firewalls, Firewall inspection models · lines 5–13 · CS-SOM-03 · NIST SP 800-41 Rev. 1 Firewall Guidelines
  98. cs-operations-firewalls, NGFW, WAF, and limits · lines 15–24 · CS-SOM-03 · NIST SP 800-41 Rev. 1 Firewall Guidelines
  99. cs-operations-firewalls, ACL rules and least privilege · lines 29–37 · CS-SOM-04 · NIST SP 800-41 Rev. 1 Firewall Guidelines
  100. cs-operations-firewalls, Segmentation, tests, and operation · lines 39–48 · CS-SOM-04 · NIST SP 800-41 Rev. 1 Firewall Guidelines
  101. cs-mitigation-protocols, SSH, HTTPS, TLS, and WPA2 · lines 5–13 · CS-SPM-01 · RFC 4251 SSH Protocol Architecture, RFC 8446 TLS 1.3, NIST SP 1800-16 TLS Server Certificate Management
  102. cs-mitigation-protocols, Certificates and trust · lines 15–24 · CS-SPM-06 · RFC 5280 X.509 Certificate and CRL Profile, NIST SP 1800-16 TLS Server Certificate Management, RFC 8446 TLS 1.3
  103. cs-mitigation-protocols, IDS and IPS mechanisms · lines 29–37 · CS-SPM-02 · NIST SP 800-94 IDPS Guide
  104. cs-mitigation-protocols, Malware, phishing, and data transformation · lines 39–48 · CS-SPM-03, CS-SPM-04 · CISA et al. Phishing Guidance: Phase One, NIST CSRC Glossary: Masking, NIST SP 800-188 De-Identifying Government Datasets, SplashKit Steganography Guide
  105. cs-mitigation-practice, Current password requirements · lines 5–13 · CS-SPM-05 · NIST SP 800-63B-4 Authentication and Authenticator Management
  106. cs-mitigation-practice, Password use and protection · lines 15–24 · CS-SPM-05 · NIST SP 800-63B-4 Authentication and Authenticator Management, CISA Use Strong Passwords
  107. cs-mitigation-practice, Patches and secure change · lines 29–37 · CS-SPM-07 · NIST SP 800-128 Security-Focused Configuration Management, NIST SP 800-41 Rev. 1 Firewall Guidelines
  108. cs-mitigation-practice, Version control and pen testing · lines 39–48 · CS-SPM-07, CS-SPM-08 · NIST SP 800-128 Security-Focused Configuration Management, NIST SP 800-115 Technical Guide to Security Testing
  109. nd-installation-soho-links, SOHO edge and traffic controls · lines 5–13 · ND-NIC-01, ND-NIC-02, ND-NIC-03 · Cisco: What Is Ethernet?, Cisco: Configure IP Access Lists
  110. nd-installation-soho-links, Firewall rules and ACL behavior · lines 15–24 · ND-NIC-03, ND-NSR-05, ND-NSR-06 · Cisco: Configure IP Access Lists
  111. nd-installation-soho-links, Wireless setup and physical media · lines 29–37 · ND-NIC-04, ND-NIC-05, ND-NIC-06, ND-NIC-08, ND-NIC-12, ND-NSR-11 · Cisco: What Is Ethernet?, FBLA Network Design 2026-27 Guidelines, study guide p. 6
  112. nd-installation-soho-links, Subnet masks and loopback · lines 39–48 · ND-NIC-07, ND-NIC-08 · RFC 3021: Using 31-Bit Prefixes on IPv4 Point-to-Point Links
  113. nd-installation-physical-services, Fiber and copper selection · lines 5–13 · ND-NIC-04, ND-NIC-05 · Cisco: What Is Ethernet?, FBLA Network Design 2026-27 Guidelines, study guide p. 6
  114. nd-installation-physical-services, Rack and blade installation · lines 15–24 · ND-NIC-09 · FBLA Network Design 2026-27 Guidelines, study guide p. 6
  115. nd-installation-physical-services, Power, temperature, and UPS · lines 29–37 · ND-NIC-10, ND-NSR-02 · FBLA Network Design 2026-27 Guidelines, study guide p. 6, NIST SP 800-34 Rev. 1, Contingency Planning Guide
  116. nd-installation-physical-services, Direct, shared, and server printing · lines 39–48 · ND-NIC-11 · Microsoft Learn: Print and Document Services Architecture
  117. nd-security-access-platforms, Threat defenses and least privilege · lines 5–13 · ND-NSR-04, ND-NSR-05, ND-NSR-06 · Cisco: Configure IP Access Lists, CISA Zero Trust Maturity Model
  118. nd-security-access-platforms, Zero Trust and network admission · lines 15–24 · ND-NSR-06, ND-NSR-07, ND-NSR-08 · CISA Zero Trust Maturity Model
  119. nd-security-access-platforms, BitLocker and directory identity · lines 29–37 · ND-NSR-06, ND-NSR-09 · Microsoft Learn: BitLocker Overview, Microsoft Learn: Active Directory Domain Services overview
  120. nd-security-access-platforms, SELinux mandatory access control · lines 39–48 · ND-NSR-09 · Red Hat Enterprise Linux 9: Using SELinux
  121. nd-security-recovery, Disaster recovery planning · lines 5–13 · ND-NSR-01, ND-NSR-02 · NIST SP 800-34 Rev. 1, Contingency Planning Guide
  122. nd-security-recovery, Backup types and restore assurance · lines 15–24 · ND-NSR-02, ND-NSR-03 · NIST SP 800-34 Rev. 1, Contingency Planning Guide
  123. nd-security-recovery, IDS, IPS, updates, and response · lines 29–37 · ND-NSR-04, ND-NSR-05, ND-NSR-10 · Cisco: Configure IP Access Lists, CISA Zero Trust Maturity Model
  124. nd-security-recovery, Wireless authentication and ACLs · lines 39–48 · ND-NSR-06, ND-NSR-08, ND-NSR-11 · CISA Zero Trust Maturity Model, Cisco: Configure IP Access Lists
  125. nd-administration-maintenance, Maintenance and recovery · lines 5–13 · ND-NA-01, ND-NA-06 · FBLA 2026-27 Network Design Guidelines, Ubuntu Server documentation
  126. nd-administration-maintenance, Accounts and permissions · lines 15–24 · ND-NA-02, ND-NA-10 · FBLA 2026-27 Network Design Guidelines, What is Windows Server?, Ubuntu Server documentation, Microsoft print command reference, Active Directory Domain Services overview
  127. nd-administration-maintenance, SNMP and management data · lines 29–37 · ND-NA-03, ND-NA-08 · RFC 3411: SNMP Management Framework Architecture, RFC 3414: SNMPv3 User-based Security Model, RFC 3418: SNMP Management Information Base, RFC 1901: Community-based SNMPv2, CISA: Reducing the Risk of SNMP Abuse
  128. nd-administration-maintenance, Traffic baselines and alerts · lines 39–48 · ND-NA-07, ND-NA-08, ND-NA-09 · FBLA 2026-27 Network Design Guidelines, RFC 3418: SNMP Management Information Base, Microsoft Azure Load Balancer overview, Azure Load Balancer distribution modes, Azure Load Balancer health probes
  129. nd-administration-troubleshooting, Fault isolation and symptoms · lines 5–13 · ND-NA-04, ND-NA-07 · FBLA 2026-27 Network Design Guidelines, Microsoft ping command reference, Microsoft ipconfig command reference, Configure IP Addresses and Unique Subnets for New Users
  130. nd-administration-troubleshooting, Read local configuration · lines 15–24 · ND-NA-04, ND-NA-05 · Microsoft ipconfig command reference, Microsoft ping command reference
  131. nd-administration-troubleshooting, Path tools and limits · lines 29–37 · ND-NA-05, ND-NA-04 · Microsoft ping command reference, Microsoft tracert command reference
  132. nd-administration-troubleshooting, Evidence and asset records · lines 39–48 · ND-NA-07, ND-NA-10, ND-NA-08 · FBLA 2026-27 Network Design Guidelines, RFC 3418: SNMP Management Information Base, Microsoft print command reference
  133. nd-planning-requirements, Translate business requirements · lines 5–13 · ND-NP-01, ND-NP-08 · FBLA 2026-27 Network Design Guidelines, Configure IP Addresses and Unique Subnets for New Users, Microsoft Azure Load Balancer overview
  134. nd-planning-requirements, Network scope and physical scale · lines 15–24 · ND-NP-01, ND-NP-02 · FBLA 2026-27 Network Design Guidelines, Configure IP Addresses and Unique Subnets for New Users
  135. nd-planning-requirements, Topology and failure domains · lines 29–37 · ND-NP-03, ND-NP-04, ND-NP-09 · FBLA 2026-27 Network Design Guidelines, Configure IP Addresses and Unique Subnets for New Users, Microsoft Azure Load Balancer overview
  136. nd-planning-requirements, Windows Server or Linux · lines 39–48 · ND-NP-05 · FBLA 2026-27 Network Design Guidelines, What is Windows Server?, Ubuntu Server documentation, What is Linux?
  137. nd-planning-tradeoffs, Peer-to-peer or client-server · lines 5–13 · ND-NP-06 · FBLA 2026-27 Network Design Guidelines, What is Windows Server?, Ubuntu Server documentation
  138. nd-planning-tradeoffs, Cloud service benefits and costs · lines 15–24 · ND-NP-07, ND-NP-08 · FBLA 2026-27 Network Design Guidelines, What is Windows Server?, Ubuntu Server documentation, Microsoft Azure Load Balancer overview, Shared responsibility in the cloud
  139. nd-planning-tradeoffs, Cost, throughput, and availability · lines 29–37 · ND-NP-08, ND-NP-09 · FBLA 2026-27 Network Design Guidelines, Microsoft Azure Load Balancer overview, Configure IP Addresses and Unique Subnets for New Users
  140. nd-planning-tradeoffs, Service targets and design choice · lines 39–48 · ND-NP-01, ND-NP-07, ND-NP-08, ND-NP-09 · FBLA 2026-27 Network Design Guidelines, Microsoft Azure Load Balancer overview, What is Windows Server?, Ubuntu Server documentation
  141. nd-protocols-environments, Network Scale and Work Models · lines 5–13 · ND-NPSA-01, ND-NPSA-06, ND-NPSA-07 · FBLA Network Design 2026-27 Individual Guidelines, Cisco: Configure IP Addresses and Unique Subnets
  142. nd-protocols-environments, Devices and Trust Boundaries · lines 15–24 · ND-NPSA-02, ND-NPSA-05, ND-NPSA-07 · FBLA Network Design 2026-27 Individual Guidelines, Cisco: Configure IP Addresses and Unique Subnets
  143. nd-protocols-environments, Connectivity and Attack Patterns · lines 29–37 · ND-NPSA-03, ND-NPSA-04 · FBLA Network Design 2026-27 Individual Guidelines
  144. nd-protocols-environments, VPN and Authorized Capture · lines 39–48 · ND-NPSA-02 · FBLA Network Design 2026-27 Individual Guidelines
  145. nd-protocols-troubleshooting, Layers and Addressing Roles · lines 5–13 · ND-NPSA-08, ND-NPSA-09 · FBLA Network Design 2026-27 Individual Guidelines, Cisco: Configure IP Addresses and Unique Subnets, IETF RFC 2131: Dynamic Host Configuration Protocol
  146. nd-protocols-troubleshooting, TCP, UDP, DHCP, and Printed SMP · lines 15–24 · ND-NPSA-09 · FBLA Network Design 2026-27 Individual Guidelines, IETF RFC 9293: Transmission Control Protocol, IETF RFC 2131: Dynamic Host Configuration Protocol
  147. nd-protocols-troubleshooting, Topology and Reachability Tests · lines 29–37 · ND-NPSA-10, ND-NPSA-11 · FBLA Network Design 2026-27 Individual Guidelines, Cisco: Configure IP Addresses and Unique Subnets
  148. nd-protocols-troubleshooting, Layered Physical Diagnosis · lines 39–48 · ND-NPSA-11 · FBLA Network Design 2026-27 Individual Guidelines, Cisco: Configure IP Addresses and Unique Subnets, IETF RFC 2131: Dynamic Host Configuration Protocol
  149. nd-roleplay-analysis, Define the Problem and Criteria · lines 5–13 · ND-RP-01, ND-RP-04 · FBLA Network Design 2026-27 Individual Guidelines
  150. nd-roleplay-analysis, Compare Real Alternatives · lines 15–24 · ND-RP-02, ND-RP-04 · FBLA Network Design 2026-27 Individual Guidelines
  151. nd-roleplay-analysis, Plan Feasible Implementation · lines 29–37 · ND-RP-03, ND-RP-04 · FBLA Network Design 2026-27 Individual Guidelines
  152. nd-roleplay-analysis, Connect Design to Business Value · lines 39–48 · ND-RP-03, ND-RP-04 · FBLA Network Design 2026-27 Individual Guidelines
  153. nd-roleplay-delivery, Organize a Decision Briefing · lines 5–13 · ND-RP-05, ND-RP-01, ND-RP-02, ND-RP-03 · FBLA Network Design 2026-27 Individual Guidelines
  154. nd-roleplay-delivery, Communicate with Confidence · lines 15–24 · ND-RP-06, ND-RP-05, ND-RP-04 · FBLA Network Design 2026-27 Individual Guidelines
  155. nd-roleplay-delivery, Answer Judges Completely · lines 29–37 · ND-RP-07, ND-RP-04 · FBLA Network Design 2026-27 Individual Guidelines
  156. nd-roleplay-delivery, Rubric and Practice Boundaries · lines 39–48 · ND-RP-01, ND-RP-02, ND-RP-03, ND-RP-04, ND-RP-05, ND-RP-06, ND-RP-07 · FBLA Network Design 2026-27 Individual Guidelines
  157. sp-discovery-opening, Open with relevance · lines 5–13 · SP-R-01 · FBLA 2026-27 Sales Presentation Guidelines, HubSpot Academy Inbound Sales Certification Course
  158. sp-discovery-opening, Find the need · lines 15–24 · SP-R-02 · HubSpot Academy Inbound Sales Certification Course
  159. sp-discovery-opening, Map people and priorities · lines 29–37 · SP-R-02 · HubSpot Academy Inbound Sales Certification Course
  160. sp-discovery-opening, Confirm before advising · lines 39–48 · SP-R-02 · HubSpot Academy Inbound Sales Certification Course
  161. sp-product-value-evidence, Explain product fit · lines 5–13 · SP-R-03 · FBLA 2026-27 Sales Presentation Guidelines, HubSpot Academy Inbound Sales Certification Course
  162. sp-product-value-evidence, Demonstrate accurately · lines 15–24 · SP-R-03 · FBLA 2026-27 Sales Presentation Guidelines
  163. sp-product-value-evidence, Substantiate claims · lines 29–37 · SP-R-03 · FTC Advertising FAQ: A Guide for Small Business
  164. sp-product-value-evidence, Calculate cost and return · lines 39–48 · SP-R-03 · FTC Advertising FAQ: A Guide for Small Business
  165. sp-objections-suggestion-close, Listen and clarify · lines 5–13 · SP-R-04 · HubSpot Academy Inbound Sales Certification Course
  166. sp-objections-suggestion-close, Respond and check · lines 15–24 · SP-R-04 · HubSpot Academy Inbound Sales Certification Course, FTC Advertising FAQ: A Guide for Small Business
  167. sp-objections-suggestion-close, Suggest related value · lines 29–37 · SP-R-05 · FBLA 2026-27 Sales Presentation Guidelines, HubSpot Academy Inbound Sales Certification Course
  168. sp-objections-suggestion-close, Close as a clear choice · lines 39–48 · SP-R-06 · HubSpot Academy Inbound Sales Certification Course, FBLA 2026-27 Sales Presentation Guidelines
  169. sp-relationships-organization, Build a reliable relationship · lines 5–13 · SP-R-07 · HubSpot Academy Inbound Sales Certification Course
  170. sp-relationships-organization, Organize buyer-centered content · lines 15–24 · SP-R-08 · Toastmasters: How to Overcome Your Fear of Public Speaking, HubSpot Academy Inbound Sales Certification Course
  171. sp-relationships-organization, Manage time and transitions · lines 29–37 · SP-R-08 · FBLA 2026-27 Sales Presentation Guidelines, Toastmasters: How to Overcome Your Fear of Public Speaking
  172. sp-relationships-organization, Coordinate team handoffs · lines 39–48 · SP-R-08 · FBLA 2026-27 Sales Presentation Guidelines, Toastmasters: How to Overcome Your Fear of Public Speaking
  173. sp-delivery-protocols, Deliver clearly and responsively · lines 5–13 · SP-R-09 · FBLA 2026-27 Sales Presentation Guidelines, Toastmasters: How to Overcome Your Fear of Public Speaking
  174. sp-delivery-protocols, Answer questions completely · lines 15–24 · SP-R-10 · FBLA 2026-27 Sales Presentation Guidelines, HubSpot Academy Inbound Sales Certification Course
  175. sp-delivery-protocols, Know the spoken rating sheet · lines 29–37 · SP-R-09, SP-R-10, SP-P-01 · FBLA 2026-27 Sales Presentation Guidelines
  176. sp-delivery-protocols, Follow event rules and ownership · lines 39–48 · SP-P-01 · FBLA 2026-27 Sales Presentation Guidelines

Source ledger with reading scope

  • Networking foundations: The OSI Model · fetched · Read overview and layer descriptions: seven-layer conceptual troubleshooting model, including functions of application through physical layers; modern Internet does not strictly map to OSI.
  • Networking foundations: RFC 791: Internet Protocol · fetched · Read abstract and introductory IP operation material on connectionless datagrams, addressing, routing and gateways.
  • Networking foundations: RFC 8200: IPv6 Specification · fetched · Read specification overview and IPv6 addressing/header material; grounds IPv6 protocol facts.
  • Networking foundations: RFC 4632: Classless Inter-domain Routing · fetched · Read abstract and prefix notation sections: explicit prefix lengths and classless address assignment/aggregation.
  • Networking foundations: Configure IP Addresses and Unique Subnets · fetched · Read IP/subnet definitions, dotted decimal explanation and subnet examples; older tutorial, classful assumptions are historical only.
  • Networking foundations: NIST Definition of Cloud Computing · fetched · Read NIST SP 800-145 abstract and definition: on-demand shared configurable resources, rapid provisioning/release, measured service and IaaS/PaaS/SaaS models.
  • Networking foundations: 5G System Overview · fetched · Read 3GPP introduction, system architecture and service descriptions: UE, radio access network and core; eMBB, massive IoT and critical/URLLC goals. Goals are not universal service guarantees.
  • Networking foundations: IEEE 802.11 Working Group · fetched · Read working-group scope describing WLAN MAC and PHY standardization; this does not support universal range or throughput figures.
  • Network Security and Protocols: CommScope Category 6A Cables · fetched · Read the manufacturer explanation that Cat 6A structured cabling supports 10 Gigabit Ethernet channels up to 100 m. This is conditional channel capability, not a guarantee for every device, optic, or installation.
  • Network Security and Protocols: CISA phishing and DoS guidance · fetched · DoS flooding, overload, botnet/distributed effects; phishing page also fetched for warning signs.
  • Network Security and Protocols: NIST SP 800-63-4 Digital Identity Guidelines · fetched · Publication scope describes proofing, authentication, authenticators, federation and assertions; technical detail here limited to those concepts.
  • Network Security and Protocols: NIST FIPS 180-4 Secure Hash Standard · fetched · Digests detect changed messages; hash standard publication overview.
  • Network Security and Protocols: RFC 4271 BGP-4 · fetched · Abstract and status: inter-AS reachability, AS paths, policy, CIDR; Standards Track.
  • Network Security and Protocols: RFC 2328 OSPFv2 · fetched · Abstract: link-state, intra-AS topology database, shortest-path tree, areas and equal-cost paths.
  • Network Security and Protocols: RFC 7868 EIGRP · fetched · Abstract/status: distance-vector basis, DUAL, informational not Standards Track.
  • Network Security and Protocols: RFC 959 FTP · fetched · FTP purpose and control/data transfer model.
  • Network Security and Protocols: RFC 4217 Securing FTP with TLS · fetched · FTP TLS extension and security/authentication mechanisms; distinguishes FTPS from SFTP.
  • Network Security and Protocols: RFC 5321 SMTP · fetched · SMTP electronic mail transport and submission role.
  • Network Security and Protocols: RFC 1035 DNS · fetched · DNS query/response and record formats.
  • Network Security and Protocols: RFC 2131 DHCP · fetched · DHCP address allocation and host configuration framework.
  • Network Security and Protocols: RFC 9293 TCP · fetched · TCP transport protocol specification.
  • Network Security and Protocols: RFC 768 UDP · fetched · Datagram service; delivery and duplicate protection not guaranteed.
  • Network Security and Protocols: RFC 3022 Traditional NAT · fetched · Address translation and NAPT address/port mapping; informational RFC.
  • Network Security and Protocols: RFC 8446 TLS 1.3 · fetched · TLS channel design goal against eavesdropping, tampering and message forgery.
  • Network Security and Protocols: RFC 2865 RADIUS · fetched · Read abstract and operation: NAS exchanges authentication, authorization and configuration with shared server; assigned UDP port 1812; limitations noted.
  • Network Security and Protocols: RFC 8907 TACACS+ · fetched · Read introduction: centralized device administration; authentication, authorization and accounting are separate; TCP port 49; informational status and deployment cautions.
  • Network Security and Protocols: IANA Service Name and Port Number Registry · fetched · Read the CSV rows for TCP 21 FTP control, 22 SSH, 25 SMTP, TCP/UDP 53 domain, UDP 67 bootps and 68 bootpc, TCP 80 HTTP, UDP 123 NTP, TCP 443 HTTPS, TCP 465 submissions, and TCP 587 submission. Registry reservations do not imply every service uses all registered transports or that a port guarantees security.
  • Network Security and Protocols: Cisco Ethernet Auto-Negotiation Guide · fetched · Operational 10/100/1000 Ethernet negotiation and NIC/switch compatibility; not a normative distance table.
  • Network Security and Protocols: Cisco Wireless RF Reference Guide · fetched · Read Wi-Fi generations table, band discussions, RF fundamentals; table maximum link rates are conditional and not throughput promises.
  • Network Security and Protocols: Cisco Ethernet Auto-Negotiation Guide · fetched · Read operational Ethernet speed/duplex negotiation and compatibility tables; this source does not establish PHY distances.
  • Network Security and Protocols: Cisco Catalyst 9800 WPA3 Configuration Guide · fetched · WPA3 SAE exchange, online/offline guessing resistance, AP/client compatibility and supported configurations.
  • Network Security and Protocols: Cisco Ethernet 10BaseT and 100BaseTX Cable Specs · fetched · Read tables showing Ethernet PHY media, 10BaseT 100m and 100BaseTX 100m segment; legacy guide, use only for named variants.
  • Network Security and Protocols: Cisco Nexus 7000 Transceiver Specifications · fetched · Read transceiver tables; optical reach varies with model, fiber grade, wavelength and loss budget.
  • Network Hardware and Connectivity: Red Hat Enterprise Linux 9: Managing RAID · fetched · Read overview and section 18.3 definitions for striping, mirroring, parity, RAID 6 recovery after any two drive losses, and Linux MD RAID 10 variants. The notes qualify the conventional four-disk mirrored-pair RAID 10 layout; Linux MD can support other layouts, including three drives.
  • Network Hardware and Connectivity: FBLA Networking Infrastructures 2026-27, pp. 5-6 · fetched · Read the current Network Hardware and Connectivity objectives; establishes assignment scope, not the technical explanations.
  • Network Hardware and Connectivity: Cisco: What Is Ethernet? · fetched · Read Ethernet media, IEEE 802.3, Layer 1/2, MAC frames and switching, router packet forwarding between networks, Ethernet cabling and power. Cisco learning explanation; not a universal reach or product compatibility specification.
  • Network Hardware and Connectivity: Cisco UCS 5100 Series Blade Server Chassis Data Sheet · fetched · Read chassis capacity, shared power supplies, hot-swappable fans, fabric/midplane, redundancy options and integrated management details; this is one specific blade implementation, not a universal blade design.
  • Network Hardware and Connectivity: Corning: Heat-Cure Connector, LC · fetched · Read manufacturer product description and variants: LC connectors offered for single-mode and multimode fiber, with distinct fiber categories and UPC/APC options. Illustrates that connector family alone does not establish optics compatibility.
  • Network Hardware and Connectivity: Microsoft Learn: Storage Spaces Direct fault tolerance · fetched · Read mirror and parity mechanisms, single/dual parity tradeoffs and failure tolerance tables. Storage Spaces Direct is a software-defined clustered implementation; used only to explain mirror/parity concepts, not as a claim that its server counts equal disk counts for RAID.
  • Cybersecurity Fundamentals and Threats: 2026-2027 FBLA Cybersecurity Guidelines · fetched · Read study guide pages 5-6 for current scope and wording of assigned Security Fundamentals and Cyber Threats and Vulnerabilities objectives; used only to establish scope, not technical mechanisms.
  • Cybersecurity Fundamentals and Threats: NIST SP 800-63A-4: Identity Proofing and Enrollment · fetched · Read identity proofing overview and passages on resolution, evidence/attribute validation, verification of rightful owner, enrollment, and assurance limits.
  • Cybersecurity Fundamentals and Threats: NIST SP 800-63B-4: Authentication and Authenticator Management · fetched · Read authentication definition, AAL summaries, distinct-factor MFA, authenticator control, phishing resistance, OTP and out-of-band limitations.
  • Cybersecurity Fundamentals and Threats: NIST CSRC Glossary: Attestation · fetched · Read definition: digitally sign hardware-secured measurements and have requester validate signature and measurements; glossary term context is SP 1800-19B.
  • Cybersecurity Fundamentals and Threats: NIST CSRC Glossary: Honeypot · fetched · Read definition of an attractive system/resource for potential intruders. NIST glossary term identifies resource examples, not a complete taxonomy of honeynet or honeyfile.
  • Cybersecurity Fundamentals and Threats: NIST SP 800-207: Zero Trust Architecture · fetched · Read official abstract: no implicit trust based solely on physical/network location; ZTA focuses on users, assets, and resources. Full publication not read.
  • Cybersecurity Fundamentals and Threats: OWASP SQL Injection Prevention Cheat Sheet · fetched · Read SQL injection mechanism, parameterized query, allow-list structural choices, and least-privilege passages.
  • Cybersecurity Fundamentals and Threats: CISA: Understanding Denial-of-Service Attacks · fetched · Read DoS flood and SYN-flood mechanics, botnet-based DDoS, compromised devices as victims, monitoring, and response. Page is explicitly archived/outdated; use for basic mechanism only.
  • Cybersecurity Fundamentals and Threats: RFC 9325: Recommendations for Secure Use of TLS/DTLS · fetched · Read TLS version/fallback guidance: TLS 1.2 clients must not fall back to earlier deprecated versions; document recommends modern secure deployment and notes guidance is point-in-time.
  • Cybersecurity Fundamentals and Threats: RFC 6962: Certificate Transparency · fetched · Read hash-tree definitions: SHA-256 digests, distinct leaf/node prefixes for second-preimage resistance, and proof construction. Does not state birthday bound; used for hash/digest context only.
  • Cybersecurity Design and Data Protection: NIST SP 800-204, Security Strategies for Microservices-based Application Systems · fetched · Read pp. 1, 6-8, 15-16, 17-19, 21-24, 25-30, 33-36. Microservice API security features, identity/access management, discovery, secure communications, monitoring, gateway/service mesh, disadvantages, threats and strategies.
  • Cybersecurity Design and Data Protection: AWS Security and Compliance: Shared Responsibility · fetched · Read shared responsibility passages: AWS security of the cloud and customer security in the cloud; AWS manages facilities/hardware while customer retains control of content, platforms, applications, systems, and networks.
  • Cybersecurity Design and Data Protection: Docker Docs: What is a container? · fetched · Read explanation and Containers versus VMs: containers are isolated processes sharing a kernel; a VM includes an operating system and its own kernel; VMs and containers may be used together.
  • Cybersecurity Design and Data Protection: NIST CSRC Hash Functions · fetched · Read hash definition mapping arbitrary-length messages to fixed-length digests, approved FIPS hash families, stated expected hash properties, and collision-resistance strength table.
  • Cybersecurity Design and Data Protection: NIST: Blockchain · fetched · Read NIST description of shared tamper-evident/tamper-resistant ledgers, blocks cryptographically linked to prior blocks, replicated nodes, validation and consensus; NIST notes different implementations and research into security guarantees.
  • Cybersecurity Design and Data Protection: RFC 9162: Certificate Transparency Version 2.0 · fetched · Read Merkle-tree passages: efficient inclusion and consistency proofs, append-only log property, and detecting log misbehavior. This is a concrete hash-tree integrity mechanism, not evidence that ledger inputs are true.
  • Cybersecurity Design and Data Protection: NIST SP 800-57 Part 1 Rev. 5, Key Management · fetched · Read publication description on key types, security services, cryptographic keying material protection and key-management practices. Landing metadata is used only for those stated scopes.
  • Cybersecurity Design and Data Protection: NIST SP 800-63-4, Digital Identity Guidelines · fetched · Read publication description identifying identity proofing, authentication, enrollment, authenticators, management, authentication protocols, federation, and assertions; use only for these scope distinctions.
  • Cybersecurity Design and Data Protection: NIST SP 800-207, Zero Trust Architecture · fetched · Read NIST summary: no implicit trust based solely on network location or asset ownership; supports explicit per-resource access framing and segmentation discussion.
  • Cybersecurity Design and Data Protection: NIST SP 800-34 Rev. 1, Contingency Planning Guide · fetched · Read publication overview describing contingency planning process, plan development, organizational resiliency, and relationship to incident/emergency plans; not used as evidence for backup copy mechanics.
  • Cybersecurity Design and Data Protection: NISTIR 8259A IoT Device Cybersecurity Capability Core Baseline · fetched · Read NIST abstract: baseline device capabilities support common controls protecting devices, device data, systems, and ecosystems; detailed capability descriptions not retrieved.
  • Cybersecurity Design and Data Protection: NIST CSRC Glossary: Mandatory Access Control · fetched · Read glossary definition: uniform policy across subjects/objects constrains information passing, privilege delegation, security-attribute changes, and access-rule changes, with trusted-subject exceptions.
  • Cybersecurity Design and Data Protection: NIST CSRC Glossary: Discretionary Access Control · fetched · Read glossary definition: object owner or authorized controller decides which subjects receive which object access rights.
  • Cybersecurity Design and Data Protection: NIST CSRC Glossary: Role-Based Access Control · fetched · Read glossary definition: user access follows role-linked authorizations typically reflecting organizational functions; role hierarchies may inherit permissions.
  • Cybersecurity Design and Data Protection: RFC 20: ASCII format for Network Interchange · fetched · Read for ASCII character encoding context only; not evidence for substitution-cipher security.
  • Cybersecurity Design and Data Protection: Harvard CS50x: Caesar · fetched · Read Problem to Solve and the rotation formula (p+k) modulo 26, wraparound and reverse-shift examples, plus the explicit warning that this is not secure by modern standards. The ATTACK example is original arithmetic independently checked from that rule.
  • Security Operations and Threat Mitigation: NIST SP 800-34 Rev. 1 Contingency Planning Guide · fetched · Read Executive Summary and Ch. 1-2 (PDF pp. 13-26): plan distinctions, contingency process, BCP/DRP, resilience. Also inspected Ch. 3 TOC; detailed RTO/RPO passages not separately retrieved.
  • Security Operations and Threat Mitigation: NIST SP 800-41 Rev. 1 Firewall Guidelines · fetched · Read PDF pp. 1-18: firewall policy, packet filtering, stateful inspection, application firewalls, proxy and WAF overview; allowed traffic, specific rules, testing and management.
  • Security Operations and Threat Mitigation: NIST SP 800-128 Security-Focused Configuration Management · fetched · Read PDF pp. 48-53, Sec. 3.3: access restrictions, requested/evaluated/tested/approved changes, verify deployment, emergency change, impact analysis, retain old baseline for rollback.
  • Security Operations and Threat Mitigation: NIST SP 800-63B-4 Authentication and Authenticator Management · fetched · Read normative password and authenticator requirements, Sec. 3.1.1 and AAL summary: 15-character single-factor and 8-character MFA-only minimums, blocklist, composition, manager, rate limiting.
  • Security Operations and Threat Mitigation: RFC 8446 TLS 1.3 · fetched · Read Sections 1-2: secure-channel goals, handshake negotiation and authentication, record protection, and weaker replay/forward-secrecy properties of 0-RTT.
  • Security Operations and Threat Mitigation: RFC 4251 SSH Protocol Architecture · fetched · Read Sections 1, 4.1, 4.4 and 9: SSH transport properties, host-key verification, client authentication, and configuration policy.
  • Security Operations and Threat Mitigation: RFC 5280 X.509 Certificate and CRL Profile · fetched · Read Sections 3.1-3.3: CA-signed key-to-subject binding, certification paths, trust, CRLs and revocation limits.
  • Security Operations and Threat Mitigation: NIST SP 1800-16 TLS Server Certificate Management · fetched · Read certificate background and issuance process: server identity, key-pair CSR, RA review, CA issuance, chain validation, expiry, private-key risks.
  • Security Operations and Threat Mitigation: NIST SP 800-94 IDPS Guide · fetched · Read Executive Summary and Ch. 2: IDS/IPS purposes and signature, anomaly, and stateful protocol detection methodologies. Document dates from 2007; platform-neutral concepts only.
  • Security Operations and Threat Mitigation: NIST SP 800-115 Technical Guide to Security Testing · fetched · Read Executive Summary, Ch. 1-2, and targeted Ch. 5-7 passages: assessment planning, risk, scope, execution/data handling, pen-test phases/logistics, reporting, and ROE appendix identified in TOC.
  • Security Operations and Threat Mitigation: NIST CSRC Glossary: Masking · fetched · Read definition: removing/replacing a field in a way that does not preserve analytic utility; examples include asterisks or random pseudonyms.
  • Security Operations and Threat Mitigation: NIST SP 800-188 De-Identifying Government Datasets · fetched · Read summary of de-identification goals, risk evaluation, removing identifiers, transforming quasi-identifiers, synthetic data, and warning that simple masking may not suffice.
  • Security Operations and Threat Mitigation: CISA et al. Phishing Guidance: Phase One · fetched · Read pp. 3-12: phishing definitions, email/link/attachment lures, filtering, least privilege, patching, training, incident response, and reporting.
  • Security Operations and Threat Mitigation: CISA Use Strong Passwords · fetched · Read guidance on unique passwords, password managers, long/random passwords, and MFA.
  • Security Operations and Threat Mitigation: NIST SP 800-53 Rev. 5 Controls Catalog · fetched · Read publication overview and control families. Catalog scope supports governance context; no individual control text claimed.
  • Security Operations and Threat Mitigation: SplashKit Steganography Guide · fetched · Read guide explaining carrier media and image LSB embedding; explicitly distinguishes hiding message existence from encryption and says combine with encryption for sensitive content.
  • Security Operations and Threat Mitigation: CISA Securing Wireless Networks · recommended · Not fetched; no claim depends on this route.
  • Security Operations and Threat Mitigation: FBLA 2026-27 Cybersecurity objectives inventory · recommended · Local objective inventory read; official PDF not fetched in this pass. Establishes assigned objective scope only, not technical evidence.
  • Network Installation, Security, and Recovery: FBLA Network Design 2026-27 Guidelines, study guide p. 6 · fetched · Read the current study-guide objective descriptions for installation/configuration and network security/recovery; establishes scope, not mechanisms.
  • Network Installation, Security, and Recovery: Cisco: Configure IP Access Lists · fetched · Read ACL matching, ordered evaluation, implicit deny, direction/application, traffic criteria, and stateful inspection discussion. Platform-specific examples; not a universal firewall configuration recipe.
  • Network Installation, Security, and Recovery: RFC 3021: Using 31-Bit Prefixes on IPv4 Point-to-Point Links · fetched · Read sections 1-3 and deployment notes: /31 uses both addresses as hosts only on point-to-point links; both endpoints must support it.
  • Network Installation, Security, and Recovery: Microsoft Learn: BitLocker Overview · fetched · Read volume-encryption purpose, TPM/offline integrity role, startup protection, and recovery-key backup behavior; warns encryption without protected keys is insufficient.
  • Network Installation, Security, and Recovery: Microsoft Learn: Active Directory Domain Services overview · fetched · Read directory objects, centralized account access, authentication, access control, policy administration, and replication. Distinguishes directory function from DNS naming.
  • Network Installation, Security, and Recovery: Red Hat Enterprise Linux 9: Using SELinux · fetched · Read guide introduction: SELinux implements MAC; policy constrains how users/processes interact with files and devices. Platform-specific Linux control, not antivirus.
  • Network Installation, Security, and Recovery: CISA Zero Trust Maturity Model · fetched · Read current model overview: per-request least-privilege decisions, location-centric to data-centric shift, visibility and granular enforcement.
  • Network Installation, Security, and Recovery: Microsoft Learn: Print and Document Services Architecture · fetched · Read print queue, client/server sharing, driver and spooler architecture. Windows Server 2012-era source; used only for durable queue/host dependency concepts, not current driver deployment advice.
  • Network Installation, Security, and Recovery: NIST SP 800-34 Rev. 1, Contingency Planning Guide · fetched · Read publication overview and planning purpose/process metadata. Detailed operational claims below are kept to general plan, backup, recovery-test concepts; document is 2010 guidance, not current vendor prescription.
  • Network Installation, Security, and Recovery: Cisco: What Is Ethernet? · fetched · Read Ethernet/IEEE 802.3, frame switching and MAC learning versus router IP forwarding, and physical media overview; not used for universal cable reach.
  • Network Installation, Security, and Recovery: IEEE 802.11 Working Group and amendments · fetched · Verified IEEE 802.11 is the Wireless LAN Working Group standard family; IEEE-SA amendment pages identify 802.11ax-2021 and 802.11be-2024. No universal device rate or range inferred.
  • Network administration and planning: FBLA 2026-27 Network Design Guidelines · fetched · Read study guide pp. 6-7 to verify Network Administration and Network Planning objective scope.
  • Network administration and planning: RFC 3411: SNMP Management Framework Architecture · fetched · Read §§1-2 and 3.1-3.2: manager and agent applications, managed objects/MIB, operations, notifications, and the distinction between message security and access control.
  • Network administration and planning: RFC 3414: SNMPv3 User-based Security Model · fetched · Read §§1.1-1.4 and 2: authentication provides integrity and user authentication, privacy protects payload disclosure and requires authentication, and timeliness limits replay. The document's example MD5/DES algorithms are historic, not current recommendations.
  • Network administration and planning: RFC 3418: SNMP Management Information Base · fetched · Read §§1-2, including system identity/location objects, SNMP counters, and notifications; used to explain management data and monitoring evidence.
  • Network administration and planning: RFC 1901: Community-based SNMPv2 · fetched · Read §§2-3: agents, managers, MIB objects, and SNMPv2c's community-based administrative framework. Historic experimental RFC; used only for community model context.
  • Network administration and planning: CISA: Reducing the Risk of SNMP Abuse · fetched · Read community-string exposure, SNMPv3 authPriv, MIB-view/ACL and least-privilege guidance. Dated 2017; confirm current device and cryptographic support.
  • Network administration and planning: Microsoft ping command reference · fetched · Read command description, examples, and parameters: ICMP Echo testing, name-versus-address comparison, and timeout behavior.
  • Network administration and planning: Microsoft tracert command reference · fetched · Read TTL-based path discovery and examples; intermediate routers can omit Time Exceeded responses, producing asterisks without proving a forwarding failure.
  • Network administration and planning: Microsoft ipconfig command reference · fetched · Read /all, /renew, /flushdns, and remarks: adapter configuration, DHCP renewal conditions, and local DNS-cache scope.
  • Network administration and planning: Microsoft Azure Load Balancer overview · fetched · Read Layer 4 flow distribution, backend pools, rules, health probes, monitoring, and availability overview. These are Azure implementation examples, not universal behavior for every load balancer.
  • Network administration and planning: Azure Load Balancer distribution modes · fetched · Read five-tuple hash distribution and two-/three-tuple client-IP affinity modes; same-client affinity can skew distribution, particularly where flow diversity is limited. Azure-specific implementation.
  • Network administration and planning: Azure Load Balancer health probes · fetched · Read TCP/HTTP probe operations, configured response/threshold behavior, unhealthy backend handling, and health-signal design guidance; implementation details vary by SKU and product.
  • Network administration and planning: Shared responsibility in the cloud · fetched · Read service-model responsibility matrix and retained customer duties for data, accounts, and access; Microsoft-specific guidance and contract terms govern.
  • Network administration and planning: What is Windows Server? · fetched · Read platform roles, deployment, management, integration, and licensing overview; used as vendor-specific evidence, not a neutral comparison or price quote.
  • Network administration and planning: Ubuntu Server documentation · fetched · Read overview sections for networking, security, software updates, storage, virtualisation, performance, and high availability.
  • Network administration and planning: What is Linux? · fetched · Read operating-system and distribution explanations: kernel, user space, packages, and different distribution choices. Vendor educational material; not used to claim universal superiority.
  • Network administration and planning: Microsoft print command reference · fetched · Read command syntax and examples showing local port printing and a named shared network queue.
  • Network administration and planning: Active Directory Domain Services overview · fetched · Read directory purpose and security sections: AD DS stores network objects and supports authentication, access control, and policy-based administration.
  • Network administration and planning: Configure IP Addresses and Unique Subnets for New Users · fetched · Read subnet/address examples and topology context. This older tutorial contains classful-era simplifications; notes do not treat them as modern routing practice.
  • Network Protocols and Role-Play Analysis: FBLA Network Design 2026-27 Individual Guidelines · fetched · Read study guide pp. 6-7 for ND-NPSA objectives; pp. 2-4 for equipment and timing; p. 8 for the seven spoken rating criteria and maxima. The document leaves SMP unexplained and conflicts on flipchart/visuals.
  • Network Protocols and Role-Play Analysis: IETF RFC 9293: Transmission Control Protocol · fetched · Read the abstract and TCP service description: TCP is connection-oriented and provides reliable in-order byte-stream service; segments use IP datagrams and ports identify services.
  • Network Protocols and Role-Play Analysis: IETF RFC 2131: Dynamic Host Configuration Protocol · fetched · Read DHCP overview and address-allocation/client-server sections: DHCP delivers host configuration and allocates addresses through client-server exchanges and leases; relay agents can pass requests across subnets.
  • Network Protocols and Role-Play Analysis: Cisco: Configure IP Addresses and Unique Subnets · fetched · Read network-mask/subnet sections and device terminology for IP addressing, router interfaces, and gateway relationships. Its classful framing is older; these notes do not teach classful masks as current practice.
  • Sales Presentation: Customer-Centered Selling: FBLA 2026-27 Sales Presentation Guidelines · fetched · Read current PDF pp. 1-8 including event instructions, technology restrictions and pp. 7-8 rubric; verified 2026-27 edition. p.4 electricity contradiction recorded below.
  • Sales Presentation: Customer-Centered Selling: FTC Advertising FAQ: A Guide for Small Business · fetched · Read deception, express/implied claims, materiality, reasonable basis, testimonial, guarantee and disclosure passages; advertising guidance, not sales rubric or legal advice.
  • Sales Presentation: Customer-Centered Selling: HubSpot Academy Inbound Sales Certification Course · fetched · Read course description and curriculum: identify, connect, explore, advise; buyer context and personalized sales presentations. Commercial course; used as learning framework, not authority for claims or rules.
  • Sales Presentation: Customer-Centered Selling: Toastmasters: How to Overcome Your Fear of Public Speaking · fetched · Read organize/practice, audience focus, mistake recovery and pause/recovery-line passages; supports concrete rehearsal/structure methods, not FBLA scoring.

Limitations

  • OSI is a conceptual model; real Internet protocols do not map perfectly to seven discrete layers.
  • Historical IPv4 class ranges are simplified and must not be used to infer modern CIDR prefixes.
  • Wireless range and 5G performance depend on local environment, hardware, regulation and deployment.
  • Cisco RF guide (2024) includes generation/link-rate table, but table cites secondary material and its maxima are not guarantees. Cisco Ethernet cable guide is older and supports only listed PHY/cable cases; validate other media/reaches against exact transceiver datasheets. WPA3 notes use Cisco 17.15 configuration guide and apply only to supported combinations.
  • Cisco UCS 5108 details describe one blade platform, not every chassis.
  • Exact STP, UTP and coax performance varies by cable construction and PHY; no universal reach is asserted.
  • RAID level tolerance describes conventional layouts; controller, implementation and failure scenario matter. Microsoft Storage Spaces Direct is related parity/mirroring evidence, not an identical RAID implementation.
  • Cisco Networking Academy course page was not readable when fetched and is not claimed as read.
  • NIST CSRC glossary provided a direct honeypot definition; separate authoritative NIST entries for honeynet and honeyfile were not found. Those common instructional distinctions are explicitly qualified.
  • CISA DoS article is archived and may not reflect current policy; it is used only for basic attack mechanics, while mitigation is described cautiously.
  • RFC 6962 supports hash/digest and Merkle-tree mechanics but not the birthday bound itself; the generic birthday estimate is standard probability analysis and is labeled as an idealized bound.
  • CS-SD-01 cloud responsibility varies by provider, service model, contract, and configuration; AWS is an illustrative provider source.
  • NIST SP 800-34 publication overview was read, but not its detailed backup-method sections; full/incremental/differential mechanics are basic explanatory notes, not attributed to that overview.
  • NIST SP 800-57 and SP 800-63 fetched pages expose publication scope/metadata; they do not establish every algorithm or authenticator detail stated here.
  • The requested NIST hash and blockchain passages were fetched and read. Blockchain security depends on implementation, governance, consensus, keys, and participants; it does not establish truth or guaranteed immutability.
  • Classical Caesar example is a toy arithmetic illustration, not a modern cryptographic recommendation.
  • NIST SP 800-94 is a 2007 guide; detection mechanisms are taught conceptually, not as current product recommendations.
  • Tokenization mechanism is summarized at concept level; no dedicated standard on token-vault architecture was fetched.
  • WPA2 is identified as a secure protocol in the current objective list; the NIST wireless guide retrieved is marked technologically outdated, so no detailed WPA2 configuration advice is given.
  • NIST SP 800-34 introductory chapters were read, but detailed numeric RTO/RPO guidance was not independently fetched; notes give conceptual definitions, not mandated values.
  • FBLA official guideline PDF was not fetched in this pass; objective scope comes from the local 2026-27 inventory.
  • Cisco ACL behavior cited is IOS-specific; other firewall products can differ in rule order, defaults and state handling.
  • Microsoft print architecture reference describes Windows Server 2012; queue and host dependency concepts are used, not current driver deployment instructions.
  • Fiber reach and exact PHY rates require the actual cable, optics, standard and vendor specifications; no universal distance/rate is asserted.
  • NIST SP 800-34 Rev. 1 is older guidance; organization-specific recovery requirements and current policy govern implementation.
  • RFC 3414 is foundational but dates from 2002 and specifies historic MD5/DES examples; deployed SNMPv3 algorithm support must be checked against current vendor guidance and policy.
  • Azure Load Balancer describes one Layer 4 product; algorithms, probe semantics, affinity, and failure handling vary by implementation.
  • LAN/WAN are geographic scope labels, not fixed throughput classes. Actual performance needs measurement of media, topology, load, and endpoints.
  • Windows Server and Ubuntu/Linux sources are platform owners; they document their own capabilities, not a neutral performance or security ranking. Licensing and support terms change and must be checked for the proposed deployment.
  • The Cisco subnet tutorial is older and includes classful simplifications; no classful assumptions are used for current network planning.
  • The National guide prints SMP as an example but does not define it. This module preserves the ambiguity and does not substitute SMTP, SNMP, or another protocol; seek adviser clarification on expected scope.
  • Network Design guideline p.2 lists flipchart/easel while p.4 prohibits visuals and props. The conflict is unresolved here; ask the adviser and do not assume equipment permission.
  • FBLA 2026-27 PDF p.4 lists power access for a conference-room final and also says electricity will not be available. No resolution inferred; confirm with event adviser/organizer. Plan without power unless clarified.
  • These notes and fictional examples teach concepts; they are not a ready-to-submit competition pitch. National rules reserve planning, research, preparation, and setup of an actual entry to registered competitors.
  • FTC FAQ is general US advertising guidance; product-specific legal requirements may differ. This module is educational, not legal advice.