Skip to content

Vendors

the vendors we work with.

Three platforms carry the vendor side of our work: Fortinet across the network, alongside Flair.io and IBM QRadar.

Fortinet has a page of its own, and this one links to it. The other two are here because the work uses them — their fuller descriptions are still being written rather than guessed at.

Vendor platforms

three platforms, one honest page.

One of these has a page behind it. The other two have a logo, a name and no documented detail yet, and this page shows that difference rather than levelling it up with copy nobody can stand behind.

Fortinet

Official Fortinet partner · certified experts in Fortinet Security Fabric

Most of our network work lands on Fortinet: we design the solution, deploy it, migrate whatever is already running, and then manage and monitor it. The reason for standardising on it is the Security Fabric — one console for the estate, shared threat intelligence, automated response and one set of policies across network, endpoint and cloud.

network security

  • FortiGate NGFW
  • FortiSwitch
  • FortiAP

security operations

  • FortiAnalyzer
  • FortiManager
  • FortiSIEM

cloud security

  • FortiCloud
  • FortiWeb
  • FortiCASB

what we do with it

design & architecture · implementation · migration · managed services · training · support

explore fortinet

Flair.io

vendor platform

A vendor platform we work with. A fuller description of what we run it for is in preparation — until then this entry says less rather than more.

talk to an engineer

IBM QRadar

security information & event management

A SIEM platform: it collects logs and events from across an estate and correlates them into alerts somebody can act on. A fuller description of how we use it is in preparation.

talk to an engineer

How we get to a product

the equipment is the last decision, not the first.

Two lines from work we have written up. Both are about vendor equipment rather than about vendors.

  • If your network was never designed, the useful first step is finding out what you actually have rather than buying a firewall.

    from “A whole company on a shop-bought router”

  • Equipment usually degrades rather than failing outright, so protecting against it needs a second device that is genuinely ready, monitoring that notices a trend rather than an outage, and a willingness to automate around a known fault.

    from “The quiet month when nothing happened”
read the case studies

Next step

already running one of these?

Tell us what is deployed and what it was bought to cover, and we will say whether it is doing that — and what it would take if it isn’t. No rip-and-replace as an opening move.

book a consultation