This is sample heading text

This is sample heading text

Is your application layer secure?

Is your application layer secure?

Ask a New Zealand managed security services provider (MSSP) to look after your laptops, your network and your Active Directory, and you'll usually get a solid job. Ask the same provider to defend a Kubernetes cluster, a public API or the service accounts your microservices use to talk to each other, and the conversation can get a lot less certain.

MSSPs were built to protect the business estate, and most do it well. But a growing share of the risk now sits in the application infrastructure that runs your digital products, and in our experience that layer often falls between your MSSP and the team that built the software.

The gap we keep seeing

We've worked alongside a lot of MSSPs that look after our clients' application infrastructure. In our experience, defending Kubernetes and APIs, segmenting networks in a cloud environment and managing service accounts sit outside what most of them were set up to do, so they end up moulding their model to make it fit.

What we often see is controls designed for laptops and office networks being applied to systems that behave nothing like them. A service account isn't a person, and traffic between services inside a cloud environment never passes through the perimeter firewall. The result can be a gap nobody owns or heavy, blanket controls that slow delivery without reducing much risk.

Why it matters more now

The time between a vulnerability becoming known and someone exploiting it has collapsed. The average time-to-exploit fell from 63 days in 2018 and 2019 to five days in 2023, and more than 44,000 new CVEs were published in 2025, depending on how you count them. Most of those live in the frameworks, libraries and open-source dependencies inside modern applications, where a monthly patch cycle struggles to keep pace with exploitation measured in days.

There's a popular view in the industry right now that attacks are getting faster rather than more sophisticated. I don't agree, because that's not what we're seeing. Attacks are getting faster and more complex at the same time, and that combination is exactly what punishes a security model built around the perimeter.

Being a small country at the bottom of the world doesn't help either. In 2024/25 the NCSC triaged 331 incidents of potential national significance.

Why builders are better placed to secure it

We spotted this gap about four years ago and shaped our security practice around it. We build these applications, so we understand the technology and the risks that come with it. That lets us put targeted controls around the risks that matter, rather than locking everything down and slowing the team.

Security has to be included from the start, and not in a performative way. On our builds, a security lead is typically involved from day one, shaping the security architecture, and stays involved through delivery and for the life of any managed services contract.

Working alongside your MSSP

We're not trying to look after your laptops or run your network. That space is already well served. We'd rather work alongside your MSSP and cover the application layer they aren't set up for.

Tooling helps, but it doesn't make the call

Tooling is moving fast on patching. But someone still has to decide which findings matter in your architecture and whether a fix will break something downstream. A misconfigured network policy or an over-privileged service account won't show up as a CVE.

Want a second opinion on your application security? Talk to our security team.

Is your application layer secure?

Role

Director of Security & Technical Operations

Based

Tāmaki Makaurau, Auckland

Most cyber advice is fear with a logo. We deliver the version that holds up.

I'm George and I lead Security & Technical Operations at RUSH alongside a full-stack managed services and technology operations practice serving enterprise and critical-infrastructure clients across APAC.