WEBVTT 1 00:00:00.040 --> 00:00:03.960 Hey, everyone, welcome back. Ready to dive into some serious cybersecurity? 2 00:00:04.040 --> 00:00:04.919 Always ready for that. 3 00:00:05.040 --> 00:00:09.359 Today we're tackling mastering defensive security. This awesome book by 4 00:00:09.400 --> 00:00:10.279 Caesar Bravo. 5 00:00:10.519 --> 00:00:13.160 Ah, Caesar Bravo. He really knows the stuff right. 6 00:00:13.199 --> 00:00:17.519 The guy's walking cybersecurity encyclopedia, teaching, giving talks, you name it. 7 00:00:18.160 --> 00:00:20.120 But what struck me about this book is how it 8 00:00:20.239 --> 00:00:24.679 really pushes for like deep understanding, not just memorizing a 9 00:00:24.719 --> 00:00:27.160 bunch of jargon. What are your thoughts on that approach? 10 00:00:27.359 --> 00:00:30.760 Well, it's like think about learning to drive. You could 11 00:00:30.760 --> 00:00:33.759 memorize every single street in your town, right, but to 12 00:00:33.880 --> 00:00:38.039 actually drive anywhere new, you need to get those underlying concepts, 13 00:00:38.399 --> 00:00:40.840 the rules of the road, how to react to you know, 14 00:00:40.880 --> 00:00:41.960 other drivers, all that. 15 00:00:42.000 --> 00:00:44.840 It's about the bigger picture, not just the rote memorization exactly. 16 00:00:44.840 --> 00:00:47.520 And cybersecurity is the same way. To really master it, 17 00:00:47.560 --> 00:00:49.719 you got to go beyond just like checking boxes and 18 00:00:49.799 --> 00:00:53.520 really grasp those fundamental principles. That's how you adapt and 19 00:00:53.560 --> 00:00:56.560 defend against, you know, whatever curveballs get thrown your way. 20 00:00:56.799 --> 00:00:58.759 And the book really digs into that with the whole 21 00:00:59.079 --> 00:01:04.359 cybersecurity triad thing, right, confidentiality, integrity, availability. It even says 22 00:01:04.439 --> 00:01:07.079 seasoned pros use this all the time. There's even that 23 00:01:07.079 --> 00:01:10.400 story about the CIO using it as a like a 24 00:01:10.439 --> 00:01:13.159 litmus test for every security decision. 25 00:01:13.200 --> 00:01:15.159 It's such a fundamental concept, you know. It's like that 26 00:01:15.239 --> 00:01:18.280 saying a chain is only as strong as its weakest link. 27 00:01:18.760 --> 00:01:21.599 The triad shows how security is multifaceted. You can't just 28 00:01:21.640 --> 00:01:23.760 focus on one area and ignore the others. 29 00:01:23.840 --> 00:01:27.920 So true. So for those who might not be as familiar, 30 00:01:28.560 --> 00:01:32.519 how would you explain the triad? Like in simple terms? 31 00:01:32.599 --> 00:01:35.359 Okay, so imagine something everyone uses email? 32 00:01:35.480 --> 00:01:36.400 Okay, makes sense. 33 00:01:36.439 --> 00:01:39.359 Confidentiality is like making sure only you and the person 34 00:01:39.400 --> 00:01:41.959 you're emailing can read that message, no one else, y'escha. 35 00:01:42.239 --> 00:01:45.480 Integrity is knowing that email hasn't been messed with in 36 00:01:45.560 --> 00:01:49.040 transit like someone changing the amount do on an invoice 37 00:01:49.120 --> 00:01:52.319 or something. And availability that's just your email working when 38 00:01:52.359 --> 00:01:54.239 you need it, no one annoying outages or anything. 39 00:01:54.359 --> 00:01:57.920 So basically, it's about keeping things private, accurate, and accessible. 40 00:01:58.159 --> 00:02:00.120 That CSO story was a great way to show that 41 00:02:00.400 --> 00:02:03.519 it's not enough to just know the definitions, right, Yeah, 42 00:02:03.560 --> 00:02:05.439 you have to get how they actually play out in 43 00:02:05.480 --> 00:02:06.079 the real world. 44 00:02:06.120 --> 00:02:09.639 Absolutely it's about making those connections and speaking. 45 00:02:09.360 --> 00:02:11.599 Of real world The book doesn't shy away from one 46 00:02:11.639 --> 00:02:15.400 of the biggest headaches in security, passwords. It's pretty upfront 47 00:02:15.439 --> 00:02:19.159 about password breaches being almost unavoidable these days. It even 48 00:02:19.199 --> 00:02:21.759 recommends checking if your INCO's already out there on sites 49 00:02:21.840 --> 00:02:25.560 like having p and Eidindia dot com and dehash dot com. 50 00:02:25.639 --> 00:02:27.080 If you ever used those, Oh. 51 00:02:27.000 --> 00:02:29.680 Yeah, it's definitely an eye opener. You'd be surprised how 52 00:02:29.680 --> 00:02:31.719 many breaches your info might have been caught up in. 53 00:02:31.960 --> 00:02:34.599 Right mays you think twice about those password one hundred 54 00:02:34.599 --> 00:02:37.639 and twenty three days. Huh. But the book goes beyond 55 00:02:37.639 --> 00:02:40.560 just telling people to use strong passwords. It gets into 56 00:02:40.520 --> 00:02:43.479 the nitty gritty, the actual math behind password complexity. It 57 00:02:43.520 --> 00:02:45.520 even has a formula and everything. 58 00:02:45.759 --> 00:02:49.039 Yeah, the math can be a bit intimidating, but it 59 00:02:49.080 --> 00:02:54.039 really demystifies password strength. The longer and more varied your 60 00:02:54.080 --> 00:02:57.879 password is, the harder it is to crack. Think of 61 00:02:57.919 --> 00:03:00.639 it like trying to guess a combination lock. A lock 62 00:03:00.680 --> 00:03:03.000 with a million possible combinations is going to be a 63 00:03:03.080 --> 00:03:05.199 lot harder to crack than one with only one hundred. 64 00:03:05.360 --> 00:03:08.840 That makes sense, So longer and more complex equals way 65 00:03:08.879 --> 00:03:09.520 more secure. 66 00:03:09.719 --> 00:03:13.879 Exactly, it exponentially increases the time and resources an attacker 67 00:03:13.879 --> 00:03:14.840 would need to crack it. 68 00:03:15.240 --> 00:03:18.479 And there's the whole discussion of those three Golden rules 69 00:03:18.479 --> 00:03:22.719 for organizational password security, including those password vaults. I love 70 00:03:22.759 --> 00:03:25.960 how the book even suggests running a live hacking demo 71 00:03:26.080 --> 00:03:27.400 using a tool called John. 72 00:03:27.199 --> 00:03:30.199 The Ripper, talk about a reality check. Password vauts are 73 00:03:30.199 --> 00:03:32.639 great because they're like having a digital lock box for 74 00:03:32.680 --> 00:03:35.240 your passwords, making it much harder for attackers to get in. 75 00:03:35.599 --> 00:03:37.560 And John the Ripper is a prime example of how 76 00:03:37.599 --> 00:03:41.120 attackers use easily accessible tools to crack weak passwords. 77 00:03:41.159 --> 00:03:43.400 So it's like a good reality check for organizations, right. 78 00:03:43.439 --> 00:03:46.439 Oh, absolutely, it really highlights the need for those strong, 79 00:03:46.520 --> 00:03:48.400 unique passwords for every single account. 80 00:03:48.520 --> 00:03:51.639 This book's all about that practical application, isn't it. It's 81 00:03:51.639 --> 00:03:54.840 one thing to talk theory, but actually seeing these concepts 82 00:03:54.840 --> 00:03:58.520 in action with that hacking demo really drives the point 83 00:03:58.520 --> 00:03:59.400 home for sure. 84 00:03:59.479 --> 00:04:04.840 It's about bridging that gap between knowing and doing, and speaking. 85 00:04:04.520 --> 00:04:07.080 Of practical defense, the book talks about defense in depth, 86 00:04:07.520 --> 00:04:10.520 this idea that you need multiple layers of security, not 87 00:04:10.639 --> 00:04:12.159 just one single barrier. 88 00:04:12.360 --> 00:04:15.840 Right, It's about creating a security fortress around your data, 89 00:04:16.160 --> 00:04:18.680 not just relying on a single lock on the front door. 90 00:04:18.879 --> 00:04:20.839 So instead of just a lock, maybe you've also got 91 00:04:20.959 --> 00:04:24.439 security cameras, motion detectors, guard dog Exactly. 92 00:04:24.480 --> 00:04:27.920 It's about layering those defenses to make it way harder 93 00:04:27.920 --> 00:04:31.279 for attackers to get through. Every layer adds another level 94 00:04:31.319 --> 00:04:32.600 of complexity for them. 95 00:04:32.560 --> 00:04:35.279 And within that fortress you need specialists, which is where 96 00:04:35.319 --> 00:04:37.680 the book's discussion on penetration testing comes in. 97 00:04:37.800 --> 00:04:40.040 Pen testing I love this part right. 98 00:04:40.279 --> 00:04:44.319 It explains how ethical hackers try to basically break into 99 00:04:44.360 --> 00:04:45.800 your systems, but for a good reason. 100 00:04:46.040 --> 00:04:48.800 It's like hiring a professional burglar to test your home 101 00:04:48.839 --> 00:04:52.639 security system. They can help you find and fix vulnerabilities 102 00:04:52.720 --> 00:04:54.560 before the bad guys can exploit them. 103 00:04:54.839 --> 00:04:58.319 That's a great analogy, and just like they're different types 104 00:04:58.319 --> 00:05:01.279 of burglars, I guess you could say the book breaks 105 00:05:01.319 --> 00:05:05.000 down pen testing into those different categories black box, white 106 00:05:05.000 --> 00:05:06.800 box and grey box testing. 107 00:05:06.920 --> 00:05:10.319 Right. Each one simulates a different level of attacker knowledge. 108 00:05:10.399 --> 00:05:12.199 So black box would be like trying to break into 109 00:05:12.240 --> 00:05:14.560 a house you know nothing about. You have to figure 110 00:05:14.560 --> 00:05:16.240 out everything from scratch exactly. 111 00:05:16.319 --> 00:05:19.519 White box testing is like having the blueprints to the house. 112 00:05:19.560 --> 00:05:22.480 You know exactly how everything works, making it easier to 113 00:05:22.560 --> 00:05:24.240 pinpoint vulnerabilities and. 114 00:05:24.240 --> 00:05:26.160 Gray boxes somewhere in between. 115 00:05:26.000 --> 00:05:29.519 Exactly you might have some information but not the complete picture. 116 00:05:29.920 --> 00:05:32.720 And while we're on the topic of vulnerabilities, the book 117 00:05:32.759 --> 00:05:36.399 gets into how often organizations should be checking for them 118 00:05:36.759 --> 00:05:39.879 and what events should trigger a full blown security assessment. 119 00:05:40.560 --> 00:05:43.680 It even gets into the weeds of USB vulnerabilities, which, 120 00:05:43.759 --> 00:05:45.959 as it turns out, are a lot scarier than I 121 00:05:46.000 --> 00:05:48.879 ever realized. It's not just about losing a flash drive. 122 00:05:48.920 --> 00:05:51.439 It's about those hid attacks. Have you heard of? 123 00:05:51.439 --> 00:05:54.240 Those hide attacks are definitely something to be aware of. 124 00:05:54.360 --> 00:05:57.040 They can really catch people off guard because they exploit 125 00:05:57.079 --> 00:05:59.639 the trust our computers have in USB devices. 126 00:06:00.120 --> 00:06:02.639 For those who haven't heard of hide attacks, break it 127 00:06:02.680 --> 00:06:04.920 down for us. What are they and why are they 128 00:06:04.959 --> 00:06:05.680 such a big deal? 129 00:06:05.839 --> 00:06:09.040 Well, imagine this. You're at a conference and you find 130 00:06:09.199 --> 00:06:12.399 a USB drive labeled conference schedule. You think, oh, this 131 00:06:12.439 --> 00:06:12.920 is great, I. 132 00:06:12.879 --> 00:06:14.240 Need this, I've totally been there. 133 00:06:14.279 --> 00:06:17.279 You pop it in your laptop and boom, that seemingly 134 00:06:17.360 --> 00:06:21.240 innocent drive is actually a modified device loaded with malware 135 00:06:21.560 --> 00:06:22.600 ready to wreak havoc. 136 00:06:22.839 --> 00:06:25.519 So it's like a wolf in sheep's clothing exactly. 137 00:06:25.879 --> 00:06:30.360 And because your computer inherently trusts these USB devices, the 138 00:06:30.480 --> 00:06:34.319 malware can do a lot of damage, injecting keystrokes, installing 139 00:06:34.360 --> 00:06:37.879 back door, stealing your data, all without you realizing it. 140 00:06:38.279 --> 00:06:39.680 That's terrifying, it is. 141 00:06:39.759 --> 00:06:42.279 It's a good reminder to be cautious about what you 142 00:06:42.319 --> 00:06:43.600 plug into your devices. 143 00:06:43.879 --> 00:06:47.279 The book talks about devices like the USB, rubber ducky, 144 00:06:47.319 --> 00:06:51.160 and bash Bunny. Those always sounded kind of ominous to me, 145 00:06:51.279 --> 00:06:52.720 to be honest. Have you ever used them? 146 00:06:52.839 --> 00:06:56.560 Oh? Yeah, They're like essential tools for ethical hackers and 147 00:06:56.600 --> 00:06:59.680 pent testers. They let you simulate real world attacks and 148 00:06:59.680 --> 00:07:03.040 find weaknesses. The rubber Ducky, for instance, looks like a 149 00:07:03.079 --> 00:07:06.319 normal flash drive but acts like a keyboard, injecting keystrokes 150 00:07:06.360 --> 00:07:07.000 super fast. 151 00:07:07.160 --> 00:07:09.680 So someone could like plug that in and steal data 152 00:07:09.680 --> 00:07:11.040 without anyone even realizing. 153 00:07:11.160 --> 00:07:13.639 It's definitely possible. That's why it's so crucial to have 154 00:07:13.680 --> 00:07:15.240 strong security measures in place. 155 00:07:15.279 --> 00:07:17.560 And the bash Bunny is like the rubber Duckies, even 156 00:07:17.600 --> 00:07:18.959 more powerful cousin. 157 00:07:18.879 --> 00:07:20.839 Something like that. It's like a tiny computer that can 158 00:07:20.920 --> 00:07:22.879 launch various attacks wild. 159 00:07:23.160 --> 00:07:26.600 But the book doesn't just scare you and run away, right, 160 00:07:26.680 --> 00:07:29.720 It gives you ways to actually protect yourself from these attacks. 161 00:07:30.079 --> 00:07:33.519 Absolutely. Awareness is a big part of it. Don't plug 162 00:07:33.560 --> 00:07:36.759 in random USB drives you find lying around, especially in 163 00:07:36.800 --> 00:07:41.000 public places, keep your systems updated with the latest security patches, 164 00:07:41.439 --> 00:07:44.879 and consider using security software that can detect and block 165 00:07:45.000 --> 00:07:48.360 these types of attacks. It's about being proactive. 166 00:07:47.959 --> 00:07:50.560 So it's not just about being paranoid. It's about being 167 00:07:50.600 --> 00:07:52.920 smart and taking precautions exactly. 168 00:07:53.000 --> 00:07:56.199 It's about understanding the risks and taking steps to mitigate them. 169 00:07:56.399 --> 00:07:59.439 Okay, let's shift gears a bit and talk risk management. 170 00:08:00.000 --> 00:08:02.160 You know, I know it doesn't exactly sound like the 171 00:08:02.199 --> 00:08:05.120 most thrilling topic, not exactly a page turner, right, but 172 00:08:05.199 --> 00:08:08.199 this book actually makes it pretty digestible, breaking it down 173 00:08:08.199 --> 00:08:12.399 into this like four step process that doesn't feel totally overwhelming. 174 00:08:12.560 --> 00:08:15.079 It's like building a house, right, You wouldn't just start 175 00:08:15.120 --> 00:08:18.360 slapping bricks together without a plan. You need that blueprint 176 00:08:18.399 --> 00:08:20.839 and risk management that's your security blueprint. 177 00:08:21.000 --> 00:08:22.160 That's a great way to put it. 178 00:08:22.160 --> 00:08:25.480 It's about figuring out what could go wrong, data breaches, 179 00:08:25.600 --> 00:08:28.959 natural disasters, those kinds of things, then figuring out how 180 00:08:29.160 --> 00:08:31.480 likely they are to actually happen and. 181 00:08:31.439 --> 00:08:34.480 How bad the damage would be if they did happen exactly. 182 00:08:34.919 --> 00:08:37.960 Then you make a plan either to stop them from 183 00:08:38.000 --> 00:08:40.960 happening altogether or at least minimize the fallout if they do. 184 00:08:41.799 --> 00:08:44.480 And then the most important part, you got to keep 185 00:08:44.480 --> 00:08:47.320 an eye on things, make sure that plan is still 186 00:08:47.360 --> 00:08:49.840 doing its job. It's not a one and done kind 187 00:08:49.840 --> 00:08:50.200 of deal. 188 00:08:50.320 --> 00:08:52.600 It's a process, not just a to do list you 189 00:08:52.679 --> 00:08:59.159 check off exactly, and the book lays it out really simply, right, identify, assess, respond. 190 00:08:59.039 --> 00:09:01.279 Monitor framework anyone can follow. 191 00:09:01.360 --> 00:09:04.840 And here's a little golden nugget from the book, using 192 00:09:04.879 --> 00:09:09.039 a canban board to actually visualize and prioritize those risks. 193 00:09:09.279 --> 00:09:12.159 You know those boards like people use for project management. 194 00:09:12.240 --> 00:09:14.480 Oh yeah, with the sticky notes and the columns. 195 00:09:14.600 --> 00:09:16.159 Turns out they're awesome for security too. 196 00:09:16.279 --> 00:09:18.039 It just makes it so much easier to wrap your 197 00:09:18.080 --> 00:09:22.879 head around having different columns for like risks, assessing, addressing, monitoring. 198 00:09:22.919 --> 00:09:24.919 You can literally see the whole process laid out in 199 00:09:24.919 --> 00:09:25.360 front of. 200 00:09:25.279 --> 00:09:28.519 You and move those sticky notes along as you make progress. 201 00:09:28.879 --> 00:09:32.200 Now, let's talk about those what if scenarios. The book 202 00:09:32.360 --> 00:09:38.600 dines into business continuity plans BCPs and disaster recovery plans DRPs. 203 00:09:39.000 --> 00:09:41.799 Those are basically your safety nets for when things really 204 00:09:41.879 --> 00:09:42.360 hit the fan. 205 00:09:42.720 --> 00:09:44.679 They are and you know, it's like that old saying, 206 00:09:45.080 --> 00:09:47.879 hope for the best, prepare for the worst. That's what 207 00:09:48.000 --> 00:09:51.559 BCPs and DRPs are all about, making sure your business 208 00:09:51.559 --> 00:09:54.799 can still function even if something major happens. 209 00:09:55.120 --> 00:09:58.799 So BCP is more about keeping those essential operations going right. 210 00:09:58.679 --> 00:10:01.279 Now exactly, think like being able to pay your employees, 211 00:10:01.399 --> 00:10:03.080 serve your customers, those core. 212 00:10:02.919 --> 00:10:04.840 Functions, keeping lights on essentially. 213 00:10:04.879 --> 00:10:07.200 And then your DRP that's all about getting your IT 214 00:10:07.559 --> 00:10:10.240 systems and data back up and running as quickly and 215 00:10:10.279 --> 00:10:11.080 smoothly as. 216 00:10:10.960 --> 00:10:14.039 Possible, getting back to business as usual, right. And the 217 00:10:14.080 --> 00:10:17.639 book really stresses how vital these plans are. It talks 218 00:10:17.679 --> 00:10:21.480 about all those businesses that get totally sideswiped by disasters 219 00:10:21.519 --> 00:10:22.720 they just weren't prepared for. 220 00:10:23.000 --> 00:10:25.320 It happens more often than you'd think, and it can 221 00:10:25.399 --> 00:10:28.519 be devastating. That's why understanding your RTO and RPO is 222 00:10:28.559 --> 00:10:29.240 so important. 223 00:10:29.399 --> 00:10:32.039 RTO and RPO remind us what those are again. 224 00:10:32.000 --> 00:10:35.200 Right, So your RTO, that's your recovery time objective. It's like, 225 00:10:35.279 --> 00:10:37.399 how long can you afford to have your systems down 226 00:10:37.440 --> 00:10:38.720 before it's a major problem? 227 00:10:38.759 --> 00:10:39.080 Okay? 228 00:10:39.200 --> 00:10:42.879 And your RPO recovery point objective. That's all about data. 229 00:10:43.279 --> 00:10:45.840 How much data can you afford to lose before it 230 00:10:45.879 --> 00:10:46.440 really hurts? 231 00:10:46.519 --> 00:10:47.320 That's huge. 232 00:10:47.440 --> 00:10:50.000 These are super critical things to think about when you're 233 00:10:50.000 --> 00:10:52.039 putting together your BCP and DRP. 234 00:10:52.320 --> 00:10:54.559 It's about figuring out your breaking points based. 235 00:10:54.440 --> 00:10:56.960 Out right, so you can put the right safeguards in place. 236 00:10:57.080 --> 00:11:00.519 And then there's this concept the book mentions called time 237 00:11:00.600 --> 00:11:05.000 between failures or MTBF, So that's basically a measure of 238 00:11:05.039 --> 00:11:07.039 how reliable your systems actually are. 239 00:11:07.559 --> 00:11:11.399 That's it. It's all about understanding how often something's likely 240 00:11:11.440 --> 00:11:15.120 to break down. The higher the MTBF, the more reliable 241 00:11:15.200 --> 00:11:15.679 the system. 242 00:11:15.799 --> 00:11:18.519 So it's like a car with a high MTBF is 243 00:11:18.600 --> 00:11:20.480 less likely to leave you stranded on the side of 244 00:11:20.480 --> 00:11:21.440 the road exactly. 245 00:11:21.799 --> 00:11:23.720 You can be more confident that it's going to get 246 00:11:23.720 --> 00:11:24.159 you where you. 247 00:11:24.120 --> 00:11:26.080 Need to go. And knowing this helps you make smarter 248 00:11:26.200 --> 00:11:29.360 decisions about maintaining, upgrading, replacing your systems. 249 00:11:29.720 --> 00:11:32.279 It helps you prioritize your resources and make sure your 250 00:11:32.279 --> 00:11:35.200 most critical systems are as reliable as possible. 251 00:11:35.320 --> 00:11:37.759 Okay, buckle up, because now we're getting into my favorite 252 00:11:37.799 --> 00:11:41.720 part social engineering, hacking the human as I like to 253 00:11:41.759 --> 00:11:44.679 call it. The book totally nails it when it says 254 00:11:44.840 --> 00:11:47.240 users are often the weakest link in the security chain. 255 00:11:47.320 --> 00:11:49.799 Oh. Absolutely. We can have all the fancy tech in 256 00:11:49.840 --> 00:11:53.840 the world, but all it takes is one well crafted 257 00:11:53.879 --> 00:11:58.159 phishing email or a convincing phone call to bypass all 258 00:11:58.200 --> 00:11:59.039 those defenses. 259 00:11:59.480 --> 00:12:01.559 It's like that's saying you can lead a horse to water, 260 00:12:01.879 --> 00:12:04.600 but you can't make it drink. You can have the 261 00:12:04.639 --> 00:12:07.440 best security awareness training, but if someone's not paying attention, 262 00:12:07.759 --> 00:12:09.600 they're still susceptible, exactly. 263 00:12:09.840 --> 00:12:13.600 And that's because social engineering. It preys on our human nature, 264 00:12:13.720 --> 00:12:16.960 our trust, our helpfulness, sometimes even our fear greed. 265 00:12:17.159 --> 00:12:18.960 It's like those scam calls where they pretend to be 266 00:12:19.000 --> 00:12:19.960 from the irs or something. 267 00:12:20.000 --> 00:12:21.679 Oh yeah, those are classic examples. 268 00:12:21.799 --> 00:12:23.480 They know how to push those buttons to get what. 269 00:12:23.440 --> 00:12:25.759 They want, and they're getting more sophisticated all the time too. 270 00:12:25.799 --> 00:12:27.799 It's not just those poorly written emails anymore. 271 00:12:28.039 --> 00:12:31.519 Right, Those phishing emails used to be so obvious. Now 272 00:12:31.559 --> 00:12:33.480 they can look incredibly legit. 273 00:12:34.120 --> 00:12:36.240 It's true, so you really have to be on your guard. 274 00:12:36.759 --> 00:12:39.879 The book dies into all the psychology behind these attacks, 275 00:12:39.919 --> 00:12:44.480 talking about things like impersonation, scarcity, authority, even just like 276 00:12:44.799 --> 00:12:47.440 playing in your emotions. Do you remember that story about 277 00:12:47.720 --> 00:12:50.960 the fake email that was going around warning people about 278 00:12:51.000 --> 00:12:51.960 infected computers. 279 00:12:52.000 --> 00:12:54.519 Oh yeah, that's a classic example of phishing. 280 00:12:54.639 --> 00:12:58.840 People were freaking out, But that's exactly how social engineering works. 281 00:12:59.000 --> 00:13:02.240 It prays on those moments of panic or uncertainty, and. 282 00:13:02.240 --> 00:13:05.039 The attackers are counting on you to not think straight, right. 283 00:13:05.159 --> 00:13:08.399 They want you to act impulsively without really thinking things through. 284 00:13:08.919 --> 00:13:11.679 So what can people do to protect themselves? It can 285 00:13:11.759 --> 00:13:13.919 feel kind of overwhelming, Honestly. 286 00:13:13.759 --> 00:13:16.799 It's all about awareness and a healthy dose of skepticism. 287 00:13:17.200 --> 00:13:19.960 Think before you click on links or open attachments, especially 288 00:13:20.039 --> 00:13:24.600 from senders you don't recognize. Verify requests, especially if they 289 00:13:24.600 --> 00:13:28.559 involve sensitive information or financial transactions. If something feels off, 290 00:13:28.759 --> 00:13:29.559 trust your gut. 291 00:13:29.720 --> 00:13:33.639 It's about taking a beat, right, not just blindly following through. 292 00:13:33.960 --> 00:13:37.039 And if you're ever unsure about something, don't hesitate to 293 00:13:37.080 --> 00:13:40.440 reach out to your IT department or a trusted security professional. 294 00:13:40.600 --> 00:13:43.600 And speaking of things being connected, let's talk about the 295 00:13:43.600 --> 00:13:46.919 Internet of Things IoT. All those smart devices we had 296 00:13:47.039 --> 00:13:49.600 these days. They're supposed to make our lives easier, but 297 00:13:49.679 --> 00:13:52.519 they come with their own set of security headaches. 298 00:13:52.200 --> 00:13:55.399 Right, Oh, absolutely, and the book really digs into that. 299 00:13:55.480 --> 00:13:59.960 It stresses how important it is to approach IoT securityless. 300 00:14:00.919 --> 00:14:03.639 It's not just about the tech itself, it's about the 301 00:14:03.639 --> 00:14:06.879 people using those devices and the processes in place to 302 00:14:06.960 --> 00:14:07.519 manage them. 303 00:14:07.759 --> 00:14:10.960 So even something as simple as changing those default passwords 304 00:14:10.960 --> 00:14:12.480 on your devices. 305 00:14:11.960 --> 00:14:14.080 Huge A lot of people overlook that, but it's a 306 00:14:14.120 --> 00:14:17.840 basic security best practice. Same with keeping your firmware updated. 307 00:14:18.039 --> 00:14:21.320 Those updates often include crucial security patches. 308 00:14:21.399 --> 00:14:23.960 It's like wearing a seat belt in your car. It's 309 00:14:24.000 --> 00:14:27.679 not fool proof, but it drastically reduces your risk exactly. 310 00:14:27.840 --> 00:14:30.879 And just like with any other technology, be mindful of 311 00:14:30.919 --> 00:14:34.879 the information you're sharing with these devices, understand the privacy settings, 312 00:14:34.919 --> 00:14:37.600 and use them to control your data. It's about making 313 00:14:37.639 --> 00:14:38.639 informed choices. 314 00:14:38.960 --> 00:14:41.679 And the book also gets pretty technical talking about all 315 00:14:41.679 --> 00:14:46.600 the different networking technologies involved, like Lorawans, Zigbee, even Bluetooth. 316 00:14:46.840 --> 00:14:49.919 It does because each technology comes with its own set 317 00:14:49.919 --> 00:14:53.320 of security considerations. Lora Wan, for example, is all about 318 00:14:53.360 --> 00:14:56.120 long range, low power communication, so it's often used in 319 00:14:56.159 --> 00:14:59.639 those industrial IoT setups. Zigbi and z wave you see 320 00:14:59.639 --> 00:15:03.159 those a lot in home automation systems and Bluetooth. Well, 321 00:15:03.240 --> 00:15:05.039 Bluetooth's basically everywhere these days. 322 00:15:05.120 --> 00:15:07.679 Yeah, from headphones to smart locks, you name it. 323 00:15:07.679 --> 00:15:11.960 It's about understanding the specific risks associated with each technology 324 00:15:12.000 --> 00:15:14.279 and taking the appropriate steps to mitigate them. 325 00:15:14.480 --> 00:15:17.080 But here's where the book gets really interesting, in my opinion, 326 00:15:17.279 --> 00:15:20.279 it talks about how to use those same IoT devices 327 00:15:20.679 --> 00:15:25.240 for DIY cybersecurity projects. Ever thought about building your own 328 00:15:25.279 --> 00:15:29.080 firewall or intrusion detection system using a Raspberry pie? 329 00:15:29.679 --> 00:15:32.039 I love that the book encourages that kind of hands 330 00:15:32.080 --> 00:15:34.360 on learning. It's one thing to read about these concepts, 331 00:15:34.399 --> 00:15:36.639 but it's a whole other level to actually build something 332 00:15:36.720 --> 00:15:39.320 tangible that demonstrates those concepts in action. 333 00:15:40.000 --> 00:15:43.200 Absolutely, and it really brings those abstract ideas. 334 00:15:42.840 --> 00:15:44.960 To life, and it can be a lot of fun too. 335 00:15:45.320 --> 00:15:49.399 The book even mentions creating your own honeypot. Now that's 336 00:15:49.799 --> 00:15:50.799 next level stuff. 337 00:15:51.200 --> 00:15:55.159 Honeypots are fascinating. They're like digital decoys that lure in attackers, 338 00:15:55.159 --> 00:15:58.039 so you can study their tactics and gather intel on 339 00:15:58.080 --> 00:15:58.840 how they operate. 340 00:15:59.080 --> 00:16:01.080 So it's like setting it try to catch a thief, 341 00:16:01.360 --> 00:16:03.120 but in the digital world. 342 00:16:02.960 --> 00:16:05.960 Exactly, and it allows you to learn about real world 343 00:16:06.000 --> 00:16:09.879 threats in a safe environment without putting your actual systems 344 00:16:09.879 --> 00:16:10.320 at risk. 345 00:16:10.519 --> 00:16:13.639 Okay, let's talk about the cloud. It seems like everyone's 346 00:16:13.720 --> 00:16:15.879 using it these days, but how do you actually keep 347 00:16:15.919 --> 00:16:19.759 your data safe in this kind of nebulous digital world. 348 00:16:20.000 --> 00:16:22.919 It's a big question, and the book dives right into it, 349 00:16:23.000 --> 00:16:25.440 emphasizing the shared responsibility model. 350 00:16:25.679 --> 00:16:27.960 So it's not as simple as just trusting your cloud 351 00:16:27.960 --> 00:16:29.480 provider to handle. 352 00:16:29.159 --> 00:16:32.679 Everything, unfortunately not. It's a partnership. The cloud provider is 353 00:16:32.720 --> 00:16:36.759 responsible for securing the underlying infrastructure, like the physical servers 354 00:16:36.759 --> 00:16:40.519 and data centers, but you, as the customer, are ultimately 355 00:16:40.559 --> 00:16:43.720 responsible for securing your own data and applications within that 356 00:16:43.799 --> 00:16:44.639 cloud environment. 357 00:16:44.799 --> 00:16:47.600 So it's like renting an apartment. The landlord takes care 358 00:16:47.600 --> 00:16:50.519 of the building security, but you're still responsible for locking 359 00:16:50.519 --> 00:16:52.519 your own door and keeping your valuable. 360 00:16:52.120 --> 00:16:55.679 Safe exactly, and the book goes deep on specific areas 361 00:16:55.679 --> 00:17:00.720 of cloud security, like securing Kuberneteskubernetes. 362 00:16:59.200 --> 00:17:01.440 That's a big one in the cloud world these days. 363 00:17:01.279 --> 00:17:06.240 Right huge. It's a powerful platform for managing containerized applications, 364 00:17:06.920 --> 00:17:10.359 but it can also be pretty complex to secure properly. 365 00:17:11.079 --> 00:17:13.759 The book highlights the importance of securing the control plane, 366 00:17:14.079 --> 00:17:18.200 making sure those container images themselves are secure and implementing 367 00:17:18.240 --> 00:17:23.240 network security controls. It's about understanding the unique security challenges 368 00:17:23.240 --> 00:17:24.720 that come with this kind of technology. 369 00:17:24.920 --> 00:17:28.000 So it's like Kubernetes is this awesome power tool, but 370 00:17:28.039 --> 00:17:30.319 you need to know how to use it safely, precisely. 371 00:17:30.400 --> 00:17:33.400 The book also talks about database security, which is I mean, 372 00:17:33.519 --> 00:17:36.559 that's huge for any organization that's storing sensitive information in 373 00:17:36.599 --> 00:17:36.960 the cloud. 374 00:17:37.000 --> 00:17:41.240 Right, databases are like gold mines for attackers, so protecting 375 00:17:41.319 --> 00:17:44.279 them should be a top priority. The book talks about 376 00:17:44.359 --> 00:17:49.559 using strong passwords, encrypting the data, implementing strict access controls, 377 00:17:49.920 --> 00:17:54.599 and regularly backing up your databases. It's all about minimizing 378 00:17:54.680 --> 00:17:57.519 the risk of data breaches and making sure you can 379 00:17:57.559 --> 00:17:59.640 recover quickly if something does happen. 380 00:18:00.000 --> 00:18:02.559 Having a vault inside your fortress exactly. 381 00:18:02.759 --> 00:18:05.799 You need those extra layers of protection for your most 382 00:18:05.960 --> 00:18:07.000 valuable assets. 383 00:18:07.279 --> 00:18:09.319 And the book doesn't just leave you hanging right. It 384 00:18:09.359 --> 00:18:11.599 gives you an overview of all these different cloud security 385 00:18:11.640 --> 00:18:13.359 tools you can actually use it does. 386 00:18:13.480 --> 00:18:16.319 It covers a wide range of tools, from security information 387 00:18:16.480 --> 00:18:21.839 and event management sign systems to cloud access security brokers 388 00:18:22.279 --> 00:18:27.519 CSPs and vulnerability scanners. There's something for everyone, regardless of 389 00:18:27.519 --> 00:18:29.319 their specific needs or budget. 390 00:18:29.440 --> 00:18:31.599 So it's a good starting point for anyone who's feeling 391 00:18:31.640 --> 00:18:33.480 a little lost in the world of cloud security. 392 00:18:33.599 --> 00:18:36.240 Absolutely, it can be overwhelming, but the book does a 393 00:18:36.240 --> 00:18:39.160 great job of breaking it down and providing practical guidance. 394 00:18:39.480 --> 00:18:42.079 And speaking of practical guidance, let's talk about web applications. 395 00:18:42.440 --> 00:18:44.880 Those are prime targets for attackers, right. 396 00:18:45.079 --> 00:18:49.880 Unfortunately, yes, Web applications are often the public facing entry 397 00:18:49.880 --> 00:18:53.200 points to an organization systems and attackers are always looking 398 00:18:53.240 --> 00:18:56.799 for ways to exploit vulnerabilities in these applications. 399 00:18:56.279 --> 00:18:58.680 And the book really dives deep into this whole world, 400 00:18:58.920 --> 00:19:02.079 talking about common attaps acts like XSS and SQL injection. 401 00:19:02.559 --> 00:19:05.440