Entrazure
The relationship, stated first
Most pages about a partner product bury the ownership question. This one leads with it, because a buyer evaluating security tooling needs to know exactly who they would be depending on.
Klarvant builds and owns the product. The intelligence, the detection logic and the roadmap are theirs. Entrazure did not write it and does not control it.
Entrazure is an authorized reseller. You can buy the license through us, and consulting fees are quoted separately from license fees so you can see what you are paying for each. The same principle applies to the Azure subscriptions we sell as a direct CSP, described on the about Entrazure page.
Entrazure operates it as a managed security service provider. For clients who want the product run rather than delivered, we scope the perimeter, integrate the output, triage the findings and drive the escalation path with your team.
What this is not: it is not our security operations platform, it is not a brand of the group, it is not a Microsoft service, and it is not bundled into any Azure agreement. It appears under Novarque by Entrazure because sovereignty buyers ask the question it answers, not because there is any ownership link.
What namespace and digital territory intelligence means
The category is about what carries your organization’s name on the public internet, and who put it there.
Most security programs are built inward. Endpoints, identities, workloads, logs: the estate you administer. Namespace intelligence looks at the part you do not administer and cannot fully enumerate. Domains registered in your name or in something close enough to it. Certificates issued for hostnames a team stood up and forgot. Public-facing assets attributed to your organization that no inventory contains. Look-alike registrations positioned for the kind of invoice fraud that costs a manufacturer a payment run.
This surface has a specific property that makes it awkward: nobody inside the organization owns it. It is not the network team’s, because it is not on the network. It is not the identity team’s. It is frequently discovered during an incident, which is the most expensive moment to discover an inventory gap.
We describe the category rather than publishing a feature matrix, because the matrix is Klarvant’s to publish and it changes. Exact capability and coverage are confirmed with the vendor during scoping, in writing, before anyone signs.
What we do around the product
Scope the perimeter. Which brands, which legal entities, which country domains, which subsidiaries acquired three years ago and never inventoried. For a group with multiple operating names this is the work that determines whether the output is useful or noise, and it takes a working session with legal and marketing, not just IT.
Integrate it with what you already run. Findings that live in a separate console get read for two weeks and then stop being read. We route them into the ticketing and alerting path your team already uses, alongside Microsoft Sentinel and Defender XDR where those exist.
Triage. Deciding what is a takedown request, what is a certificate to revoke, what is an asset to bring back under management, and what is genuinely nothing. Volume without triage is a dashboard nobody opens.
Escalation with a named path. Who is called, in what order, with what authority to act. Agreed before the first finding, not improvised during one.
Evidence. For regulated organizations, a documented external exposure process supports the control set an auditor examines and the incident detection obligations in Loi 25. The mapping is handled the same way as everything else in compliance architecture: the control points at an artefact, and the artefact is exportable.
Where it fits, and where it does not
It fits when the organization is large enough to have lost track of its own external footprint, operates under more than one name, and has a fraud or impersonation exposure that is financial rather than theoretical. Government, financial services, large industrial groups and health networks are where the case is clearest.
It does not fit as a first security investment. If identity is unmanaged, if there is no logging strategy, or if administrative access is standing rather than time-bound, that is where the budget belongs, and cybersecurity and Entra ID is the right starting page. Buying outward-facing intelligence for an estate with an open inward-facing problem is a sequencing error we would rather point out than profit from.
It also does not fit a mid-market estate with a handful of domains. That is a quarterly review task, not a product.
How to find out which applies to you
The two-week assessment covers external exposure alongside the rest of the estate, and produces a ranked backlog with an honest cost against each item. If Klarvant belongs on that list, it will be on it with a reason. If it does not, it will not appear, and that outcome is a legitimate result of the engagement rather than a lost sale.
Related
- Novarque by Entrazure, the offer this page sits under.
- Data residency and sovereignty architecture, the adjacent question.
- Cybersecurity, Entra ID and zero trust, the inward-facing half.
- Compliance architecture, where the evidence mapping is done.
Questions we get
Is Klarvant an Entrazure product?
No. Klarvant is built and owned by Klarvant. Entrazure is an authorized reseller and operates it as a managed security service provider for clients who want it run rather than handed over. It is not our platform, not a brand of ours, and not part of the Novarque offer in any ownership sense. We are precise about this because a buyer evaluating a security product needs to know who they would be depending on.
Is this a Microsoft service?
No. Klarvant is not a Microsoft product and is not included in any Azure or Microsoft 365 subscription. It is licensed separately. Everything Microsoft in this estate, Defender XDR, Microsoft Sentinel, Entra ID, is covered under cybersecurity and identity work instead.
Does it replace Defender XDR or Microsoft Sentinel?
No, and anyone who tells you it does is selling something. Defender XDR covers endpoint, identity, mail and cloud apps. Sentinel is the log and detection layer. Namespace and digital territory intelligence looks outward at what carries your name on the public internet. Different surface, different question. They complement each other, and if you have neither of the Microsoft two, start there.
What size of organization is this for?
Enterprise and government scale. We state that on this page deliberately, because presenting it as a mid-market SKU would waste your time and ours. A 60-person firm with three domains has a spreadsheet problem, not an intelligence problem, and we will say so rather than sell a license.
What exactly does Entrazure do, as opposed to Klarvant?
Klarvant produces the intelligence. We handle the commercial relationship, scope what should be in the perimeter, integrate the output into the estate you already run, triage what comes out of it, and take it into a documented escalation path with your team. Coverage windows and response commitments are written into the service description before signature, not implied by a web page.
Can we buy the license and run it ourselves?
Yes. We will resell the license without the managed service if that is what you want. In our experience the product produces findings faster than an unstaffed team can act on them, which is why the managed arrangement exists, but it is your call and we do not bundle it as a condition.