Console Wars
A Bit of Security for June 24, 2024
Every security product tells you something about the world it perceives. That information is presented in reports, messages, and on a console. Part of the cost associate with deploying any security tool (or any systems management tool) is learning how to read the console.
The console becomes the focus for the organization’s security program. Enterprises that are looking for a console should speak with peers about how well the tool performs in their environment, and how receptive the vendor is to enhancements. This point is too often undervalued.
In the 1980s, IBM had a set of systems engineering tools for network analysis: NCCF, OCCF, NPDA, and three others. They were quite helpful independently, but someone figured out how to bring them together behind a consolidated console and the suite was sold as NetView – and it was a huge hit! IBM had always realized that computing is a major investment by the enterprise, so they built strong relationships with their customers. There were multiple forums for customers to suggest enhancements, provide feedback, and engage with executives to understand the longer view for the product set.
I called on one major Canadian bank and the IT director proudly showed me his NetView console. He had never seen how the network was performing in near-real-time before, and it changed his life. As customers adopted NetView, they found new uses for products they already had, and recognized gaps in their ability to manage the increasingly complex network environment they were growing into. The company had always said that the sales team was paid a commission for their selling; and was paid a salary for the marketing intelligence they collected. Marketing is understood to be two-way: not just prepping for the next deal, but also gathering insight into future product requirements, competitive offerings, and enterprise strat3egy and architecture evolution.
Today’s console vendors compete not just on the snazzy graphics but on the functionality and flexibility of the console. When you look to extend or enhance your security team’s capabilities, see how the console you have meets your current and future requirements. If you don’t know what your future requirements will be, a trusted advisor can help – be that a research and advisory firm, a dependable vendor who sticks with you after the current transaction, or your organization’s Chief Technology Officer.
I’ve spoken about the CTO’s role in another broadcast. Someone in your organization should understand the organization’s goals and direction well enough to build a model mapping your strategic requirements against your potential vendor’s offerings and direction. And never underestimate the value of a durable two-way relationship with your security vendors.
A Bit of Security for June 24, 2024
Your cybersecurity console is the hub of your incident response capability, and the anchor for your information security program. How well does your vendor listen to your requirements? Listen to this -
Let me know what you think in the comments below or at wjmalik@noc.social
#cybersecuritytips #console #platform #securityplatform #BitofSec