Start from the problem.

The areas below are the ones we cover, and four more have an agreement in progress. If your problem is not in one of them, we would rather tell you than sell you the thing next to it.

Why these areas

These are not a menu we assembled from a category list. Each one is an area where a buyer in the region already has a budget line and someone asking about it.

Identity and key protection are asked about because they can be checked. An auditor can open a directory and read its configuration, and a tender can name a certification by number. Exposure management is here because the annual penetration test stopped matching the rate at which an estate changes. Threat intelligence is here because the evidence that matters appears outside the perimeter, where nothing inside it is looking. The human layer is here because it is the control that can be retrained, and the one that can be measured before and after.

Browser security and deception are here for a narrower reason. Each has a product in this portfolio that wins on a difference a buyer can verify inside a trial, rather than on a category argument.

Endpoint security is here for the opposite reason to all of them. Every organisation already has the budget line and a product installed against it, so nothing in this area is a category argument. The only question worth asking is what a replacement does that the installed product does not.

The four still in negotiation are on the list for the same reason as the rest. Network security, data masking, API security and AI runtime security are each an area where a buyer here already has the budget line. We would rather arrive in one of them with a single product we can argue for than with three we cannot.

Tell us the problem.

We will name the product, or the vendor we are still negotiating with, or nothing. All three happen.