The engagements that break the defaults.
A standard SOC engagement assumes an estate of managed endpoints, a patch window, and a containment action that is safe to take. Six kinds of environment break at least one of those assumptions, and each one needs a different answer rather than a louder version of the same one.
Vijilan's specialty services are the managed security engagements where a standard SOC engagement's assumptions do not hold.
Six of them. Non-human identity, where the account has no person attached so MFA, offboarding and access reviews all fail. Agentic and GenAI workloads, where the thing being protected reasons and acts on its own. OT and industrial control, where availability outranks confidentiality and an isolation action can stop a process line. Connected medical devices, where much of the estate cannot take an agent or be patched on your schedule. Regulated and sovereign environments, where proving where the telemetry lived matters as much as detecting the intrusion. And proactive threat hunting, for the client who already has monitoring and wants to know what it is not reporting.
All six are built to run white-label behind an MSP, MSSP or consultancy, with the partner's brand on the reporting. Vijilan never competes with a partner for that partner's clients. Organizations that prefer to contract directly can.
Named by the problem, not the product.
Because that is how a partner describes the client sitting in front of them.
Including whether you need the rest of it first.
What counts as a specialty service here?
Work that needs something the standard managed SOC engagement does not assume: a different asset model, a regulator with its own evidence expectations, or an environment where the usual containment action is unsafe. It is not a premium tier of the same service. It is the set of engagements where the default assumptions break.
Are these delivered through partners?
They are built to be. Every one of them runs white-label behind an MSP, MSSP or consultancy, with your brand on the reporting and your service desk in front of it, and we never compete with our partners for their clients. Where an organization would rather hold the contract with us directly, it can.
Do we need to already run a Vijilan service to add one?
No. Several of these are taken on their own, particularly threat hunting and non-human identity discovery, and are frequently the first piece of work a partner brings us because they are bounded and the output is something you can hand a client.
How is any of this priced?
Through partner verification rather than a published rate, because the cost drivers differ sharply between them: asset counts for some, data volume for others, and hunt cadence for ThreatHunt™. The pricing wizard routes a verified work email to real numbers.
The ones worth a call
are the awkward ones.
An environment where the obvious containment action is unsafe, an estate that cannot take an agent, or a client asking what their AI agents are actually authorized to do. Those are the conversations this page exists for.