Back to blog

What the telephone teaches about cybersecurity

What the Telephone Can Teach Us About Cybersecurity

NetSenX Team9 min read
governancemid-marketndr

Can we recognise a technology that will change the rules of the game before it becomes obvious? Can we admit that solutions which worked well enough for years may stop being sufficient in a new world? Or do we, as entrepreneurs and decision-makers, often defend the old order not because it is the best, but because it is familiar?

These are questions worth asking especially today, when we talk about cybersecurity.

When Alexander Graham Bell was working on the telephone, the world of communication was organised around the telegraph. It was a serious, proven, business-oriented and understandable system. A message could be sent, written down, forwarded and delivered. There were procedures, people, infrastructure and habits. At the beginning, the telephone did not look like an obvious revolution. To many, it may have looked like a technical curiosity, an experiment, a device that was too strange, too imperfect or simply unnecessary.

A popular anecdote says that some decision-makers at the time looked at the telephone through the logic of the telegraph: why would anyone need a conversation through a wire if a telegram could be sent and delivered through a proven system? Historians point out that some quotes attributed to Western Union are difficult to verify conclusively and may have been simplified by later business storytelling. But the lesson itself remains relevant: new technologies often lose at the beginning not because they are weak, but because they are judged by the standards of the old world.

And this is exactly where the problem begins in cybersecurity today.

Many companies still think about digital protection in the same way that old telegraph operators might have thought about communication. We have a firewall. We have antivirus. We have backups. We have an IT provider. We have procedures. Somehow it works. Why would we need an additional monitoring layer? Why would we analyse network behaviour? Why would we need a system that shows anomalies if the company is operating, people are working, production is running, invoices are being issued and customers are not reporting problems?

It sounds reasonable. Until it stops being reasonable.

Because a modern company no longer resembles a simple office with a few computers. It is a living, connected organism. It runs on cloud systems, integrations, remote access, technical accounts, ERP, CRM, MES, SaaS applications, APIs, automation, AI tools, industrial devices, machines, sensors, admin panels and suppliers who often have deeper access than the board actually sees.

In such an environment, a firewall is important, but it is not the answer to everything. Just as a horse-drawn carriage may still have been useful in the era when the telephone was emerging, but it was no longer the answer to the future of communication. The problem is not that old tools are useless. The problem is that new risks require new layers of visibility.

Today, attackers no longer behave only like someone trying to force the door open. Increasingly, they behave like someone who first wants to enter quietly, look around, understand the layout of the rooms, check where the documents are, who has the keys and what time the company goes to sleep. In the cyber world, this means network reconnaissance, unusual logins, command-and-control communication, lateral movement, slow data exfiltration, abuse of privileges, use of old accounts or supplier activity that looks normal only because nobody is watching it closely enough.

Would your company be able to notice it?

This is not a technical question. It is a management question.

Because if a company cannot see what is happening in its network, it is not managing risk. It is only assuming that risk is under control.

In the 21st century, such an assumption is becoming increasingly dangerous. Artificial intelligence lowers the barrier for automation on both sides. Companies use AI to speed up work, analyse data, communicate and automate processes. But attackers also use automation, scripts, tools that support reconnaissance, phishing content generation, vulnerability analysis and faster operations. Add to this robotics, Industry 4.0, IT/OT environments, cloud systems and an increasingly tense geopolitical situation.

This is no longer a world in which it is enough to say “we have security tools.”

The question is: do we know what is happening between those security tools?

This is where many risks are created today. Not on a slide with a security policy. Not in a supplier’s declaration. Not in a procedure table. But in real network traffic. In who communicates with whom. How often. At what times. From which locations. To which systems. What data leaves the company. Which device suddenly changes its behaviour. Which account starts doing something it did not do before. Which application communicates with an address that was not part of the normal working pattern before.

This is the new language of risk management.

And this language is based on visibility.

This is not about paranoia. It is not about blocking business. It is not about stopping every innovation with a procedure. Quite the opposite. Well-designed security should allow a company to grow faster, but without operating blindly.

It is a bit like a car. We do not buy comprehensive insurance because we plan to have an accident. We buy it because we understand that risk exists regardless of our intentions. We do not install sensors, cameras and driver assistance systems because we cannot drive. We install them because the environment is complex, dynamic and not always predictable.

Cybersecurity works in a similar way.

