<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rafal Los on Medium]]></title>
        <description><![CDATA[Stories by Rafal Los on Medium]]></description>
        <link>https://medium.com/@blogwh1t3rabbit?source=rss-153a543f560d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*T7ii7qaPwzCWZqfPP0A7Yw.jpeg</url>
            <title>Stories by Rafal Los on Medium</title>
            <link>https://medium.com/@blogwh1t3rabbit?source=rss-153a543f560d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:38:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@blogwh1t3rabbit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Show Your Work]]></title>
            <link>https://blogwh1t3rabbit.medium.com/show-your-work-4d820cf3850c?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d820cf3850c</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[decision-making]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Thu, 30 Jan 2025 19:41:51 GMT</pubDate>
            <atom:updated>2025-01-30T19:41:51.899Z</atom:updated>
            <content:encoded><![CDATA[<p>I was one of those kids in school. I got the right answer, but I couldn’t be bothered to show my work. Why did it matter anyway, I got the right answer. Who cares if I didn’t write the 11 steps it took to get there?</p><p>Well, as I got older I learned that more and more often the way you got the answer was just as important — and in some cases <em>more important</em> — than actually getting the right answer.</p><p>Here’s why this applies to <strong>right now</strong> in your career.</p><h3>There are right way to eat a Reese’s</h3><p>I’m not trying to sound edgy here — I mean it. In cybersecurity we don’t have clear-cut “right answers” when it comes to what we do. There are what <em>feels like</em> obvious “right answers” but that’s wishful thinking, at best. Everything is a trade-off between performance, security, usability, and functionality. Every risk calculation you do in your head, and every decision you make on-the-fly, has to be accounted for. <strong>That</strong> is the part that matters.</p><p>When you’re called to testify in court on why you applied a stringent policy of restricting outbound traffic from network segment A, but not network segment B, the people asking the questions will try and paint you as making the “wrong” answer. In fact, you may have made the <em>best answer</em> at the time and with the information you had available to you.</p><p>This is why every regulation that’s worth it’s paper tells you in broad terms <em>what</em> you need to accomplish, not <em>how</em> you need to accomplish it. Because there are times when applying the appropriate control will halt or severely degrade business capabilities that is above the risk tolerance level — so the security control gets shelved with a risk acceptance of the lower risk.</p><h3>Show your work — it matters more</h3><p>The reason you’re being asked to justify your decision, show your work, is because people want to know <strong>why</strong> you made that decision. Why that server that was compromised did not get the latest Patch Tuesday patch but rather a temporary work-around. Yes, you were compromised because a compensating control was put in place, and a risk was recorded as accepted. Yes, you were compromised. Yes, you can show why that risk was taken, the decision criteria, and who was involved.</p><p>That’s what we want to see, after all. Those of us who have been doing this a long enough time know there will always be the next compromise, and the next breach. We’re over the faux outrage and pretending that “this could have been prevented if only…”. We want to know that someone thought things through, carefully, and came to a conclusion. Even if we don’t like the conclusion, and even if it led to a bad outcome, we just want to know what factors were considered, and why the decisions that were made, were made.</p><p>So you see, kids, the next time you’re taking an algebra test, or a physics exam, show your work. Maybe you’ll get the wrong answer because you added 2 plus 4 wrong in the heat of an important test — but if you show how you got there you’ll demonstrate understanding of the mechanics and decision-marking. That should get you most of the credit because at some point the computers will do the math for us, but they likely won’t have the graymatter to make difficult, squishy, gut-base decisions like we can.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d820cf3850c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Complex Systems Fail in Complex Ways]]></title>
            <link>https://blogwh1t3rabbit.medium.com/complex-systems-fail-in-complex-ways-13c209db1237?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/13c209db1237</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[outage]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Fri, 17 Jan 2025 21:23:26 GMT</pubDate>
            <atom:updated>2025-01-17T21:23:26.459Z</atom:updated>
            <content:encoded><![CDATA[<p>In case you’ve not come up for air in the last 36 or so hours, CapitalOne is having a bad few days. I’m not going to <a href="https://www.forbes.com/sites/tylerroush/2025/01/17/capital-one-outage-continues-for-second-day-as-thousands-report-deposit-issues-heres-what-to-know/">retell the story</a> which is hopefully resolved by the time you read this, but something sticks out in my mind that I don’t hear discussed often enough when these types of incidents happen.</p><h3>The Outrage</h3><p>Inevitable is the outrage you see on the socials when a large company has an outage. People will resort to shaming and as one of my good friends likes to say “talking out of their a**” when they understand very little about some of these highly complex systems. Complex systems like, for example, banking.</p><p>As someone who received physical checks I would have to go to the bank to deposit and get physical cash in return after a few days, I’m still in awe of how far technology has come. I also understand more than the average person on the street just how complex the systems and processes are that take a paycheck from your employer and magically make it show up in your account where you’re able to debit against it — that’s magic. There aren’t dozens of computer-based processes, there are <em>thousands</em> in some cases.</p><p>So when people make these outrageous “How dare they have an outage” comments I both roll my eyes, and perk my ears. I always wonder if there’s something truly novel going on, or if someone tripped over a power cord and blacked out a data center that was pivotal for routing packets from point A to point X. More often than not, people who freak out have no idea how complex things are, and maybe they don’t care.</p><h3><strong>Actual Reality — Yeah, it’s “Complicated”</strong></h3><p>I’ve worked <em>inside</em> the banking system. I’ve done security for a company that was a big chunk of the process from when you swiped a credit card, to where a product magically showed up at your door. Sometimes the answers are simple — “The circuit that supports traffic from this city to that one was cut by a guy named Mike with a backhoe.” Sometimes though, and more often than not, the answer is “it’s complicated”.</p><p>I’d love it if we lived in a simple world. Company X makes a poor decision, and it results in outage Y. When that happens, sure, let’s go pummel them on social media until they learn their lesson (I’m kidding, obviously…). But the world just isn’t that simple. With hundreds of systems, processes, and thousands of different pieces of technology that have to work just right to do what we want — when things fail it’s not simple. Luckily there is technology out there to help us troubleshoot (disclosure: I happen to work for a company that does this) and pinpoint issues quickly. But if your network or applications aren’t instrumented in a way to be able to do this — you’re left guessing and checking. Oh, and those 12+ hour long conference bridges with dozens of people who all “try something real quick” the result of which is a new problem. We fumble and stumble our way to a fix, and in some really scary cases things “just start working” and we’re not sure why. I’ve been a part of that too.</p><p>But complex systems like banking, logistics, healthcare, manufacturing, retail supply chains — these things can fail in minute or massive ways. Each time we work hard to fix the problem, then afterwards after we’ve had a few hours sleep and some time to think about it we go back and divine what lessons we should learn and apply that to our principles and practices and improve. Well, some of us do that. Some of us out there just shrug our shoulders, tell people “it’s complicated, sorry we couldn’t have done anything about it” and move on.</p><h3>Plan, Anticipate, Respond, Learn</h3><p>The take-away from any big failure is the way we can improve. Here’s what you should be doing, or at least how I see it.</p><p><strong>Plan</strong></p><p>Set your organization, your infrastructure, and your applications up as much as you can to be resilient. Resilience is important, but it is not a magic wand that makes outages go away. Plan for the day when things will go horribly sideways so that you have available telemetry, staff, and processes to figure out where things broke, how, and what you’re doing to do to remedy the situation.</p><p><strong>Anticipate</strong></p><p>Now, try your best to look at available telemetry and get ahead of the outage. If you start seeing “Zero Window” responses climbing for any particular endpoint of an application you can be fairly sure that call to the helpdesk telling you the “application is down” is coming. If you can anticipate outages and failures you’re not bulletproof, but you can tell your customers and partners that you’re on it before they even notice the issue. That’s worth its weight in gold in most situations. That capability to anticipate also requires you to do a lot of built-in information gathering, profiling, and analysis — stuff you can’t easily do after it’s all built and launched.</p><p><strong>Respond</strong></p><p>When it goes south, whether it’s catastrophic failure or a slow-down with minor impact, be responsive and decisive. Take action that remedies the situation and ensure that you do it as quickly as possible with sensitivity to all of the people that are going to freak out. Even a great response can be completely undone with poor PR. Remember that. Response is as much about how fast and accurate your fix it, as it is about how well you explain it to those impacted.</p><p><strong>Learn</strong></p><p>If you learn nothing from an outage — no matter how big or small — you’re wasting opportunity. There is always something to learn. Even if the outage is at a third party that you have <strong>no control over</strong>, there is still something you can learn, and thus apply it internally to be better. Never waste an opportunity to learn, see things from a different angle, and gain some new insights. As little kids many of us wanted to be Sherlock Holmes — and then we got into IT. Well…don’t give up on your dreams, go figure out that root cause and learn from it!</p><h3>Sh!t happens, it’ll happen again</h3><p>If you’re one of those people who make comments like “I’m never using that company again because they had an outage” — we probably won’t see eye to eye. Everything fails, on a long enough timeline, in certain high-stress situations. Nothing is perfect. Your bank will have a bad day. Or two. But they’ll make it right, and the next time something like what just happened presents itself they’ll be ready for it if they learned something.</p><p>Your car, your relationship, your dog, and your TV — all of these things will fail or have issues at some point. But the issue or outage isn’t the end of the relationship, rather, it’s just another bump on the road of life, and remember these things are complex. It’s happened before, it’ll happen again, and you’ll live though that one too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13c209db1237" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Burned Out on Trust]]></title>
            <link>https://blogwh1t3rabbit.medium.com/burned-out-ontrust-e4d32e40b3d0?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4d32e40b3d0</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[zero-trust]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Thu, 02 Jan 2025 20:36:24 GMT</pubDate>
            <atom:updated>2025-01-07T00:09:47.007Z</atom:updated>
            <content:encoded><![CDATA[<p>My friend, and brilliant CEO, <a href="https://www.linkedin.com/in/patrickjdennis/">Patrick Dennis</a> posted an article on the brittleness of trust, back in June 2023. I’ve been thinking a lot about it, and I’m dedicating a podcast to it on Monday, January 6th (<a href="https://www.extrahop.com/blog/how-brittle-is-trust-in-an-era-of-continuous-compromise">link here</a>). The more I think about this topic, the deeper down the rabbithole (<em>pardon the pun</em>) of despair I go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJAbhp0EBC72hZiZdnFk-A.png" /></figure><h3>The Premise</h3><p>Trust has been a war on <em>at least</em> two fronts. First there’s the digital — you can call this the <strong>Cyber Security</strong> perspective. The second is societal — where misinformation, disinformation, and propaganda live. These two fronts have been rapidly flanking the trust that people and governments have spent decades (maybe longer) building…and the stress cracks are starting to become highly visible.</p><p>What I mean to paint for you is a mental picture of trust as both a concrete and abstract thing. Let me explain.</p><p>The concrete part comes in, for example, when computers interact, or autonomous systems exchange data. A second example from the real world is where someone calls you on the phone and tells you that you owe some company money and the person on the phone is offering you a chance to settle the debt or else there will be dire and urgent consequences. In both examples, these interactions need to make rapid and often only slightly informed trust decisions. Some of us will tell you that you should always default to “no” when the question “Can I trust this?” is asked — but as I’ll explain later, that becomes a practical impossibility faster than many of us are comfortable admitting.</p><p>The abstract is a little more difficult to grasp. The concept of trust, in the abstract, is a philosophy question. Each one of us and all of our computer systems make millions of <em>trust decisions</em> a day. Right, millions. You teach your children never to trust strangers — but at some point trust may be a life and death decision that they have to make…and potentially trust a total stranger. Don’t trust strangers — except teachers, mechanics, your bus driver, the person on the radio reading you the weather …you get it. Trust in the abstract is the default for humans. In spite of everything you’re told fron the time you’re born, you default to trusting someone <em>unless they give you a reason not to</em>.</p><h3>Current State of Trust</h3><p>I think I can make a reasonable argument that trust as both an abstract concept and a concrete thing is being eroded faster than ever before in human history. Two things are driving this, and as someone who works in Cyber Security — I’m genuinely anxious about the future.</p><p>The first front comes in the form of digital, or technology. Cyber Security professionals have been screaming from the mountain tops for over a decade that you can’t trust technology… “don’t click that link”, “don’t trust that message”, “don’t open that email” and the like. Assume everyone is trying to hack you, and don’t trust anything <em>external to the company</em>. And thus the arms race between threat actors and your internal security teams was born. Attackers will exploit your trust and appear as though they are trustworthy to get you to give them access. Here’s the thing — phishing lures have become so good that even some of the best cyber security professionals fall for them! Furthermore, it’s impractical not to open external links, emails, and documents — unless you don’t conduct remote business or ever get a photo from a friend, or a PDF from Human Resources. At some point you have to get your job done, and the difference between legitimate email and attacker is so difficult to distinguish that even the most skeptical are still caught.</p><p>The second front comes on the societal, or social, side. Whether it’s that call from the “Social Security Office”, or a text telling you that a package is stuck in processing with insufficient postage and you just need to pay the difference to get your package, or social media postings breaking news that your favorite Congresswoman is actually a lizard creature — it’s pretty difficult to distinguish between real and fake. Let’s not forget that AI can now create really, really life-like “deepfakes” — Joe Biden dancing the salsa, or Taylor Swift exposing the lizard people. It’s so difficult to tell the difference between real and fake that most people can’t, especially when it’s not an obvious one like the examples I’ve picked. The world isn’t as simple as when I was a kid — never to get into a stranger’s van no matter how many free puppies he has in there for you, duh.</p><h3>Erosion on Both Fronts</h3><p>Where we stand today is that the digital and the social have been blended to a point where I can’t tell easily if a news story I see on social media is real…or fake. If you’re laughing to yourself because you’re sure that you could spot the difference, think again.</p><p>I’ve carefully avoided politics in this post, but I’ll give you one very clear examples of the converged erosion of trust. The calls that voting machines were hacked and swung the election in favor of one candidate or the other are the perfect example. In every case I’ve seen people took <em>theoretical</em> vulnerabilities, or even real ones but out of context, and created an entire narrative of what <strong>they claim happened</strong> based on a combination of peudo-tech, conspiracy theory, and misinformation. If you don’t know enough to dispute individual facts, and most people wouldn’t, then it’s reasonable that you would fall for these claims. The reality is that the point wasn’t to win the argument over a specific political race, or voting machine vendor — it was to sow distrust in the system as a whole. If Americans don’t trust the voting process, our Democracy is dead in the water… A combination of outright fake news, with trolling on all social media platforms, influence peddling to those “influencers” some of us get our “news” from (God help us all), and inherent distrust of technology that well-meaning Cyber Security campaigns and policies have sewn …and voila!</p><p>Where I believe we are right now, as a society, is at the intersection of being <strong>overwhelmed</strong> with trying to stay hyper-vigilant for trust decisions, and being <strong>exhausted</strong> from that process day in and day out. We have been scared into not trusting anything, but that’s impractical in daily life so we do our best to make the best decisions we can with the limited knowledge we all carry. And we’re exhausted.</p><h3>Burnout is Inevitable</h3><p>Many people whom I’ve spoken with — family, friends, co-workers, and colleagues — are starting to feel burned out on trust. Technology has largely failed to bring us the answers to implement broadly in society, and in fact, things like AI have only made it much, much worse to try and make trust decisions. The Chinese, Russians, and others are doing their best to make sure you don’t trust <em>the media</em>, and let’s face it the mainstream media has torched any trust we had in them anyway. Technology companies and cyber security professionals are telling you that you can’t trust that piece of hardware or software because it’s potentially vulnerable, while typing away on their Chinese-made mobile devices. In a world increatingly going all-digital, the only things you can trust is what you can physically touch and see. These are incompatible, and I believe that the next decade or more will be a very rough time for <em>trust</em>, partly because cyber security has failed to provide answers to what, who, and how to trust.</p><p>I’m burned out, and you probably are too. The big question is where do we go from here? I am doing a lot of thinking on this, and I’ll write more as I think of, or find, some decent answers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4d32e40b3d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[More Difficult Means More Secure, Right?]]></title>
            <link>https://blogwh1t3rabbit.medium.com/more-difficult-means-more-secure-right-27be0c55613c?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/27be0c55613c</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Fri, 09 Feb 2024 17:26:48 GMT</pubDate>
            <atom:updated>2024-02-09T17:26:48.390Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been involved in an unnatural amount of conversation lately about the failings of the “cyber security” industry. So much so that it has be thinking that there may be something going on out here — maybe it’s dawning on people that the utter madness of repeating the same failing strategies over and over isn’t going to suddenly turn into winning tomorrow.</p><p>Enter LinkedIn. My former colleague and swell guy, <a href="https://www.linkedin.com/in/billbernardchicago/">Bill Bernard</a>, posts these little things on Fridays where he relates something real-world to security. You should be following him. And today’s was a doozy. Take a minute and go read his super-short post, <a href="https://www.linkedin.com/feed/update/urn:li:activity:7161717819334750208/">here</a>. Then take a minute to soak that in, including the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*JbqVwHx8ehOuO4017Y5TcA.png" /><figcaption>borrowed from Bill’s original post</figcaption></figure><p>I looked at that image for a minute because there was another lesson in it for me. Then it hit me.</p><p>The last ~25 years or so that I’ve been associated with the field of information, network, enterprise, or cyber security has been an escalation in making critical tasks more difficult to the point of absurdity.</p><p>I don’t know if anyone’s come up with a name for this phenomenon yet so I’ll outline it here in case it’s actually original’ish. Maybe we call this Rafal’s theory of cyber equilibrium …or something.</p><p>This whole thing revolves around the idea that you can’t just make something more difficult to use and assume that this means better security. It doesn’t. Your user base will work against you to find ways to use the system and do their jobs bypassing all those glorious security measures. And what you’re left with is an insecure system, with a ton of security in it, that is out of balance. Angry users. Poor security. I think I just described the last 25 years in security…didn’t I?</p><blockquote><strong>Theory</strong>: Users of a system are willing to tolerate a certain amount of additional complexity or difficulty of use for the sake of security. When measures are added that push beyond this limit, user behavior adapts to restore balance in favor of usability, thereby reducing or eliminating the security benefits of the added complexity.</blockquote><h3>Cybersecurity professionals have largely mistaken making something more difficult to use, with making that thing more secure.</h3><p>I don’t think we do this on purpose, to hurt usability and productivity — but I think it’s a side effect of the way we’ve been thinking. Bill mentions password + PIN as one example. I’ve seen it, and it’s been a head scratcher. On the surface, it’s “two things you need to know”, but in reality it’s not actually increasing the difficulty in breaking into that account because those two things (password, pin) will likely be written down or stored in the same place so…</p><p>I’ve believed for a long time that the most secure systems are the easiest and more simple — because adding complexity increases the chances of getting something wrong. It is in that simplicity that cybersecurity professionals need to work. But that requires us to show up when the system is being designed, and work our mechanisms that increase security right into the system. We need to think “<em>How do I minimally disrupt the intended usage of this system, while making it more secure?</em>” That’s not trivial — but it can’t be that difficult.</p><p>Having worked in a large enterprise as a security architect, I know how difficult it can be to shimmy security components and ideas into an application, system, or product. It takes compromise, and system-level thinking. It means you have to consider the entirety of the system and its intended use, not just the security measures you’ve been taught to jam in.</p><p>So the next time you’re looking at adding security into something — ask yourself the big question.</p><h3>How can I add security without increasing complexity and reducing usability, so users don’t work against the security measures meant to protect them?</h3><p><strong>THAT</strong>, my dear reader, is the $64,000 question. Start there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27be0c55613c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Simple Rules for Publishing Your Hot Take]]></title>
            <link>https://blogwh1t3rabbit.medium.com/3-simple-rules-for-publishing-your-hot-take-d4f9f0126806?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4f9f0126806</guid>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Fri, 10 Nov 2023 17:52:31 GMT</pubDate>
            <atom:updated>2023-11-10T17:52:31.452Z</atom:updated>
            <content:encoded><![CDATA[<p>We humans just can’t help ourselves sometimes.</p><p>Like clockwork — within minutes of an announcement of a security incident, breach, or other bad news the flood of comments and hot takes pours out like an open fire hydrant in July. Now, look here, I can appreciate that some of you are trying to provide analysis but the vast majority of your takes are ill-informed, poorly communicated, and frankly make you look silly. About half the time I find myself asking “Did they even bother looking at the details of the thing, before offering an opinion?”</p><p>I don’t think I’m alone in feeling like we could use a little less ill-informed verbal vomit in the trade publications, blogs, and social media. So with that in mind, here are 3 <strong>simple rules</strong> I suggest we all use before we post, provide a quote, or jump in front of a camera.</p><ol><li><strong>Take a minute to inform yourself first </strong>— I can’t believe I’m writing this but for the love of all that is good, <strong>please read</strong> before you speak. If it’s an article you’re commenting on — <strong>read it first</strong>. I don’t mean skim it. I also don’t mean read the ‘summary’ that social media platforms give you. I mean, read the ******* article, top to bottom, carefully. Then go read another. And a few more. I say this as someone who was once hot-headed and prone to jumping in with in opinion before being fully informed. Age has taught me that I was being stupid. I have since learned my lesson. Just don’t be “that person”, ok? Incidents are <em>very rarely black and white</em>, and there are often 3 sides to every story. Make sure you read the majority opinon, the dissent, and the fringes. If you’re brave, read the comments section too. Understand that trade publications and “news” outlets write for clicks, so they tend to, how do I put this nicely, “sensationalize” things for dramatic appeal. Think about those people living through the moment, and ask yourself if your take will be informative, or if you’re doing it to join in the feeding frenzy at someone else’s expense. Speaking of which…</li><li><strong>Practice empathy (“don’t be an asshole”)</strong>— This is difficult for many of the people in cyber security — maybe because we’re just broken, or not wired for it, but we suck at empathy. Remember kids, the thing you’re dying to get your comments published on may be someone’s very, very bad day. 9 out of 10 times you’re making comments about the victim of an unfortunate situation, or even a crime. I’ve learned that being an asshole may get you some air time, but at the end of the day you’re still an asshole. A great reason to take the time and practice empathy is that you never know when you’ll be the next dumpster fire everyone is talking about. I’ve read comments where someone takes a shot at a breached company for, as an example, not being fully patched only to end up in the news <em>in the same week</em> for the exact same thing. Whoops. Don’t be an asshole, I can’t stress that enough.</li><li><strong>Ask yourself how this hot-take will age</strong> — Have you ever accidentally read some hot-take that someone posted, quoted, or published and thought to yourself “Well, that aged poorly”? I suggest you always think of that moment when you’re posting something about a <strong>developing</strong> current event. So many times the information that’s available in that moment will write one narrative, and you’ll be asked to comment on that narrative. But keep in mind that developing situations often change many times before they’re clear… so the worst-case for you is that something you say ages poorly and you once again, look stupid. I can think of no better illustration (outside of cyber, even) than most of the media outlets that commented on the hospital in Gaza that was blown to smithereens. Allegedly. A terrorist organization claimed Israel’s IDF hit the hospital with a missile and killed “thousands” of innocent civilians. News programs and writers fell all over each other to be the first out there to criticize the horrible thing the IDF had done. Well, it turns out, as often is the case, that the terrorists (Hamas) who put out the information were…lying. When the truth came out a day or so later, the evidence was crystal clear that Hamas had a rocket mis-fire and they hit their own people, and they killed some. But the damage wasn’t even remotely close to the original narrative, and certainly Israel wasn’t to blame. Some newspapers and programs had to walk back their stories. Some silently changed their articles or narratives. Don’t do this. It shatters your credibility, if you care about this sort of thing. Consider how the event will develop, where we are in the fact-finding journey, and how much we know collectively right now. Understand that “those who know, can’t talk, and those who don’t know, can’t shut up” is a real thing. Again, don’t be one of those people.</li></ol><p>There you have it. Three very simple rules that could not only save your reputation, but maybe your career.</p><p>If you care about that sort of thing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4f9f0126806" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical Demos — Getting to Something Compelling]]></title>
            <link>https://blogwh1t3rabbit.medium.com/technical-demos-getting-to-something-compelling-2af07469cfc5?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2af07469cfc5</guid>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Mon, 21 Aug 2023 20:23:12 GMT</pubDate>
            <atom:updated>2023-08-21T20:23:12.366Z</atom:updated>
            <content:encoded><![CDATA[<h3>Technical Demos — Getting to Something Compelling</h3><p>I have to get this off my chest — most of the technical demos I’ve seen in the last decade have been awful.</p><p>There, I said it, now let me explain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Jn8BWgWutTvlWwUMQxbdA.png" /></figure><ul><li><strong>Lack of flexibility </strong>— Someone is teaching pre-sales people to, as one of my mentors once said “Show up and throw up”. They join a call, the sales exec points to them, and they do one of two (or both) things. They walk through the sales deck and explain all of the technical intricacies, and then they “do the demo”. In about 75% of the cases the <em>I’ve personally experienced</em> on both sides of the table (buyer, and seller) there is a complete lack of creativity in how they explain to the prospective customer what they’re about to see. It’s just a script they follow, click here, look at this doodad, click here, wow look at this, click, click, end of demo.</li><li><strong>Lack of context — </strong>What, “No way!”, you say? We’re clearly not in the same meetings. My first job where I was doing for-real pre-sales work, a guy named Bill Weinberg kept telling us that we should do research on our prospective customers before we got in front of them. Those words echo back across these last 15+ years loud and clear. Especially when I watch someone talk about their product or service in a way that is completely irrelevant to the buyer. Is it really too much to ask that if you’re selling SOC optimization technology, you should at least look up how big the customer’s SOC is, and whether they have open roles?</li><li><strong>Lack of vision</strong> — It’s strange to me that when you’re talking about a widget, you don’t see the broader implication of your widget in the company’s ecosystem or processes. Let’s say you’re selling vulnerability management software. Yes the features are nice and but colors and dashboards and knobs and dials are cool. But why does that prospective customer actually <em>care</em> about what you’re selling. One reason may be compliance driven — but being bullied into buying an item that checks a box means they’re going to go with the cheapest, least complicated thing to accomplish the task. Your thing is priced higher and has way more features…so why do they <strong>need it</strong>? Maybe you’re helping reduce time spent by the team in triage of vulnerabilities, or maybe you the thing you’re selling will increase productivity, or maybe it’ll just keep people from making poor choices. Maybe it’ll help the CIO hold line of business owners accountable for open issues in their business. Any one of those may be “<em>the thing</em>” but I am willing to be if you don’t at least look up off those dashboards your outcome as a sales engineer will be less than ideal.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*IvwgujYU0MQdynxM7HhKnw.jpeg" /></figure><h3>You didn’t tell me a story</h3><p>Remember the line “<a href="https://www.youtube.com/watch?v=9UspZGJ-TrI">Sell me this pen</a>”? You have to have some compelling reason, a story or some urgency. The catch is, you can’t make it up or you’re selling bullshit. Nobody wants to buy bullshit. And the buyers you <em>actually want</em> have good bullshit detection. So you have to tell them a story.</p><p>Imagine you’re in the most beautiful setting you’ve ever seen in your life. Your family is there, and it’s just a picture from a postcard, or Southern Living magazine. You want to capture the moment forever, for your children, and their children. It’s that kind of moment. You have your camera and you pull that camera out to take a photo of this amazing moment. But you… you bought the cheap batteries because you thought all batteries are the same. And now they’re dead. And while you have your camera, it’s no good to you when the batteries are dead and you can’t capture the most beautiful setting you’ve ever seen in your entire life. You put batteries in before you left the house but you didn’t know they were already low. Batteries can’t tell you they’re low. My batteries… the batteries I’m selling will tell you… they have an indicator that will tell you how much power they have. With my batteries you will never again be in a position like you’re in right now — beautiful scenery, perfect picture, and you’re stuck with dead batteries.</p><p>Tell the story…</p><p>Sure you can go through and tell the prospective customer about the technical details of these batteries. The type of core the are based on, that the design has 100 patents, and that every feature available that distinguishes them. But without telling me that story, the “low power indicator” is just something that’s a nice to have. In that story, if I’ve done my job, that power indicator is essential and you <strong>must have it</strong>.</p><p>That’s how you turn a bunch of features into a must-have. You tell a good story. Storytellers are rare. Storytellers that can do it with a technical product are unicorns that drop gold bricks when they poop.</p><h3>Features I’ll likely forget after this call</h3><p>This may be something you don’t want to hear, but the people who make decisions and sign the big checks for the widget you’re selling probably won’t remember 90% of the features you’ve just rattled off in your technical demo. Now, I’m not saying <em>features are not important because obviously they are</em>, but have some awareness of who is in your audience and what they want to hear. Technical evaluators want to hear about the technical features and go down the technical rabbit hole (all pun intended). The executive sponsor will be looking for the big “why” — what makes your thing compelling to them. Then those people will look at their technical evaluators and ask them “Does this do the things you need?” And if the answer is yes, and you’ve told a good story and related it to the value they seek, you’re a winner. But if you can’t relate the widget to the business value the executive is looking for, the features don’t matter.</p><p>Moral of the story: features are often forgotten shortly after the meeting. Unless your prospect is taking great notes, they’ll forget half the things you told them. And, unfortunately, unless you’ve told a killer story that sticks around in their brain (remember my pitch on those batteries?) then they’ll forget what makes you special or why they should be buying your thing. At that point, you’ve lost.</p><h3>Be a Story Teller</h3><p>The best and most successful people I know — in the vendor world — are relatable, technically astute, and can tell a great story that blends in the value and capabilities into a “sell me this pen” moment that you won’t forget. Please, can we have more of this?</p><p>If you have this magical skillset, <strong>teach others</strong>.</p><p>If you don’t have this skillset, <strong>seek someone who can do it out and learn.</strong></p><p>What do you think? Am I wildly off? Do you see this too? What about you buyers out there — does this resonate?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2af07469cfc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dumb AI, Dumber Humans]]></title>
            <link>https://blogwh1t3rabbit.medium.com/dumb-ai-dumber-humans-8e82d113d4ba?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e82d113d4ba</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[futurism]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Fri, 04 Aug 2023 14:56:11 GMT</pubDate>
            <atom:updated>2023-08-04T14:56:11.627Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a movie about “AI becoming sentient and wiping out humans” — we all know it and it’s scary as hell. So when OpenAI started talking about how magical their AI was, a small section of the human population cringed a bit. Then we heard that AI was at times indistinguishable from an actual human being, and that AI could write better, manipulate humans in real life ( <a href="https://www.psychologytoday.com/us/blog/freedom-of-mind/202304/how-ai-can-be-used-to-manipulate-people">https://www.psychologytoday.com/us/blog/freedom-of-mind/202304/how-ai-can-be-used-to-manipulate-people</a> ), and was doing all kinds of interesting things.</p><p>Naturally, the Spidey sense went to 11.</p><p>Then this …</p><p><a href="https://futurism.com/the-byte/stanford-chatgpt-getting-dumber">https://futurism.com/the-byte/stanford-chatgpt-getting-dumber</a></p><p>And frankly, now I’m torn.</p><p>Between the stories of autonomous robots falling into water fountains at the mall, and the above referenced AI report on how it’s getting dumber the longer it exists — something feels off.</p><h3>The Blind leading the Dumb</h3><p>So look, I’m not on either end of the spectrum at this point. I neither believe that AI will kill humanity in a matter of minutes, nor do I believe that AI is a temporary technological wünderkind. What I do believe we have is the typical thing that happens… stop reading at the point you disagree.</p><ol><li>Someone invents new technology</li><li>Said technology is massively hyped, to the point where the hype far out-paces any reality</li><li>Overhype leads to mass reactions at the fringes: one side believes this is mankind’s salvation, the other thinks it’s our doom</li><li>Marketing people sieze the opportunity to convince analysts this is better than sliced bread and the invention of vulcanized rubber</li><li>Analysts, because if you’re not first, you’re last, want to be on the leading end of a hype curve — hype up the technology and have magic quadrants and waves and all manner of predictions for market domination</li><li>Companies who have no business using the technology rush to use it somehow, so they can use the buzzword on an earnings call to show how progressive and technologically leading-edge they are</li><li>Technology proves to be problematic, causes some potential negative market or real-life impact when it’s inserted into nonsensical applications “My toaster now has AI to tell me when my bread is perfectly toasted.”</li><li>It’s too late, because the over-hyped limited-use tech is so over-blown and over-hyped that it’s virtually meaningless and (“threat intelligence”, “XDR”, “AI powered”) and we don’t remember why we cared in the first place</li></ol><p>So AI is being pushed into <strong>literally everything</strong> now, because it’s going to change your life in every way, and we’re not even sure it’s not going to a) kill us accidentally, or b) kill us on purpose.</p><p>Oh, right, and now there’s a call for a ‘pause on research’ while the collective “they” start to think about societal and ethical implications of <em>artificial intelligence</em> (oxymoron, in my book).</p><p>Maybe what I’m saying is “Get off my lawn, you crazy kids” — or maybe I’m just concerned that in the race to hype up the latest technical advancements and shove it into our daily lives we haven’t actually conducted enough testing to figure out if that’s even a good idea.</p><p>But…what do I know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e82d113d4ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security Snapshots vs Real-Time World]]></title>
            <link>https://blogwh1t3rabbit.medium.com/security-snapshots-vs-real-time-world-281ed22e3867?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/281ed22e3867</guid>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Fri, 21 Apr 2023 21:40:35 GMT</pubDate>
            <atom:updated>2023-04-21T21:40:35.347Z</atom:updated>
            <content:encoded><![CDATA[<p>A photograph is a snapshot of a point in time. It tells us where we were, what we looked like, and gives us some insights into how we felt. I love to take photographs, I think they’re tremendously powerful.</p><p>While snapshots of our lives are a wonderful thing for memories, they’re not so good for security. A snapshot — whether you’re doing compliance, vulnerability management, attack surface management, or anything else security-related — is a bad thing. In fact, the usefulness of a snapshot can be measured in seconds, minutes, hours, or even days in some companies.</p><p>On one end of the spectrum are fairly static infrastructure companies that don’t have as much IT change — those snapshots are likely valid for weeks or even months. On the other end of that spectrum are many of the ultra-modern cloud-born start-ups that spin operate on an infrastructure-as-code mentality and change in seconds. On this end of the spectrum snapshots have a useful shelf life of seconds, maybe minutes.</p><h3><strong>So what?</strong></h3><p>So why do I bring this up? Because security, as much as we try and assure ourselves otherwise, is a snapshot-based practice. Your software security, third party risk management, vulnerability management, identity and access management, and compliance programs (to name just the obvious ones) are all based on snapshots. Maybe that’s OK for your organization because you’re static and don’t change rapidly. But maybe you’re the type of organization where a snapshot of the assets on network is valid for hours or minutes.</p><p>But that’s how we’ve operated since inception. Why is this a problem I’m identifying now, you may be asking yourself. Let me tell you.</p><p>I believe that of all the metrics we’re reporting to boards and what-not that try to tell a story of “<em>how good our security program is</em>”, few metrics are as relevant as the distance between your last snapshot and right now. I don’t have a snappy name for it, but this window of time is one of your largest sources of risk, in my opinion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GJdMCDbQTBXDZxXA" /><figcaption>Photo by <a href="https://unsplash.com/@pawel_czerwinski?utm_source=medium&amp;utm_medium=referral">Pawel Czerwinski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Risk, you say?</h3><p>I’ve always been suspect of people who claim that they have no <em>unknown things on their network</em>, mainly because I think think they’re lying. Either to me, themselves, or both. Sometimes the pull to self-delude if powerful when we need hold up some proof of <em>progress</em>.</p><p>What I think is interesting about the snapshot window (terrible name for it, feel free to suggest a better one) is that I currently don’t know of a way to get the window to zero. In fact, I don’t have a reusable methodology for getting the snapshot window to zero across <strong>any</strong> of the top-line security program items. Vulnerability management? Nope. Compliance? We wish. Attack Surface Management? Close, but no.</p><p>I know many of you out there reading this are working with pretty small windows, in a lot of cases. But in some areas, you’re probably pretty miserable. How do I know? Because every time a major vulnerability comes out everyone scrambles to find a scanner, run scans, and find those vulnerable assets rather than dive right into the fix. That’s how. I’ve seen claims of <em>continuous compliance </em>but those platforms depend on process and system input that is not, in fact, real-time. So that’s a no too.</p><p>This is a risk. In fact, I think it’s a risk that we’re not thinking about enough.</p><p>Think about it this way. If your organization runs security scans <strong>continuously </strong>across your environment, how long between the time the scanner hits an asset, and the next time that asset is reached again? That’s your snapshot window. There are many ways you can apply technology to decrease that window length, but eventually you have to ask whether the effort is worth the risk reduction — and there we agree. There is a diminishing point of returns. The problem is, I am fairly confident most of you aren’t anywhere near it.</p><h3>TL;DR:</h3><p>So why should you care? Because I believe that as security programs mature, technology improves at protecting and detecting malicious activity, and we automate more of our security stack — we need to think about this window. We need to start thinking about how to decrease our blind spots, and this is specific metric to me is crucial as collectively security organizations seek to improve themselves.</p><p>Let me know what you think — I’m interested in hearing what this triggers in someone else’s brain!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=281ed22e3867" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Education Under Attack]]></title>
            <link>https://blogwh1t3rabbit.medium.com/education-under-attack-5029ce27e11a?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5029ce27e11a</guid>
            <category><![CDATA[ransomware]]></category>
            <category><![CDATA[education-technology]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Wed, 07 Sep 2022 15:42:53 GMT</pubDate>
            <atom:updated>2022-09-07T15:42:53.420Z</atom:updated>
            <content:encoded><![CDATA[<p>In case you’ve somehow missed the headlines, the education systems in this country are under attack. Stow your politics, I’m talking cyber.</p><p>The latest is the 2nd largest school district in the United States — LA Unified School District was briefly taken offline and down over the Labor Day holiday, but quickly returned to function on Tuesday as kids went back to school. There were claims of a <em>ransomware</em> attack; however, there’s something else afoot here. But as you all know, I generally dislike speculation so I’ll leave you to <a href="https://techcrunch.com/2022/09/06/los-angeles-unified-school-district-ransomware/">read</a> the <a href="https://www.npr.org/2022/09/07/1121422336/a-cyberattack-hits-the-los-angeles-school-district-raising-alarm-across-the-coun">details</a> for yourself.</p><p>In the last 25 years I’ve worked in, with, and for various educational institutions in this great country, from faith-based education, to public primary schools, high schools, and colleges. With few exceptions, such as well-funded higher education institutions, there is something that every single one of these has in common. They’re all <em>dramatically under-funded</em> and <em>under-managed</em> when it comes to technology.</p><p>You’d think that knowing the importance of technology to the current generations of students there would be a lot of money and effort directed at technology, and hence, security. You, like me, would be wrong. Most of the schools I’ve worked with have tiny technology budgets compared to the actual need, and where they do spend money it’s on enriching the student’s ability to learn. Security pretty far down the list. What’s worse, these institutions are patchworks of ancient technology, hand-me-down laptops, donations, and half-broken things.</p><p>I’ve said for a long time that security vendors who want to test their kit in a real-world stress test should deploy to school districts across the country and see how they fare. In these places you’ll encounter a patchwork of operating systems, hardware platforms, software, and special-needs devices that make management damn near impossible — never mind security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*1UqBBkKQsenjiPIemE--1Q.jpeg" /></figure><p>So why are schools a target? Pick a reason, there are so many. Criminals look at schools as soft targets to take down knowing their defenses are weak and they’ll pay up if they are taken down. Your kids’ personal information including addresses, SSN, and other identifying information is worth more on the open market because they don’t have mired credit histories yet and probably won’t look at their credit reports for a while. The reasons are many.</p><p>I log into my kids’ school’s online platform that connects me to their teachers, their school work, and other information nearly every day. Each time I do I marvel that the platform feels like it was written in the days of Office 95 and designed for Netscape Navigator 7. If you know these, you are picturing the web app in your head right now, aren’t you? How easy would it be to break in? Let’s just say it’s not something you have to be a nation-state threat actor to achieve.</p><p>I don’t envy the position of administrators in the education system. They’re caught with poorly run budgets, Unions and misguided school boards that control far too much and know far too little, and students that want to poke around. There is also a dramatic difference between private schools with big-budget spending on technology and security, and those not-so-privileged school districts where hand-me-down tech is a luxury.</p><p>At times it’s easy to get angry at the situation, and curse the criminals. The problem is we — those of us who are tax payers and parents — have a hand in this too. We need to put focus on the security of the technology that our children use in schools, keep a watchful eye on privacy, and do everything we can to make sure our children aren’t the target of online predation. Better funding isn’t enough.</p><p>So if you’re reading this, I challenge you to do what I’m doing. Go to your local school, or school district, and offer to help. You’re likely far more experienced and intelligent on cyber security matters than the administration — so help out. Offer advice, consult, work with tech companies to provide partnership and support. Tomorrow’s hope is today’s mission. Go.</p><p>By the way, if you’re on the administration side of the conversation — leave me a message directly or contact the <a href="https://www.securityadvisoralliance.org/">Security Advisor Alliance</a>. We’re an organization that can help, with experts, expertise, and a desire to train and bring our knowledge to your schools. Our mission and focus is on workforce development, but we can do so much more. It costs you literally nothing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5029ce27e11a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation Isn’t the Savior You Think It Is]]></title>
            <link>https://blogwh1t3rabbit.medium.com/automation-isnt-the-savior-you-think-it-is-88c979044245?source=rss-153a543f560d------2</link>
            <guid isPermaLink="false">https://medium.com/p/88c979044245</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[soar]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Rafal Los]]></dc:creator>
            <pubDate>Fri, 04 Feb 2022 20:58:59 GMT</pubDate>
            <atom:updated>2022-02-04T20:58:59.764Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone’s talking about automation as cyber security’s salvation. I wish I could agree with the same level of enthusiasm as some of my colleagues and friends. The fact is, no matter how much lipstick you throw on that pig, it still tastes like bacon.</p><p>It appears to me that what the technology industry is lacking in process, it attempts to make up for with automation. This approach plainly does not work.</p><p>Cybersecurity appears to be learning no lessons from our colleagues in IT, and in fact, seems to be doubling down on automation for salvation. Where we lack process and expertise — we buy technology. I recognize an apparent lack of truth and transparency in the cyber security product market. Some of us have been fighting this for years with little success to show for it. For an interesting take check out this <a href="https://twitter.com/mmurray/status/1488874956263993345">Twitter thread</a> by Mike Murray. I, perhaps unlike you, am deeply frustrated by the lack of actual progress in our industry.</p><p>How did we get here?</p><p>Early in my career, nothing was <em>automated</em> like you see today. We updated anti-virus definitions by hand before Symantec introduced corporate IT to the concept of managed anti-virus. I’m not saying they were the first, only that Symantec was my first true enterprise-grade tool. Automation was very poor, and it often failed, but at least the work was not manual anymore.</p><p>In the last twenty years, security professionals have done a catastrophically poor job at creating repeatable, sustainable, process-driven activities. It started in the SOC — where analysts would just “do security stuff” sifting through raw log files, looking at a half-dozen different dashboards, and of course checking the SIEM. Because these teams were used to living in chaos, they just accepted that things were done however you can do them. Worse, documenting processes and ways of doing things became somehow undesirable. If you don’t believe me ask a SOC analyst what their processes are like. Very few organizations are mature enough to have repeatable, documented, and optimized processes for analyzing the mountains of data and alerts to make security decisions. Very. Few.</p><p>The problem spills far beyond the boundaries of the Security Operations Center (SOC). Unfortunately, in my career, I’ve experienced a lack of processes everywhere from the software development lifecycle, change management, security management, incident handling, and various other critical areas of IT.</p><p>The result is a predictable level of chaos and inefficiency.</p><p>So what have companies done to account for this obvious lack of process? Technology purchases of course! Seems logical, right?</p><p>The big problem I believe that security leaders somehow either overlook or ignore, is that technology and automation only mechanize existing processes. If you have nothing to automate … well, I’ll leave you to finish that sentence in your own head. Where does that leave the state of the industry? With three very big problems:</p><ol><li><strong>Reliance on vendor “out of the box” technology</strong> — because when you have nothing, you take what you can get. I shouldn’t have to explain why this is problematic. Your vendors don’t know your organization, your staff, your particular quirks, or organizational challenges. Simply relying on out-of-the-box solutions for security automation creates a wildly inefficient, poorly implemented, and immature organization. Even if you pay a ton of money to a consultant to “customize” the technology to your environment, remember that you’re now beholden to that person to repeat that task regularly because your business is not static and changes regularly.</li><li><strong>Predictable in an undesirable way</strong> — because attackers know how out-of-the-box security tools work; they buy them too! Without adaptation and customization, your security organization is predictable and thereby rather easily manipulable and able to be bypassed. Evidence of this is all over the news, literally every single day.</li><li><strong>Immature</strong> — because chaos with a lot of technology is still chaos. It’s just very expensive chaos with pretty dashboards. Maturity is critical to security and having well-designed processes is fundamental to maturity.</li></ol><p>So, look, while I applaud that companies are taking the initiative to implement XDR-based technologies and SOAR — that tree is unlikely to yield any fruit. If I may offer up a suggestion — before you write that next budgetary check investigate the process maturity of your security organization. Ask yourself a few fundamental questions:</p><ol><li>Are we interested in automation to scale and mechanize our existing mature processes, or are we looking for the tools to build processes for us?</li><li>Do the tools we’re thinking of implementing <em>support our processes</em> or are we going to change how we operate to accommodate the tools?</li><li>Does the automation technology we’re interested in purchasing adapt quickly and easily as our processes change?</li></ol><p>It’s not too late to break out of this death spiral we seem to be in, but the point of no return is close. Technology will continue to evolve and the point where manual data analysis was practical is a distant and forgotten time. Without well-thought-out processes in the security organization, no magical tool will save you. Not even that next-next-Gen AI-powered cloud-based SOAR widget all the analysts are raving about right now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88c979044245" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>