Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

7/24/2018
03:30 PM
Joshua Goldfarb
Joshua Goldfarb
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

How 'Projection' Slows Down the Path to Security Maturity

A little bit of self-awareness goes a long way when it comes to evaluating a company's security maturity level. It's also a prerequisite to improving.

Recently, I observed a somewhat intense conversation between two acquaintances about a parenting issue. In this conversation, one person was critical of the other's childrearing approach. I happen to know both individuals, who are both good people. But like any human being, neither of them is perfect. Putting aside the fact that it generally seems best not to judge or comment on another person's behavior, particularly when it comes to parenting, this exchange highlighted an important concept for me: projection.

Wikipedia defines psychological projection as "a theory in psychology in which humans defend themselves against their own unconscious impulses or qualities (both positive and negative) by denying their existence in themselves while attributing them to others." I am not a psychologist and don't know all of the background information and details around this particular exchange. But after reading more about the topic of projection, it seemed to be a possible explanation for what I witnessed.

OK. But what does psychological projection teach us about security? I would argue quite a bit, in the sense that security organizations are often most critical toward other organizations regarding the very weaknesses that they themselves exhibit. This is important because only when organizations are aware of their own behavior and attitudes can they hope to improve. In this spirit, I offer five ways in which projection slows down the path to security maturity.

1. "They don't know what they're doing." I've lost count of the number of times I've heard phrases to the effect of "so and so has no idea what he's doing," "that place is clueless when it comes to security," and "if only they knew what they were doing like we do." Of course, it is entirely possible that your organization is leaps and bounds beyond your peer organizations. But, it is also quite possible that your peer organizations are more or less just as on top of security as you are. What if instead of taking the easy out of looking down upon other organizations, your organization turned its gaze inward?

2. "Their leadership has no vision or direction." Unfortunately, there are a fair number of people in security leadership positions who are not really leaders. Not surprisingly, you won't find a tremendous amount of vision or direction coming from these people. Of course, I haven't found that to be the case in the majority of instances. In my experience, there is almost always something (or several things) that we can learn from others in leadership positions. It's easy to be dismissive of those individuals. But there is much more to be gained by looking honestly at our own leadership abilities, our own strengths and weaknesses, our own vision and direction.

3. "Their team isn't adequately staffed or trained." No organization is able to provide the level of staffing and training that it would like to in an ideal world. As with so many things in business, the issue becomes a game of prioritization and resource management. There are certainly a good number of organizations that, for whatever reason, do not staff and train in a way that will allow them to mitigate risk appropriately. But many organizations make good use of whatever resources they have available. Whether your organization is resource strapped, could staff and train better, or both, a lot can be learned by stopping the finger-pointing and looking internally to see where changes can be made.

4. "Their security technology stack is problematic." I have yet to meet a security organization that doesn't hold strong opinions about the security technology stack it has chosen (or was handed) to deploy and operate. The truth of the matter is that the security technology stack should support and serve the organization's risk mitigation strategy. As long as that is the case, there are many different choices around security technology that the organization can make to meet its goals. I've sometimes heard organizations poke fun at and/or mock the security technology in place elsewhere. This doesn't help anyone advance the state of their security program. A far better use of this energy is to look inwardly in an attempt to understand if the security technology your organization uses is helping you meet your risk mitigation goals, both strategically and tactically.

5. "They aren't as mature as we are." It's far too easy to consider our own security organizations to be very mature. It's even easier to look at other organizations in our sector, geographic area, or of a similar size and see them as less mature than we are. To be perfectly honest, nearly all the security organizations I meet with consider their security maturity level to be above average. For some of those organizations, that is definitely a realistic view of the situation. Unfortunately, the laws of statistics don't allow for nearly all security organizations to be of above average maturity. A little bit of self-awareness goes a long way when it comes to evaluating one's own security maturity level in earnest. It's a prerequisite to improving.

Related Content:

Learn from the industry's most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Register before July 27 and save $700! Click for more info

Josh (Twitter: @ananalytical) is an experienced information security leader who works with enterprises to mature and improve their enterprise security programs.  Previously, Josh served as VP, CTO - Emerging Technologies at FireEye and as Chief Security Officer for ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.