Network monitoring is not a sign of distrust towards employees. It is a form of prevention. It is an independent verification layer that helps answer a simple question: does what is happening inside the company still look normal?

And the word “normal” is crucial here.

Because many attacks do not look like attacks at the beginning. They look like a normal working day. Like a user logging in. Like a system sending data. Like a supplier using remote access. Like an application communicating with an external server. Like a device appearing in the network because someone “had to launch something quickly”. Like an AI tool used by an employee because they wanted to prepare a document, offer or analysis faster.

Individually, such events may look harmless. In context, they may be the first signal of a problem.

That is why modern cybersecurity cannot be based only on the question: do we know this signature? An increasingly important question is, does this behavior fit our environment?

This is where the value of NDR systems (Network Detection & Response) appears. Not as a fashionable acronym. Not as another dashboard for the IT department. But as a layer of visibility and response that looks at network behaviour, not only at known threat patterns.

Because if an attacker uses new methods, new tools, automation and vulnerabilities that classic systems do not yet recognise, the company needs the ability to detect deviations. It needs to see that something is behaving differently before it becomes an obvious incident.

The history of the telephone is a good mirror here.

It is easy today to laugh at people who did not see the potential of a new form of communication. But are we not sometimes doing something similar? Do we not say, “our current system is enough”? Do we not assume that if nothing has happened so far, the risk is low? Do we not treat network monitoring as something additional until the first serious incident happens?

Or maybe the biggest mistake is that we look at the future through the tools of the past?

In Bell’s time, the problem was that people tried to understand the telephone through the logic of the telegram. Today, many companies try to understand cybersecurity through the logic of the firewall. A firewall is needed. Just as the telegram was needed. But the world has moved on.

A company that wants to be resilient must see more than the edge of the network. It must see the behaviour of the environment. It must understand communication between systems. It must know when a supplier, application, account, device or employee begins to deviate from the normal pattern. It must have not only protection, but also evidence. Not only an alarm, but context. Not only a technical signal, but information that can be translated into a business decision.

This is particularly important in Europe, where regulations such as NIS2, GDPR and DORA are moving cybersecurity from the area of “technical best practice” into the area of organisational responsibility, reporting, documentation and operational resilience. After an incident, a company will not only be asked whether it had tools. It will be asked when it noticed the problem, what it did, what evidence it had, what the impact was and whether it was able to act responsibly.

And to document something, you first have to see it.

This sentence is simple, but very uncomfortable.

Because it forces companies to ask a question they often avoid, how many things are happening in our network that we do not really know about?

NetSenX was created around this exact need. Not as a replacement for existing security tools, but as an additional layer of visibility, monitoring and anomaly detection in network traffic. As a way to see unusual behaviours, command-and-control communication, lateral movement, data exfiltration, Shadow IT, unauthorised connections or activity that does not fit the company’s normal operating pattern earlier.

This is not about fear. It is about changing perspective.

Because cybersecurity should not be the last reaction after a failure. It should be the continuous ability of a company to see what is really happening.

And here we return to the telephone.

New technology rarely looks like a necessity at the beginning. Often, it looks like an exaggeration. Like a cost. Like something we have managed without so far. The same is true today when many companies talk about advanced network monitoring: “maybe later”, “for now this is enough”, “we are not a big target”, “we have IT”, “we have a firewall”.

But attackers do not wait until a company matures into a new era.

They are already in it.

They use automation, scale their operations, search for weak points, exploit distraction, complexity and lack of visibility. If a company looks at cybersecurity as if the world stopped ten years ago, it is not standing still. It is falling behind the threats.

That is why the question is no longer: is additional network monitoring a luxury?

The question is: how long can a company afford not to see its own risk?

Do companies still too often assess new security technologies through the lens of old tools? Do firewalls and classic security systems still give boards too much comfort? Where do you think the biggest blind spot is today, suppliers, remote access, cloud, IT/OT environments, AI tools, or perhaps the belief that “nothing is happening in our company”?

Someone in your network may need this question before an auditor, regulator or attacker asks it first.

Further reading: the NetSenX plans and prices, NDR vs EDR vs SIEM for teams without a SOC and what NetSenX detects and how each alert explains itself.


Written by the NetSenX Team at TriStiX S.L. Questions: [email protected].

NetSenX Team

TriStiX S.L.