To improve the security posture of our organizations, we must open our eyes to rationalization and put an end to it with logic. Here's how.

Joshua Goldfarb, Global Solutions Architect — Security

August 6, 2019

4 Min Read

As humans, we have a tendency to justify and rationalize our actions. We all do so, whether we see what we're doing and whether or not we do so willingly. The novelist Paul S. Kemp is quoted as saying that "the human mind has infinite capacity to rationalize." Former tobacco lobbyist Victor Crawford, who died of lung cancer at 63, justified his personal and professional choices in a 1994 article in The New York Times Magazine entitled "How Do Tobacco Executives Live With Themselves?" this way:

In a way, I think I got my just desserts, because, in my heart, I knew better. But I rationalized and denied, because the money was so good and because I could always rationalize it. That's how you make a living, by rationalizing that black is not black, it's white, it's green, it's yellow.

What does rationalization have to do with security? First, we are security professionals, but we are, of course, also human. As humans, we rationalize just like anyone else would, which can have a negative influence on our decision-making, weaken our security posture, and introduce additional risk to the business. One way to improve our security postures is to stop rationalizing and to start using logic instead.

Let's consider four preventable signs of rationalization in a security organization:

Sign 1: "We have to do something." When a high-profile incident occurs or there is a newsworthy buzz about the world of security, it often comes with a lot of questions from executives, customers, and other stakeholders. While it's clear that something needs to be done, it's not always clear what that something is. If a security organization evaluates the issue at hand, the risk it brings to the organization, and how that risk can be remediated, the team can arrive at a logical conclusion as to what actions are necessary. If, however, the security organization finds itself saying "well, we have to do something," that's usually an indication that rationalization is occurring. It's often a sign that a knee-jerk response is being put in place rather than the right response.

Sign 2: "We can't do that." It may very well be the case that whatever is being proposed can't actually be done. But before accepting that conclusion, you need to ask: "Why not?" If there isn't a clear, concise, logical answer to that simple question, take it as a sign of rationalization.

Perhaps completing a particular task will be difficult, will require significant effort, or will ruffle some feathers in the organization. Regardless, if a security organization isn't honest with itself about what it can and cannot do, it may discount or dismiss ideas that could go a long way toward helping it improve.

Sign 3: "Our security program is quite mature." When I hear a statement like this, I want to see metrics that prove it. If there aren't any readily available, that's the first sign that rationalization is at play. This may sound a bit harsh, but half of security programs are of average or below-average maturity! That's the way a mean works — it's right in the middle. It may very well be the case that a given security organization is ahead of its peers and excelling. Those security teams generally have extremely well-defined processes and procedures, along with metrics to continuously monitor and improve progress and performance. In other words, if a security program is mature, there should be numbers to prove it. If there aren't, logic isn't likely in the mix.

Sign 4: "That's not how we do things here." There are policies, rules, guidelines, practices, and procedures that make sense and are in place for good reason. However, not all of them make sense all of the time. If something isn't producing the required or expected results, it's time to change the way that something is done. I don't mean simply changing for change's sake. I mean real change that improves outcomes and results based on logic and reason. That requires putting the rationalization aside.

Rationalization is lazy — the easy way out. Logic requires more effort. But the extra investment of identifying and eradicating rationalization allows a security organization to open doors that lead the way toward improvement. An improved security posture begins by opening our eyes to rationalization and putting an end to it with logic.

Related Content:


Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

About the Author(s)

Joshua Goldfarb

Global Solutions Architect — Security, F5

Josh Goldfarb is currently Global Solutions Architect — Security at F5. Previously, Josh served as VP and CTO of Emerging Technologies at FireEye and as Chief Security Officer for nPulse Technologies until its acquisition by FireEye. Prior to joining nPulse, Josh worked as an independent consultant, applying his analytical methodology to help enterprises build and enhance their network traffic analysis, security operations, and incident response capabilities to improve their information security postures. Earlier in his career, Josh served as the Chief of Analysis for the United States Computer Emergency Readiness Team, where he built from the ground up and subsequently ran the network, endpoint, and malware analysis/forensics capabilities for US-CERT. In addition to Josh's blogging and public speaking appearances, he is also a regular contributor to Dark Reading and SecurityWeek.

Keep up with the latest cybersecurity threats, newly discovered vulnerabilities, data breach information, and emerging trends. Delivered daily or weekly right to your email inbox.

You May Also Like

More Insights