Resources

Keep It Koncise

Straight-talking cybersecurity insight. No jargon, no scare tactics - just what you need to know.

← Back to Blog

Who Else Can Talk to Your Customers?

Identity & Access

Who Else Can Talk to Your Customers?

7 Oct 2026 · Max Harper, Koncise Solutions

Email platforms, CRMs, push notifications, SMS gateways. Most organisations now hold a collection of systems that can speak to customers as them. Who else has that access?

Most organisations spend a lot of time thinking about protecting their data.

Quite rightly.

But there's another question that probably doesn't get asked anywhere near enough…

Who else has the ability to speak to your customers as you?

Because almost every organisation now has a growing collection of platforms capable of doing exactly that.

  • Email marketing platforms.
  • CRM systems.
  • Push notifications.
  • SMS gateways.
  • Customer service tools.
  • Social media platforms.
  • Marketing automation.

All legitimate.

All incredibly useful.

And, in some cases, capable of reaching thousands or even millions of customers in a matter of seconds.

That's quite a lot of trust sitting behind a login.

Borrowing your credibility

The interesting thing about these platforms is that an attacker doesn't necessarily need to impersonate you.

If they compromise the right platform…

they are you.

At least as far as the customer is concerned.

A notification arrives from an app already installed on their phone.

An email comes from your legitimate domain.

A message appears in a channel they've trusted for years.

Why wouldn't they believe it?

That's what makes these incidents so potentially damaging.

Even if the initial compromise is relatively contained, the attacker has gained something incredibly valuable - your credibility.

They can create panic.

Direct customers towards malicious sites.

Support an extortion attempt.

Send fraudulent instructions.

Or simply create enough doubt that customers no longer know whether the next genuine message they receive is actually genuine.

…and now you have two incidents to deal with.

The technical compromise.

And a trust problem.

Because cyber incidents don't stay inside IT

This is the bit I think we sometimes underestimate.

Cyber incidents can move from a technical issue to a business issue incredibly quickly.

Customers start asking questions.

Suppliers and partners want reassurance.

The board wants to understand the exposure.

Legal, insurance and communications teams get involved.

And for publicly listed organisations, markets can react long before the forensic investigation has finished.

We've seen plenty of examples where the announcement of a cyber incident alone has caused a company's share price to fall.

Not necessarily because investors already understand the full impact.

Quite the opposite…

uncertainty is the impact.

What happened?

What systems are affected?

Was data accessed?

Can customers still trust the organisation?

How long will this last?

What will it cost?

The technical facts might take days or weeks to establish.

The reputational and commercial reaction can happen in minutes.

Now imagine the attacker can still communicate

This is where it gets particularly interesting.

Imagine an attacker compromises one of the platforms you use to communicate with customers and sends a malicious message.

You identify it.

You contain the account.

You start investigating.

Great.

Now you need to tell your customers that the previous message wasn't genuine.

So you send another message…

Why should they trust that one?

Email them?

What if they've just been told your communications have been compromised?

Post something on social media?

Is that account trusted?

Put something on the website?

Who owns that communication and how quickly can it be published?

Suddenly “send a customer communication” isn't quite as straightforward as it sounds.

Your incident response plan therefore needs to consider something beyond containment and recovery:

How do we establish a trusted source of truth when one of our trusted communication channels can no longer be trusted?

That is a really good tabletop question.

…and one I'd wager quite a few organisations haven't tested.

Start by understanding who can speak for you

Before getting into technology, I'd start with something really simple.

Make a list.

Every platform that can communicate externally using your brand.

Then ask:

  • Who owns it?
  • Who has administrator access?
  • Is that access tied back to our central identity platform?
  • Is MFA actually enforced?
  • Are there local accounts sitting outside SSO?
  • Do agencies or suppliers still have access?
  • Are there shared credentials?
  • What API keys or tokens exist?
  • Could one administrator message the entire customer base?
  • Would we know if somebody did?

That last one is particularly important.

Because preventing every compromise isn't realistic.

Spotting something unusual quickly absolutely is.

If a marketing administrator suddenly logs in from somewhere unusual and attempts a mass send at 2am… somebody should probably know about it.

That's where identity security, SaaS security monitoring and 24/7 detection start becoming just as relevant to Marketing platforms as they are to the traditional IT estate.

Because attackers don't really care which department bought the software.

And then there's email…

Email deserves its own mention because protecting the ability to send legitimate email is only half the problem.

You also need to stop everybody else pretending to be you.

SPF, DKIM and DMARC are fundamental parts of that.

Implemented properly - and importantly, with DMARC actually moving towards enforcement - they make straightforward domain spoofing considerably harder.

Brand monitoring can take that further by identifying lookalike domains, impersonation attempts and infrastructure being created around your brand before customers start interacting with it.

But there's an important distinction here.

DMARC can't protect you from an attacker who has compromised a legitimate sender.

If your marketing platform is authorised to send email on behalf of your domain and an attacker compromises that platform, the email may pass SPF.

It may pass DKIM.

It may pass DMARC.

Because technically…

…it came from somewhere you've told the internet to trust.

Which is why email authentication, identity security, SaaS security and monitoring all have to work together.

There isn't one magic control.

The bigger problem is SaaS sprawl

Ultimately, I don't think this is really a story about push notifications, email or any individual platform.

It's a SaaS problem.

Businesses have accumulated hundreds of cloud applications over the last decade.

Some are controlled tightly by IT.

Some aren't.

Some use SSO.

Some have an old username and password somebody created three years ago.

Some are managed by agencies.

Some have API connections into other systems.

Some probably haven't been thought about since the day they were implemented.

Yet many of them hold customer information, business data…

…and increasingly, the ability to speak on behalf of the organisation.

That makes them part of your attack surface whether they're sitting on IT's asset register or not.

So maybe add another question to your incident plan…

We spend a lot of time asking:

What happens if somebody gets into our systems?

Maybe we should also be asking:

What happens if somebody gets hold of our voice?

Who detects it?

Who shuts it down?

How do we communicate?

Where is the trusted source of truth?

How do our customers know which message is real?

How do we reassure suppliers and partners?

…and how quickly can we answer those questions while customers, journalists, regulators and potentially the markets are already asking them?

Because protecting your data matters.

Protecting your systems matters.

But protecting your organisation's identity, reputation and ability to communicate with the people who trust you probably deserves just as much attention.

Attackers don't always need to pretend to be your business.

Sometimes they just need access to something that already can.

If this is resonating with conversations you're having internally at the moment, or wondering where to begin and you'd like to learn more, arrange a conversation with a member of the Koncise team today.

Want to talk it through? Arrange a conversation with the Koncise team.

Koncise Solutions - Not your MSP. Not your Reseller. Your Cybersecurity Partner.