platform security – Linking Humans ServiceNow Recruitment

In the last fortnight ServiceNow patched three vulnerabilities in its AI Platform that each scored a perfect 10.0, none of which required authentication to exploit. In the same window it expanded the AI Control Tower to govern AI across any system in the enterprise, whoever built it. I think those two events point at the same career opportunity, and at a profile the market is short of.

What happened

The advisory came out on 27 August. CVE-2026-18885 allowed arbitrary code execution. CVE-2026-18886 allowed privilege escalation through improper access control. CVE-2026-74820 was a SQL injection flaw against the underlying database. All three scored 10.0, none required authentication or user interaction, and all three were rated low complexity. A fourth, a sandbox escape, scored 8.7.

ServiceNow patched hosted instances directly and released hotfixes for self-hosted deployments across Xanadu, Yokohama, Zurich and Australia.

Separately, coverage in early September described the AI Control Tower being expanded to discover, observe, govern, secure and measure AI deployed across any system, not just ServiceNow’s own. I have not pinned the exact announcement date, so take the timing loosely. Alongside that, this year’s acquisitions tell a consistent story: Armis for asset visibility, Veza for identity governance, and Sweep, which ServiceNow confirmed as completed on 1 September, for a governance layer spanning ServiceNow, Salesforce and HubSpot.

Read those together

ServiceNow is becoming the place enterprises govern all their AI. Which makes the ServiceNow platform itself a very high-value target, and makes the person who secures it a very hard person to replace.

The role that is forming

There is a gap opening between two established professions and it does not yet have a settled job title.

Security teams own vulnerability management but frequently lack depth on the ServiceNow platform itself. Platform teams own the instance but sit inside IT service management, where security advisories are not the daily rhythm. Advisories land in the space between and both sides assume the other has it.

The people who can occupy that gap need three things at once: real hands-on platform knowledge, enough security literacy to read an advisory and work out what it touches in a specific configuration, and enough standing to force an out-of-cycle change when it matters. That is an unusual combination. My expectation is that scarcity of that kind gets priced eventually, though I am not going to pretend I can show you a published benchmark for a role that does not yet have a settled title.

It is also getting broader. When agents hold credentials and act autonomously inside your environment, they become identities that need governing like any other. The controls we built over two decades for human insider risk mostly have not been applied to them, because attention has been on the productivity gain. Somebody has to close that, and it will not be a pure security person or a pure platform person.

How to move towards it

1. Start with what you already have. If you are a platform person, you are closer to this than a security generalist is. Platform depth is the harder half to acquire. Security literacy on top of real ServiceNow experience is a shorter journey than the reverse.

2. Learn the machine identity side. The Zurich release documentation covers capability for securing machine-to-machine integrations, including the Vault and Machine Identity consoles. Check the release notes for what is in your version, then get hands-on. This is the concrete, learnable part of the agent governance problem, and it comes up far less often in conversations than the strategy layer does.

3. Read the advisories, properly. Not the headline. Go and understand which components each CVE touched and why. Doing that four times will teach you more about the platform’s attack surface than any course, and it costs nothing.

4. Build one governance story. How you handled access, auditability, or the decision not to automate something. Even small. Hiring managers are nervous about exactly this and hardly any candidate raises it unprompted.

5. Learn to talk about risk in business terms. The question that decides these interviews is some version of: an agent takes a wrong action against customer data at 2am on a Sunday, what happens? If you can answer that with a clear account of accountability, detection and rollback, you are ahead of nearly everyone.

A realistic word on timing

I am not going to tell you this is an easy pivot or that a certification unlocks it. It is a genuinely senior profile and it usually forms out of an architect or senior developer who has been pulled into governance work informally and then made it their identity.

What I will say, and I want to be clear this is my read rather than a measured finding, is that the demand side is visible in what ServiceNow is buying and building, while the supply side looks thin to me from where I sit. If that is right, it is a good window. If I am wrong about the supply side, the worst case is that you have gone deep on security and governance skills on a platform that is becoming the enterprise control plane for AI, which is not a bad place to be wrong.

If you are three or four years into ServiceNow and wondering where to go deep, this is the most defensible direction I can point you at.

Thinking about your next move? We speak to ServiceNow professionals across the UK, Europe and North America every day and we are happy to give you an honest read on your profile, whether or not you are actively looking. Start a conversation.

