I recently published Artificial Intelligence and the Role of the Analyst on Gray Space, where I discuss how the growing role of artificial intelligence should shift cyber analysts toward supervising systems, evaluating evidence, and exercising judgment, rather than manually writing queries, debugging logic, and reviewing logs.
My article Demystifying the Analytic Scheme of Maneuver was just published on Gray Space, where I discuss how an analytic scheme of maneuver connects a commander’s questions to evidence, data, and investigative actions.
I recently published Schrodinger’s Breach on Gray Space, where I discuss why cyber investigations should assume compromise and rigorously test that assumption.
I’m pleased to share that my article, The Military Needs Frontier Models, was just published on Military Review, where I discuss why complex military applications need the reasoning and contextual capabilities of frontier AI models.
Ethan Mollick wxplains a recent Harvard Business School study examined the impact of large language models as collaborative “teammates” within Procter & Gamble. The findings revealed that employees augmented with AI not only outperformed those without AI assistance but also experienced notable productivity gains. Significantly, the integration of AI enabled specialists to transcend their narrow expertise, fostering more comprehensive and well-rounded solutions. This suggests that AI can effectively dismantle knowledge silos, enhancing collaborative problem-solving — a crucial insight for technical work in particular, such as in the cybersecurity field.
In Keeping Up with Current Events, I talked about the websites I turn to each morning to stay informed; in My Evening Reads, I shared the many others I follow on niche subjects. Podcasts, however, are another important part of how I learn and grow. Some offer regular updates on current events, while others dive deep into niche topics. As a complement to Keeping Up with Current Events and My Evening Reads, I wanted to start a list of the podcasts I follow here.
I’m pleased to share that my article, A Cyber Force is Not the Only Solution, was just published on War on the Rocks, where I discuss how specialization, job-specific training, and improved career incentives could strengthen the Army’s cyber workforce. Ultimately, although a new Cyber Force is not the only way to implement these changes, it is unfortunately the most likely path given the services’ demonstrated unwillingness to make these changes on their own.
I recently published Everyone Can Contribute to Professional Discourse on The Harding Project, where I discuss how reading, writing, editing, and finding the right outlet can help anyone contribute to professional discourse.
Let me save you some time: the Framework laptop is great, and you should buy it. The rest of this post will delve1 into the why, but that’s the “so what.”
I last wrote about my setup in May of 2019, almost five years ago. While some of those specifics have stayed the same, much has changed since then, and so I decided to write a new version of that article today. For ease of comparison over time, this post will—-for the most part — follow the same format as in 2019.
In a class a few days ago, the instructor trotted out Donald Knuth’s famous quote about premature optimization. Of course, as nearly every other instructor has ever done, he cherry-picked the catchy middle part: “Premature optimization is the root of all evil.” He did not, however, share the context around it. Here’s the full quote:
Thanks in no small part to OpenAI’s ChatGPT, the past year has seen an explosion in interest in artificial intelligence in general, and in large language models in particular. That democratization of access turned this niche research area into a common topic of conversation, and has led to a lot of fascinating writing on the subject. Although certainly not comprehensive, this article collects some of my favorite articles, papers, and resources into a single reading list.
A few weeks ago, I participated in a working group tasked with identifying areas where artificial intelligence and machine learning could improve network utilization. What, specifically, “improve” and “utilization” meant were some of the first questions we addressed. During that conversation, though, one of the participants made an insightful observation that the group promptly ignored. He told a brief story about how someone had asked him for a networking device that could aggregate multiple uplinks and then “use AI to choose the best one.” When he offered a simple WAN failover solution, a technology that has existed for decades and comes built-in to open source firewalls like pfSense, commercial appliances from the likes of Cisco, and every modern mobile phone, the customer told him, “No.” Like our working group, that customer person had a solution (artificial intelligence) driving their requirements (an AI-based WAN failover), not the other way around.
Over a year ago I read Matthew Strom’s article How to pick the least wrong colors, where he explored the fascinating intricacies of designing good color schemes. Here, “good” meant not just whether the colors looked nice, but also how distinguishable they were from each other and whether or not they accomodated individuals with conditions like protanopia, for example, who cannot see red light. He came up with a great solution and posted the NodeJS code to GitHub. Since I do most of my work in Python, though, I had few chances to take advantage of his research — until now. My latest project, Colors, helps to generate large sets of attractive and accessible color schemes. The current version of this project is, for the most part, a direct NodeJS-to-Python port of Matthew’s code from 2022 with a few minor changes, but I look forward to building on it and keeping pace with Matthew. Colors is currently available as a Jupyter notebook and a regular Python script.
I keep fielding this question in private, so I finally decided to answer it in public: “What SANS courses should I take?” Although I have a much longer answer to give about training in general, this article answers that specific question based on my own personal experience, having taken several SANS courses over the years.
I have, for years now, wanted a cool shell prompt — something worth showing off on r/linux or even r/unixporn. Not enough to dig into the weeds and figure out how to write one myself, but enough that it came up every once in a while. Then, the other day, I had a great idea: why not just let ChatGPT make it for me?
Both civilian cybersecurity practitioners and military defensive cyber operations personnel continue to push a similar idea, that to identify malicious activity one must “just get a baseline and then flag anything different.” If only! I call this the Baseline Fallacy:
Military leaders have sought hard data to drive their decisions for decades, perhaps most famously beginning with Secretary of Defense Robert McNamara’s so-called Whiz Kids’’ in the 1960s. As retrospective analysis of those decisions made clear, however, data alone does not good decisions make. Errors in collection, transmission, and presentation decimated the efficacy of this initiative.1 The Vietnam War is a cautionary tale in data-driven decision-making gone wrong, an important reminder that modernity’s insatiable need for more data is no more a silver bullet today than it was sixty years ago.
A few days ago, I mentioned that I use Git to synchronize work between several different devices and across several different platforms. This setup has served me well, and so today I want to talk about it in detail.
I have used git to synchronize work between several different devices and across several different platforms for quite some time now. Over the years, though, inconsistencies have crept in. The name attached to my commit messages, for example, might be “Zac” on one device, “Zachary Szewczyk” on another, and “Zac Szewczyk” when committing via GitLab’s web editor. The same applied to the email address attached to those messages. Elijah Newren’s git-filter-repo project made it a breeze to fix this.
My book Handbook for Defensive Cyberspace Operations contains an extensive chapter on tools and resources for cybersecurity analysts. As a closed project, however, this knowledge has had little impact outside of my niche community. This post contains a version of that chapter suitable for distribution to the public.
Like college degrees before them, professional certifications seem to be waning in popularity in the cybersecurity industry. Perhaps as a way to mitigate the well-documented workforce shortage, some companies have gradually begun to account for competence and experience, too, rather than onerous credentials alone — and in some cases, base their hiring decisions solely on those criteria. This is a localized phenomenon, though, exclusively limited to the private sector, and even there primarily limited to smaller firms. In the public sector, at many large firms, and particularly at large firms that work with the government, formal credentials such as a degree and professional certifications remain not only an important factor, but in many cases the only factor. This led me to take (ISC)<sup>2</sup>’s Certified Information Systems Security Professional (CISSP) exam earlier this summer. Even as a Cyber Operations Officer, credentials like this one carry great weight. I passed on my first attempt, so in this article I want to share my preparation strategy.
The other day, a member of SANS’s GIAC Advisory Board asked a question about Mean Time to Detection, or MTTD. In the ensuing discussion, another member cautioned against confusing key performance indicators used to assess individual efficiency, to then serve as the basis for penalties and rewards, with measures of program efficiency. Holding individuals accountable for MTTD, for example, made little sense when that detection relied on factors outside of their control such as effective data collection and efficient aggregation into a centralized platform, each of which were likely to be managed by a separate department. I alluded to the challenge of implementing metrics in part one, but did not deal with this issue specifically. This bonus article provides specific recommendations for applying SOC metrics to individuals versus an entire program.
It’s human nature to assume there’s a good reason for why things are the way they are. And that this reason is either benign, based on careful deliberation, or malignant, derived from malice or incompetence. But this is a false dichotomy that often steers us away from the simpler answer: Nobody thought about this at all.
Given an absence of information, many tend to fill those gaps with generous assumptions. At the beginning of Russia’s botched invasion of Ukraine, national security pundits considered it some sort of 4D chess game; time proved otherwise. No one knows what they’re doing, “It’s OK though — that’s not where your problems are coming from. Rather, your problems are coming from the fact that you think other people know what they’re doing.”
I’m pleased to share that my article, Command vs Leadership, was just published on The Center for Junior Officers, where I discuss why conflating command with leadership can discourage technically skilled cyber officers.
I went to a presentation from a large cybersecurity firm the other day. The salesmen — and they were all salesmen, as even a few post-presentation questions made clear — focused on the intelligence their company produced, but knew little about the rest of their company’s intelligence cycle. As a consumer of their products, though, I consider knowledge of the process that created them critical. After an hour on finished intelligence, and in particular a slide that touted a “globally deployed sensor grid”, I wanted to know more about that production process in general, and about their collection specifically. Unfortunately, when asked, the salesmen offered a handful of handwavy “We have millions of sensors across the globe”, and, “We ingest billions of events per day” statements, but little beyond that.