WEBVTT 00:00:00.000 --> 00:00:02.899 Welcome to the deep dive. You know, if I were 00:00:02.899 --> 00:00:05.719 to ask you to picture high stakes network security, 00:00:06.320 --> 00:00:09.919 you'd probably visualize massive data centers. 00:00:09.960 --> 00:00:12.439 Or government agencies, right, with layers of 00:00:12.439 --> 00:00:14.439 biometric scanners and all that. Exactly. We 00:00:14.439 --> 00:00:17.000 tend to associate that kind of complexity with 00:00:17.000 --> 00:00:18.920 these billion dollar budgets. And that's totally 00:00:18.920 --> 00:00:21.719 natural. But the source material we analyzed 00:00:21.719 --> 00:00:24.460 for this deep dive, it really challenges that 00:00:24.460 --> 00:00:27.320 idea. Some of the most critical and, I mean, 00:00:27.550 --> 00:00:30.489 uniquely challenging networks to manage and secure 00:00:30.489 --> 00:00:33.789 are actually school IT networks. That's surprising. 00:00:34.149 --> 00:00:36.229 Well, they're essential infrastructure for learning, 00:00:36.289 --> 00:00:38.829 but they have to operate under enterprise -level 00:00:38.829 --> 00:00:41.369 demands, but with definitely non -enterprise 00:00:41.369 --> 00:00:44.070 budgets. So our mission today is to use that 00:00:44.070 --> 00:00:46.770 complexity, the complexity of, say, a high school 00:00:46.770 --> 00:00:49.530 network, as a practical model. A model to master 00:00:49.530 --> 00:00:51.869 the foundational concepts of enterprise networking. 00:00:51.990 --> 00:00:54.460 Yeah. We're aiming for those aha moments, you 00:00:54.460 --> 00:00:56.799 know, the ones that bridge the gap between a 00:00:56.799 --> 00:00:58.979 technical definition and actually managing something 00:00:58.979 --> 00:01:01.460 strategically. And the challenge here isn't just 00:01:01.460 --> 00:01:04.700 technical. It's logistical. It's legal. For anyone 00:01:04.700 --> 00:01:07.939 entering security or IT, this is a real trial 00:01:07.939 --> 00:01:11.019 by fire. You've got this massive user volume, 00:01:11.239 --> 00:01:14.340 often non -technical administrators, and huge 00:01:14.340 --> 00:01:16.560 data liability. You mean something like FERPA. 00:01:16.920 --> 00:01:19.359 Exactly. The Family Educational Rights and Privacy 00:01:19.359 --> 00:01:22.280 Act. So you can't just defer your understanding. 00:01:22.340 --> 00:01:24.640 You have to become an expert in risk management. 00:01:24.739 --> 00:01:27.340 And you have very, very little room for error. 00:01:27.500 --> 00:01:29.099 OK, let's unpack this. Maybe we can start with 00:01:29.099 --> 00:01:31.659 a quick look at how we even got here. I mean, 00:01:31.819 --> 00:01:34.359 at its most basic level, a network just provides 00:01:34.359 --> 00:01:37.939 a path to move data packets between nodes, right? 00:01:38.099 --> 00:01:40.459 Right. It gives each node a unique address and 00:01:40.459 --> 00:01:42.480 then tracks where to send the packets. That's 00:01:42.480 --> 00:01:45.079 it. And that core function started decades ago, 00:01:45.340 --> 00:01:48.239 serving mostly academic researchers and the military. 00:01:48.319 --> 00:01:50.819 Yeah, very specialized needs. For most people, 00:01:50.959 --> 00:01:52.459 networking didn't really become a thing until 00:01:52.459 --> 00:01:54.920 the mid -90s with the World Wide Web and HTTP. 00:01:55.159 --> 00:01:57.140 That's what made the internet a common utility. 00:01:57.319 --> 00:01:59.260 And now, of course, computing and networking 00:01:59.260 --> 00:02:01.680 are basically the same thing. Our data is in 00:02:01.680 --> 00:02:04.159 the cloud, our apps are in a browser, and if 00:02:04.159 --> 00:02:06.659 the network fails... The whole institution stops. 00:02:07.060 --> 00:02:11.610 A bank? a corporation, or a school. It just grinds 00:02:11.610 --> 00:02:13.969 to a halt. That necessity is what drives the 00:02:13.969 --> 00:02:16.210 need for these two critical pillars of performance 00:02:16.210 --> 00:02:18.710 you mentioned earlier. Robustness and reliability. 00:02:19.430 --> 00:02:22.229 When IT managers design any network, especially 00:02:22.229 --> 00:02:24.650 in a high demand school, they're trying to optimize 00:02:24.650 --> 00:02:26.949 for both of those. So let's break down the difference. 00:02:27.409 --> 00:02:30.819 Robustness is about capacity, isn't it? Can the 00:02:30.819 --> 00:02:33.659 network deliver information without delays, no 00:02:33.659 --> 00:02:35.819 matter how many people are on it? Exactly. If 00:02:35.819 --> 00:02:38.240 your network isn't robust, you get high latency. 00:02:38.759 --> 00:02:41.819 Pages load slowly. Services might crash completely 00:02:41.819 --> 00:02:45.080 when every student logs in after lunch. And reliability 00:02:45.080 --> 00:02:46.919 is different. That's just uptime. It's uptime, 00:02:47.039 --> 00:02:48.819 yeah. It's the percentage of time the network 00:02:48.819 --> 00:02:52.099 is available and accepting connections. An unreliable 00:02:52.099 --> 00:02:55.039 system just fails intermittently. And it doesn't 00:02:55.039 --> 00:02:57.280 matter how heavy the traffic is. So what's the 00:02:57.280 --> 00:02:59.650 strategic trade -off here? Well, the key insight 00:02:59.650 --> 00:03:03.110 is that managers often have to sacrifice robustness. 00:03:03.449 --> 00:03:05.789 So they might delay a critical software update 00:03:05.789 --> 00:03:09.330 or a reboot just to guarantee reliability during, 00:03:09.330 --> 00:03:12.490 say, standardized testing week. You can't always 00:03:12.490 --> 00:03:15.669 have both at 100%. Not with a limited budget, 00:03:15.669 --> 00:03:17.650 anyway. Right. And these trade -offs, they're 00:03:17.650 --> 00:03:19.710 often being made right where the network physically 00:03:19.710 --> 00:03:23.479 lives, the wiring closet. Ah, the wiring closet. 00:03:23.599 --> 00:03:25.539 Yeah. If you haven't seen one, just picture a 00:03:25.539 --> 00:03:28.000 small, usually hot room. It's full of racks, 00:03:28.259 --> 00:03:30.639 blinking lights, lots of fans. It's the physical 00:03:30.639 --> 00:03:32.919 brain of the whole operation. It really is the 00:03:32.919 --> 00:03:34.740 nerve center. It's where you find the crucial 00:03:34.740 --> 00:03:36.819 hardware, like the Unified Threat Management 00:03:36.819 --> 00:03:39.919 Appliance or UPM. That's your main defense against 00:03:39.919 --> 00:03:41.919 malware and hackers, right? Right. And it also 00:03:41.919 --> 00:03:43.879 houses the Gateway, which is the device that 00:03:43.879 --> 00:03:46.759 connects every single computer inside the school 00:03:46.759 --> 00:03:50.969 to the global internet. So security... as our 00:03:50.969 --> 00:03:53.689 sources really stress, starts with physical control. 00:03:54.490 --> 00:03:56.509 Why is that so much more critical in a school 00:03:56.509 --> 00:03:59.069 than, say, a digital firewall? Because if someone 00:03:59.069 --> 00:04:01.289 can physically get into that closet, they can 00:04:01.289 --> 00:04:03.770 do anything. They can plug in malicious hardware. 00:04:03.969 --> 00:04:06.090 They can unplug a key cable and launch a denial 00:04:06.090 --> 00:04:08.270 -of -service attack. They can even steal equipment. 00:04:08.909 --> 00:04:11.750 Physical security is the baseline. And in a school... 00:04:11.610 --> 00:04:13.830 That control is contentious. Oh, absolutely. 00:04:14.430 --> 00:04:17.449 IT wants total lockdown, but then principals 00:04:17.449 --> 00:04:20.209 and administrators want emergency access, and 00:04:20.209 --> 00:04:23.069 that just blurs those essential security boundaries. 00:04:23.410 --> 00:04:26.029 That distinction brings us to a really foundational 00:04:26.029 --> 00:04:29.389 concept. The difference between the LAN and the 00:04:29.389 --> 00:04:32.120 internet. And it's not just what you can touch. 00:04:32.439 --> 00:04:35.779 The real strategic differentiator is about trust 00:04:35.779 --> 00:04:38.339 and control. OK, explain that. The local area 00:04:38.339 --> 00:04:41.319 network, the LAN, is made up of all the devices, 00:04:41.540 --> 00:04:44.319 like shared servers or printers, that the school's 00:04:44.319 --> 00:04:47.439 IT team actually controls and can trust. Or at 00:04:47.439 --> 00:04:50.120 least they can manage the security of those devices. 00:04:50.300 --> 00:04:52.360 The internet is everything else. The internet 00:04:52.360 --> 00:04:55.220 is this vast sea of resources that are maintained 00:04:55.220 --> 00:04:57.420 by people you don't know, that you have no control 00:04:57.420 --> 00:04:59.620 over, and that you fundamentally cannot fully 00:04:59.620 --> 00:05:01.759 trust. That's a much more useful way to think 00:05:01.759 --> 00:05:04.879 about it. And the problem is that things that 00:05:04.879 --> 00:05:07.779 used to be on the LAN, like a library card catalog, 00:05:07.920 --> 00:05:10.500 are now almost all on the internet, which just 00:05:10.500 --> 00:05:13.000 massively increases the complexity of maintaining 00:05:13.000 --> 00:05:15.319 that boundary of trust. And that requires enterprise 00:05:15.319 --> 00:05:17.800 -grade hardware, which gets us to the issue of 00:05:17.800 --> 00:05:20.509 scale. Right. You can go buy a basic consumer 00:05:20.509 --> 00:05:23.410 switch for, what, under 50 bucks, but that's 00:05:23.410 --> 00:05:26.149 not going to handle more than maybe 10 devices 00:05:26.149 --> 00:05:28.209 before it starts to choke. And you contrast that 00:05:28.209 --> 00:05:31.069 with a school network, and you see why the costs 00:05:31.069 --> 00:05:34.970 just explode. A sophisticated 48 -port enterprise 00:05:34.970 --> 00:05:37.670 switch with advanced management software could 00:05:37.670 --> 00:05:42.139 cost $5 ,000. And that massive price jump isn't 00:05:42.139 --> 00:05:44.759 just for more ports. It's for the software. The 00:05:44.759 --> 00:05:47.319 ability to manage, configure, and secure traffic 00:05:47.319 --> 00:05:50.279 for hundreds, even thousands of nodes all at 00:05:50.279 --> 00:05:52.720 the same time. It's the cost of control. Exactly. 00:05:52.800 --> 00:05:55.139 The cost of granular control and reliability. 00:05:55.420 --> 00:05:57.180 Let's move into the technical fundamentals then, 00:05:57.279 --> 00:05:59.100 starting with bandwidth. We know it's the amount 00:05:59.100 --> 00:06:01.500 of information transferred over time, but the 00:06:01.500 --> 00:06:04.019 key insight isn't just the number, right? It's 00:06:04.019 --> 00:06:06.930 the management. It's a political issue, disguised 00:06:06.930 --> 00:06:09.569 as a technical one, because bandwidth is a zero 00:06:09.569 --> 00:06:12.209 -sum game. If a whole classroom starts streaming 00:06:12.209 --> 00:06:15.449 video, that bandwidth is now completely unavailable 00:06:15.449 --> 00:06:17.509 for something more critical, like state -mandated 00:06:17.509 --> 00:06:19.529 testing. And the bottleneck isn't always your 00:06:19.529 --> 00:06:23.110 ISP contract. No, not at all. Internally, your 00:06:23.110 --> 00:06:26.029 total data rate is limited by your slowest device. 00:06:26.319 --> 00:06:29.500 your weakest link, you could have a one gigabit 00:06:29.500 --> 00:06:31.500 per second network. But if it runs through an 00:06:31.500 --> 00:06:34.379 old 100 megabit switch, that whole segment of 00:06:34.379 --> 00:06:36.939 the network is now running at 100 megabits. So 00:06:36.939 --> 00:06:39.480 IT teams have to become resource managers. They're 00:06:39.480 --> 00:06:41.759 rationers. They don't just buy more bandwidth. 00:06:41.879 --> 00:06:44.279 They actively configure the routing and switching 00:06:44.279 --> 00:06:48.240 to limit access to known broadband hogs, like 00:06:48.240 --> 00:06:50.199 certain streaming sites. They're making policy 00:06:50.199 --> 00:06:52.439 decisions through IT configuration. How do they 00:06:52.439 --> 00:06:54.800 even know who the hogs are? They use network 00:06:54.800 --> 00:06:57.660 sniffing. It's basically packet analyzing software 00:06:57.660 --> 00:06:59.879 that lets them see all the traffic in incredible 00:06:59.879 --> 00:07:02.839 detail. And that tool is crucial, not just for 00:07:02.839 --> 00:07:05.259 usage patterns, but for spotting malware -infected 00:07:05.259 --> 00:07:07.560 computers or other weird behavior on the network. 00:07:07.800 --> 00:07:11.579 Okay, so from capacity to identification. Addressing 00:07:11.579 --> 00:07:14.300 is also key. Every device needs an identity. 00:07:14.579 --> 00:07:16.800 Two types, actually. You have the physical identity, 00:07:17.040 --> 00:07:18.699 which is the permanent media access control, 00:07:19.040 --> 00:07:21.959 or a mass address. It's hard -coded right into 00:07:21.959 --> 00:07:23.680 the hardware. And then there's the logical one, 00:07:23.779 --> 00:07:26.529 the IP address. Yeah. which is temporary. Right. 00:07:26.689 --> 00:07:29.370 It's assigned by DHCP software when you connect. 00:07:29.790 --> 00:07:32.629 And the classic school problem is address exhaustion 00:07:32.629 --> 00:07:35.649 when the DHCP pool just runs out of addresses 00:07:35.649 --> 00:07:38.670 and new devices simply can't connect. It's incredibly 00:07:38.670 --> 00:07:40.649 frustrating. And this is only getting more complex 00:07:40.649 --> 00:07:44.589 with IPv6. It is. The move from IPv4, which was 00:07:44.589 --> 00:07:48.410 about 4 .3 billion addresses, to the 128 -bit 00:07:48.410 --> 00:07:51.949 IPv6 isn't just about more nodes. For security 00:07:51.949 --> 00:07:54.170 people, the real headache is that the sheer size 00:07:54.170 --> 00:07:57.209 of the IPv6 address space makes things like firewall 00:07:57.209 --> 00:07:59.949 management and packet inspection way more complex 00:07:59.949 --> 00:08:02.129 and resource intensive to do right. And here's 00:08:02.129 --> 00:08:03.810 where it gets really interesting for troubleshooting. 00:08:04.290 --> 00:08:06.610 Humans can't memorize those long numbers, so 00:08:06.610 --> 00:08:08.829 we need a translator. The domain name server 00:08:08.829 --> 00:08:14.310 or DNS? Exactly. It turns www .google .com into 00:08:14.310 --> 00:08:17.470 an IP address. And if your device says it's connected, 00:08:17.529 --> 00:08:19.829 but you can't open any website by name. It's 00:08:19.829 --> 00:08:22.089 almost always a DNS problem. That's your key 00:08:22.089 --> 00:08:24.670 diagnostic indicator. And DNS ties directly into 00:08:24.670 --> 00:08:27.360 the third concept. routing. Which is just directing 00:08:27.360 --> 00:08:29.100 packets along an efficient route to where they 00:08:29.100 --> 00:08:31.160 need to go. The router handles traffic between 00:08:31.160 --> 00:08:33.639 the LAN and the internet. And inside the LAN, 00:08:33.919 --> 00:08:35.879 packets are managed by those expensive enterprise 00:08:35.879 --> 00:08:37.639 switches. Okay, let's talk about connectivity 00:08:37.639 --> 00:08:40.600 without cables. Wireless. Most schools now are 00:08:40.600 --> 00:08:43.039 almost entirely on Wi -Fi. They are. And Wi -Fi 00:08:43.039 --> 00:08:45.299 uses radio signals to connect devices to the 00:08:45.299 --> 00:08:47.639 school's own wired network through devices called 00:08:47.639 --> 00:08:50.220 access points, or APs. And it's important to 00:08:50.220 --> 00:08:52.100 distinguish that from cellular, right? Oh, absolutely. 00:08:52.659 --> 00:08:54.679 Cellular bypasses the school network entirely. 00:08:54.990 --> 00:08:57.909 directly to outside cell towers. But when a device 00:08:57.909 --> 00:09:00.529 uses the school's Wi -Fi, every single one of 00:09:00.529 --> 00:09:02.450 its packets has to pass through the school's 00:09:02.450 --> 00:09:04.649 security infrastructure. And to manage that, 00:09:04.929 --> 00:09:07.830 IT usually sets up multiple network names, or 00:09:07.830 --> 00:09:11.250 SSIDs. Correct. You'll typically see a few. Maybe 00:09:11.250 --> 00:09:14.710 a hidden admin SSID for staff and secure devices. 00:09:15.450 --> 00:09:17.750 Then the main one, the teaching and learning 00:09:17.750 --> 00:09:20.370 SSID, which gets the most bandwidth and access 00:09:20.370 --> 00:09:22.470 to LAN resources. And then there's the really 00:09:22.470 --> 00:09:26.419 important one for security. The guest SSID, this 00:09:26.419 --> 00:09:29.460 is the safety net. It usually has very limited 00:09:29.460 --> 00:09:32.279 bandwidth and critically it's configured to provide 00:09:32.279 --> 00:09:36.039 zero access to any internal LAN resources. This 00:09:36.039 --> 00:09:38.360 is the main strategy for handling bring your 00:09:38.360 --> 00:09:41.940 own device or BYOD. You put them in a zero trust 00:09:41.940 --> 00:09:44.080 zone right away. So what's the biggest challenge 00:09:44.080 --> 00:09:46.669 with Wi -Fi reliability? It's not technical, 00:09:46.769 --> 00:09:49.149 it's physical placement. If you have too many 00:09:49.149 --> 00:09:51.789 access points in one area, their signals overlap, 00:09:51.929 --> 00:09:54.529 and that causes devices to constantly drop and 00:09:54.529 --> 00:09:56.889 reconnect. For the user, it just feels like a 00:09:56.889 --> 00:09:59.070 completely unreliable network. Which brings us 00:09:59.070 --> 00:10:01.169 back to management. So what does all this mean 00:10:01.169 --> 00:10:03.149 for the person on the ground, the IT professional? 00:10:03.549 --> 00:10:06.210 It means management is continuous, it's labor 00:10:06.210 --> 00:10:08.690 -intensive, and it's not glamorous. And a lot 00:10:08.690 --> 00:10:10.610 of it has to be done during school holidays to 00:10:10.610 --> 00:10:12.470 avoid disrupting classes. What's the one thing 00:10:12.470 --> 00:10:14.309 they have to get right? The sources all agree 00:10:14.309 --> 00:10:16.990 on this. mapping and documenting the network. 00:10:17.370 --> 00:10:20.009 Knowing the address, the physical location, and 00:10:20.009 --> 00:10:23.289 the configuration of every single device, it's 00:10:23.289 --> 00:10:25.710 often neglected because people are overworked. 00:10:25.710 --> 00:10:28.509 But you cannot troubleshoot, upgrade, or audit 00:10:28.509 --> 00:10:30.970 a network you haven't meticulously mapped. And 00:10:30.970 --> 00:10:33.470 the day -to -day work is just relentless. It 00:10:33.470 --> 00:10:36.889 is. You're authenticating thousands of users, 00:10:37.090 --> 00:10:39.769 managing their permissions using organizational 00:10:39.769 --> 00:10:42.470 units like ninth grade students versus admin 00:10:42.470 --> 00:10:45.169 staff. You're troubleshooting remote across different 00:10:45.169 --> 00:10:47.509 buildings and constantly doing system maintenance 00:10:47.509 --> 00:10:49.710 to make sure everything is patched and updated. 00:10:49.950 --> 00:10:52.289 And all that work is driven by the security imperative. 00:10:52.629 --> 00:10:55.429 Exactly. Network security is all about applying 00:10:55.429 --> 00:10:59.669 the CIA triad. Confidentiality, integrity, and 00:10:59.669 --> 00:11:01.990 availability. Okay, so confidentiality means 00:11:01.990 --> 00:11:05.029 only authorized people can access data. Integrity 00:11:05.029 --> 00:11:07.490 means the data is accurate. And availability 00:11:07.490 --> 00:11:09.809 means people who need access can actually get 00:11:09.809 --> 00:11:12.419 it. And for schools, confidentiality is not just 00:11:12.419 --> 00:11:14.500 a best practice. It's a legal mandate because 00:11:14.500 --> 00:11:17.240 of FERPA. School leaders can face real liability, 00:11:17.519 --> 00:11:19.960 even criminal charges, for failing to protect 00:11:19.960 --> 00:11:22.799 student data. And that legal pressure forces 00:11:22.799 --> 00:11:25.700 confidentiality right to the top of the priority 00:11:25.700 --> 00:11:27.519 list. It does. And that's where the conflict 00:11:27.519 --> 00:11:30.519 comes in. If confidentiality is a legal must 00:11:30.519 --> 00:11:33.220 -have and your budget is finite, the trade -off 00:11:33.220 --> 00:11:36.960 is often felt by the other two. Increasing confidentiality, 00:11:37.059 --> 00:11:39.740 like adding more layers of verification, almost 00:11:39.740 --> 00:11:42.580 always limits availability. And trying to maintain 00:11:42.580 --> 00:11:45.360 that high level of security with fewer staff 00:11:45.360 --> 00:11:48.440 might mean you compromise integrity by delaying 00:11:48.440 --> 00:11:50.919 important system patches. It's a constant balancing 00:11:50.919 --> 00:11:53.240 act. It is. So the practical security measures 00:11:53.240 --> 00:11:56.480 beyond just the UTM appliance are all about containment. 00:11:56.820 --> 00:11:59.259 You block known malware sites, use that zero 00:11:59.259 --> 00:12:02.940 trust guest SSID for view IOD, and you are constantly 00:12:02.940 --> 00:12:05.450 monitoring traffic logs. And if you find a threat, 00:12:05.669 --> 00:12:08.309 remediation has to be fast. Super fast. That 00:12:08.309 --> 00:12:10.190 could mean taking an infected computer off the 00:12:10.190 --> 00:12:12.610 network or restoring critical data from secure 00:12:12.610 --> 00:12:14.809 offsite backups. And there's an ultimate tactical 00:12:14.809 --> 00:12:18.480 move they can make. Blacklisting, yes. If one 00:12:18.480 --> 00:12:21.559 specific device, say, a student's laptop that's 00:12:21.559 --> 00:12:23.419 always getting infected is causing problems, 00:12:23.840 --> 00:12:27.000 the IT manager can blacklist its MSE address 00:12:27.000 --> 00:12:30.580 on the DHCP server. And that prevents that specific 00:12:30.580 --> 00:12:33.519 machine from ever getting an IP address or connecting 00:12:33.519 --> 00:12:35.360 to the network again. It's the network equivalent 00:12:35.360 --> 00:12:37.960 of a permanent timeout. Pretty much. So this 00:12:37.960 --> 00:12:40.940 deep dive really shows that understanding a school 00:12:40.940 --> 00:12:44.179 IT network is, I mean, it's a practical shortcut. 00:12:44.330 --> 00:12:46.629 to mastering these huge enterprise principles. 00:12:46.970 --> 00:12:50.129 You're managing diverse users, legal data requirements, 00:12:50.450 --> 00:12:53.110 evolving tech, all under major constraints. It 00:12:53.110 --> 00:12:55.029 forces you to think strategically, because you 00:12:55.029 --> 00:12:57.169 realize security is never just a technical problem. 00:12:57.289 --> 00:12:59.210 And that's the core lesson, really. The three 00:12:59.210 --> 00:13:01.870 pillars, confidentiality, integrity, and availability, 00:13:02.129 --> 00:13:04.610 they're inherently contradictory. Every single 00:13:04.610 --> 00:13:06.929 decision is a constant calculation of tradeoffs. 00:13:07.129 --> 00:13:09.850 Which leaves us with this final provocative thought 00:13:09.850 --> 00:13:13.129 for you to consider. Knowing that confidentiality 00:13:13.129 --> 00:13:15.929 is a legal mandate under FERPA, if you were managing 00:13:15.929 --> 00:13:18.210 the budget for a school district, how would you 00:13:18.210 --> 00:13:20.450 allocate resources across the other two pillars? 00:13:21.129 --> 00:13:24.110 Would you prioritize integrity to make sure academic 00:13:24.110 --> 00:13:26.149 records and student grades are always perfectly 00:13:26.149 --> 00:13:28.769 accurate? Or would you prioritize availability 00:13:28.769 --> 00:13:31.490 to ensure every student has reliable, fast access 00:13:31.490 --> 00:13:33.889 to learning resources, even if that introduces 00:13:33.889 --> 00:13:36.350 some small risks? Something to chew on until 00:13:36.350 --> 00:13:37.429 our next deep dive.