Sources: ServiceNow security advisory, 27 August 2026 · SecurityWeek, 31 August 2026 · ServiceNow newsroom

On 27 August, ServiceNow published a security advisory covering four vulnerabilities in the AI Platform. Three of them scored a perfect 10.0. None of them need authentication, none need user interaction, and all three are rated low complexity to exploit. If you run ServiceNow self-hosted, the patch is your job, and the clock started two weeks ago.

What was disclosed

CVE-2026-18885, CVSS 10.0. Code injection allowing arbitrary code execution, with potential access to and modification of data.
CVE-2026-18886, CVSS 10.0. Improper access control allowing an attacker to create or modify arbitrary data and elevate privileges.
CVE-2026-74820, CVSS 10.0. SQL injection allowing arbitrary SQL statements against the underlying database, and access to instance data beyond what was intended.
CVE-2026-6876, CVSS 8.7. A sandbox escape, also exploitable without authentication.

ServiceNow patched its hosted instances directly. Hotfixes were released for self-hosted deployments across the Xanadu, Yokohama, Zurich and Australia release families. The company says it has no evidence of exploitation and that the issues came out of its own research and responsible disclosure programmes.

The split that matters

ServiceNow states it patched hosted instances. Self-hosted deployments need the hotfix applied by you. Either way, confirm remediation status against your own instance list rather than assuming it, particularly if you have multiple instances or any inherited from an acquisition.

The gap between disclosure and patching

Jason Brown, director of counter fraud operations at iCOUNTER, made the point sharply in SecurityWeek’s coverage. Self-hosted organisations now have to find, schedule and apply the patch themselves, and in many organisations that takes weeks rather than days. During those weeks an unauthenticated attacker with a working exploit has a real shot at systems sitting next to HR records, vendor onboarding and finance approvals. His advice was not to wait for the normal patch cycle and to confirm it is applied this week.

That advice was published on 31 August. It is nine days old.

Why I’m writing about this on a recruitment blog

Because “find, schedule and apply” is not a technical instruction. It is a description of a person, and in a lot of ServiceNow estates that person does not clearly exist.

ServiceNow platform security tends to fall between two teams. The security function owns vulnerability management but often has limited depth on the platform itself. The platform team owns the instance but sits inside IT service management, where security advisories are not the daily rhythm. So the advisory lands, both teams assume the other is handling it, and the patch cycle quietly absorbs something that needed to be treated as urgent.

The organisations that handle this well have one named person who owns ServiceNow platform security specifically. Not security in general. Not the platform in general. The overlap. And that is a genuinely awkward role to fill, because it needs someone who can read a ServiceNow advisory, understand what it touches in your configuration, and have the authority to force an out-of-cycle change.

Four questions worth asking this week

1. Are we hosted or self-hosted, and does everyone in the room agree? It sounds trivial. In organisations with multiple instances and a history of acquisitions, it frequently is not.

2. Who received the 27 August advisory, and what did they do with it? Not who should have received it. Who did.

3. Do we have a route to apply an emergency ServiceNow patch outside the normal change window? If the answer involves a CAB meeting three weeks out, you have found your problem.

4. Is ServiceNow platform security in anyone’s objectives? If it is not written down as someone’s responsibility, it is nobody’s.

The wider pattern

This is the third time this year the same shape has appeared. ServiceNow ships capability at pace, and the operational burden of running it safely lands on customers who have not resourced for it. The AI Platform is now the layer holding your workflow logic, your identity data and your audit trail. Three unauthenticated 10.0s in that layer is a serious thing, and the fact that it was found and fixed responsibly is genuinely reassuring. What is less reassuring is how many organisations will not have applied the hotfix by the end of this month.

If you are self-hosted and you cannot say with confidence that the patch is in, that is today’s job, not this quarter’s.

Need someone who owns the overlap between ServiceNow and security? It is one of the harder profiles in the market and we recruit for it regularly. We can tell you what it pays and how long it takes before you commit to a requisition. Talk to us.

Sources: ServiceNow security advisory, 27 August 2026 · SecurityWeek, 31 August 2026 · BankInfoSecurity, 1 September 2026

Tag: platform security

The ServiceNow Job Nobody Trained For Is The One Everybody Now Needs