CISO's View: Why an Integrated Approach Matters
Today the author focuses on why culture is critical and an integrated approach to cybersecurity solutions is the key to success for the security program.
Join the DZone community and get the full member experience.Join For Free
if you’ve been reading along, you’re aware of the lightbulb moments from my article, “echo: hello world” , that allowed me to discover the benefits of an analytic approach to cybersecurity. this is the start of my new blog series, the ciso’s view, where i focus on the executive level business concerns facing security leaders. today, i’d like to focus on why culture is critical and an integrated approach to cybersecurity solutions is the key to success for the security program.
cybersecurity isn't just a list of products…
i use several innocent questions in conversations to gauge the maturity of a company’s security program, the first i lead with is “what’s your security program look like?” unfortunately, i’ve had many instances where i’m given a list of security point solutions as their answer. digging deeper, it appears that the entire program lifecycle consists of: identify gap -> purchase product. these same folk will then go on to explain – at length – how the business doesn’t get security, won’t invest in the products they need, and considers security to be a nuisance.
digging even deeper, the security organization is structured around the security products: the anti-virus group, the forensics group, the data loss prevention group, etc. each of these people/teams are responsible for the full stack support of each of these products; patching, maintenance, configuration, and, occasionally , use.
this thought process leads to the last question i ask to understand that maturity of the company: “what title does the head of security hold and where in the organization do they reside?” just understanding where this role sits within the company shows me the how security is perceived by the company.
the security maturity path
as you can see, those simple questions can tell you a lot about the maturity of a security program as the answers range from the reactive technical response to the mature security as a strategic business value proposition focus. the maturity path roughly follows the following growth pattern:
- the head of security considered a middle or technical manager of a team reporting indirectly up to the cio. security is considered a technical add-on or a specialized it team to be treated in the same fashion as desktop support.
- the head of security holds some chief title such as ciso/cso and directly reports to the cio/cfo/coo and is responsible for presenting security metrics to the board on some infrequent basis such as annually. the organization has realized that security concerns cut horizontally across all of it and needs governance as such; however, it is still considered a cost of doing business alongs the lines of facility maintenance – somewhat important but not core strategic value.
- the head of security with a title such as cro (chief risk officer) is considered a full member of the ceo staff to ensure the desired risk posture is embedded into the corporate strategy for competitive advantage. the organization realizes the cost savings of incorporating security and risk management principles into all phases of the business from design to operations and security initiatives are prioritized on the basis of minimizing uncertainty.
- the head of security has a matrix reporting structure to the ceo and board since there is awareness that the risk posture of the company directly impacts shareholder value. the organization realizes “security” is actually a set of sound risk management practices that help drive best of industry practices that make the business more agile and capable of capitalizing on market opportunities. traditional “security” roles are embedded through the organization where the accountability should have always been; with those who make the decisions.
cybersecurity is a cultural issue
we are living in interesting times where companies are transitioning from operating as legacy brick and mortar to technology focused for disruptive advantage.
“may you live in interesting times” – a curse.
the fact is, the modern company is a technology focused one that happens to make, service, or sell stuff. we can see this new reality by comparing companies that get this to those who don’t.
- the neighborhood bookseller to amazon
- blockbuster to netflix
- paypal & fintech to community banking
- uber and autonomous vehicles to taxi services
those who understand the new reality become a disruptive force in their industry, and those who don’t become – disrupted. the modern company’s core is a technology platform that integrates with their partners and customers, and the company’s operating tempo is the development and release cycle of that platform with the disruptors aiming for continuous delivery.
great, what does this have to do with security?
in my view, legacy company thinking is the result of consolidating not only the responsibility but the technical skill for leveraging technology into a single department or division within the company, treating technology as some operational cost center somehow divorced from the core company strategy, and believing their strategic decision makers don’t need strong technical competency. after all the business makes widgets, moves boxes, provides services – it’s not a technology company.
technology focused companies become disruptive industry forces.
those that don’t become disrupted.
it is this legacy thinking – this cultural issue that is the core challenge a ciso faces in being successful. when technology is considered some operational cost center and security is a minor issue within that cost center, then, of course, it isn’t given the consideration and funding required to be truly successful.
leveraging cybersecurity as a competitive advantage
i view the first and most fundamental challenge a ciso must face when building their security program is addressing the cultural thinking head on. the ciso must win the hearts and minds of the ceo and board by changing the perception as some peripheral afterthought to a core part of the company’s strategy. “show, don’t tell,” isn’t just a tip for writers seeking to engage their readers. the ciso must show with every communication how security can be a competitive advantage and the value it brings to the business.
security: is “the” business enabler
to do this means taking all the activity in the security program and making it both visible and tied directly to the company’s top and bottom line. it is the ciso’s first and most important job to show – on a daily basis – that security is a critical part of the company strategy. yes, i’m saying the ciso’s first job is metrics. these metrics influence and enable the rest of the program and this topic will be the focus of a later article. today, i want to keep to why integration matters and we have now arrived at the core concept that drives a program focused on a single integrated security platform instead of a list of security products.
data, transformed into metrics, drives understanding of the company’s true risk posture, and that in turn drives both the security program and company strategy. these concerns are all interconnected and so our data needs to be as well. this drives a shift into what we look for out of the list of security products above, from a list of bells and whistles to a core requirement that the data they create is open and available for integration into a larger enterprise platform.
integrated approach for point security solution:
- be a succinct source of data or control point and not a monolithic closed black box.
- provide data using open non-proprietary data formats ready for machine parsing.
- establish data provenance, chain of custody, non-repudiation of all data for forensic evidence through the data lifecycle.
- be designed to sit within a larger enterprise platform architecture versus built as a closed application or security appliance.
to be succinct: the ciso’s first and most fundamental job is taking all this security data, threats, vulnerabilities, policy violations, and transforming it into business language that shows the impact to the company’s top and bottom line. once this is done well, the authority and resources to be successful are justified within the executive’s and board’s minds and doesn’t have to be fought for using fear uncertainty and doubt.
Published at DZone with permission of Michael Schiebel, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Send Email Using Spring Boot (SMTP Integration)
RAML vs. OAS: Which Is the Best API Specification for Your Project?
Microservices With Apache Camel and Quarkus