Azbers Signal

One short observation, every other day.

Azbers Signal is a short running note on what changed in the threat and compliance landscape. Each entry carries an operational note and can be exported as a branded image for your own briefing.

Archive

Everything published so far.

The newest sits at the top. Read the whole run, pick a date, or pick a topic below, and export any entry as a branded image for your own briefing.

All 41 signals, newest first.
Supply ChainLatest22 November 2026 at 09:10

The breach came through an application you connected, not a system you run.

Several of the largest incidents this year involved unauthorised access to third party applications holding customer and health data.

Operational note

Nothing on your network is touched in that pattern, which is why the usual tooling misses it. List every third party application with granted access to your major tenants, check who approved each one, and remove what nobody can justify. Most teams stop naming them somewhere in the first ten.

SaaSThird Party RiskOAuth
Read source
AI Security20 November 2026 at 09:10

An AI application builder that runs code is a remote execution risk.

Frameworks that let a user compose a flow and execute it have been exploited for unauthenticated code execution.

Operational note

The feature and the vulnerability are frequently the same thing, because executing user supplied logic is the product. If you run one of these, it should not be reachable from the internet, it should require authentication, and it should run somewhere its compromise does not reach anything else.

AI SecurityRemote ExecutionExposure
Read source
AI Security18 November 2026 at 09:10

Your AI framework is now production infrastructure.

Authentication weaknesses in AI gateway and orchestration components have been added to the exploited list, which changes what they are.

Operational note

A component that routes model calls holds API keys for every provider behind it and usually sits on an internal network nobody segmented. Treat it as production infrastructure with an owner, a patch cycle and an inventory entry, not as a piece of the experiment it started as.

AI SecurityInfrastructurePatching
Read source
Vul16 November 2026 at 09:10

The appliance at your edge is on the exploited list again.

Remote access and secure access appliances keep arriving in the known exploited catalogue, and they sit by definition on the internet.

Operational note

These devices are attractive because they are reachable, they hold credentials, and they are frequently excluded from the patch cycle that covers servers. Find out who owns yours, what version it runs, and whether it appears in the catalogue this month. The answer to the third question is more often yes than teams expect.

Edge DevicesPatchingRemote Access
Read source
Supply Chain14 November 2026 at 09:10

A framework aimed at infrastructure never stops at infrastructure.

If you supply technology into a regulated organisation, their obligation reaches you commercially even where the framework does not name you.

Operational note

The organisation you serve has to evidence its supply chain, so the question arrives as a contract clause rather than a regulation. A small software house with three public sector clients is inside this whether or not it considers itself in scope. Find out now, not during their audit.

Supply ChainThird Party RiskCompliance
Read source
Data Protection12 November 2026 at 09:10

Ask where RSA is used and watch the room slow down.

Teams name the certificates and the VPN quickly. Then the honest answer starts including a library chosen years ago and a signing key held by somebody who left.

Operational note

A cryptographic inventory is worth building even if quantum computing never arrives, because it answers a question you cannot answer today: what breaks if an algorithm is deprecated tomorrow. That has already happened twice with hash functions and it will happen again.

CryptographyAsset ManagementRisk
Read source
What we write about

The ground it covers.

Roughly the same ground the rest of the company works on, which is deliberate. We write about what we are actually doing that month, and each topic here opens every signal filed under it.

Pick a topic to read every signal on it in the archive above.

What is in one

Four lines, and none of them wasted.

A signal is short on purpose. If it takes longer than a minute to read, it competes with the work it is supposed to support.

01

What changed

One observation, written plainly. Not a summary of the week, and not a link to somebody else's blog.

02

Why it matters

The control or the exposure it touches, so you know whether this is your problem before you finish reading.

03

What to verify

An operational note with something specific you can check today. This is the part that makes it worth publishing.

04

Something you can share

A branded card you can export and drop straight into a briefing, without rewriting it first.

Questions we get asked

Before you get in touch

The questions that come up most often, answered the way we would answer them on a call.

How often does a signal appear?

Roughly every other day. The stream is written ahead of time and each entry appears on its own date, so it keeps moving even in a week when everyone is busy.

Can I use these in my own briefings?

That is what the export is for. Every signal can be saved as a branded card you can drop straight into a deck or a message without rewriting it.

Is this a newsletter?

No, and deliberately not. There is nothing to sign up for and nothing tracking you. It is a public page you can read when it is useful and ignore when it is not.

Where do the longer pieces live?

In the article library. Signal is for the one thing worth checking this week. Articles are for arguments that need more room.

Why it exists

A company blog nobody updates is worse than no blog at all.

Signal was built as the sustainable alternative. One short observation is something a working security team can genuinely produce, and it stays useful precisely because it is small.

For longer arguments there is the article library, which moves at a different pace on purpose.

01

What changed

One observation, stated plainly.

02

Why it matters

The control or exposure it touches.

03

What to verify

A check you can run today.

04

Share it

Export a branded card for a briefing.