Operating since 2002 · Delhi NCR and Dallas, Texas
Nearly everyone arrives with one of three worries. Something is not working and nobody can say why. Something might already be inside and nobody would know. Or someone — a board, a customer, a regulator — has asked whether any of it would hold up.
Knowing which of those you are asking is most of choosing the right service, so the pages below are grouped that way rather than by our internal departments. Each entry gets one honest line and a link; the detail lives on the page itself.
The map
Where everything sits
The three overlap in practice — a network problem and an intrusion can look identical for the first twenty minutes, which is exactly why we keep the NOC and the SOC on the same floor and staffed separately. But as a way to find the right page, the question you arrived with is the fastest route.
Availability and performance
Is it working?
NOC as a Service
24/7 monitoring with a probe at every site and the platform included rather than licensed per device.
Managed NOC services
Fully managed network operations for Indian estates, with escalation and vendor co-ordination.
Network management (NMS)
Network management services across SNMP, NetFlow and API telemetry — the platform and its tuning, with or without the 24/7 desk.
Enterprise networking
Campus and wireless design: site surveys, capacity planning, access point placement and 802.1X.
SD-WAN
Branch connectivity with local breakout — and an honest account of the branch security it creates.
Managed IT services
Service desk, endpoints, identity and procurement, with the pricing models compared properly.
Detection and response
Is someone in it?
Managed SOC services
The whole security operations function, compared against MDR, MSSPs and managed SIEM.
SOC as a Service
The subscription model, with pricing against building in-house and Indian regulatory duties.
Managed SIEM
Collection, retention and tuning — including how to stop the bill scaling with your coverage.
SOAR
Playbooks that automate response, and a clear line on what should never be automated.
Detection and response
EDR, XDR and MDR compared by what each can actually see, not by feature list.
Threat hunting
Hypothesis-led search for what no rule was written for, measured on coverage rather than kills.
Email security
Business email compromise, DMARC done properly, and why a gateway cannot stop invoice fraud.
Assessment and assurance
Would it hold?
VAPT
Network, application and cloud penetration testing with prioritised, exploitable findings.
Application security
What SAST, DAST, SCA and manual testing each catch — and the flaws no tool finds.
Infrastructure security
Hardening, segmentation and the attack path, scored on the chain rather than a checklist.
Cloud security
Shared responsibility in practice, the CSPM acronym soup, and where breaches actually start.
OT and ICS security
Industrial security that respects what a running plant can tolerate. Passive by default.
Compliance
Which framework applies, and the evidence an auditor will accept rather than a policy set.
Backup and disaster recovery
Backups verified by restoring them, isolated from the credentials that protect production.
Getting started
Three sensible ways to begin
Most engagements start narrow and widen. None of these require restructuring anything, and each answers a question you can act on within a quarter.
Start with an assessment if you do not know what you have
The most common first engagement, and the one that most often pays for itself immediately. Discovery routinely finds devices nobody remembered, a vendor connection nobody documented, and at least one circuit still being invoiced for a site that closed.
Start with after-hours cover if the problem is the rota
Nights, weekends and public holidays are the hardest and most expensive hours to staff internally. Taking only those requires no restructuring, and a quarter of it tells you more about a provider than any reference call.
Start with one thing if you are being asked for everything
A board asking for “cyber security” and a regulator asking for a specific control are different problems. We would rather scope the second properly than sell against the first.
A contract that cannot change shape without renegotiation is worth noticing before you sign it. Requirements move, and an agreement that cannot move with them becomes the reason to change provider rather than the reason to stay.
Working with us
What we are, plainly
A network and security operations business that has been doing this since 2002, from a floor in Delhi NCR, with a US entity in Dallas for clients who need one.
We watch what we build
The team that designs your network is the team answering the alert about it at 3 a.m. That connection changes what we recommend at the design stage.
NOC and SOC kept separate
Same floor, different desks. Availability and attack are different questions needing different skills, and one desk doing both does neither properly.
Multi-vendor by necessity
Real estates are mixed. Fortinet primarily — we are a partner and say so — alongside Cisco, Dell, Palo Alto and Sophos.
Certified operations
ISO/IEC 27001:2022 with our operations centre inside the certified scope, and the scope statement available on request rather than asserted.
We will argue you out of things
Several pages here recommend against buying something. That is deliberate, it costs us sales, and it is why the rest is worth reading.
Two entities, stated clearly
P J Networks Pvt Ltd in India, P J Networks LLC in Dallas, Texas. The Indian entity holds the ISO certification.
Questions we get asked
Choosing a service, answered
Where should we start?
With whichever of the three questions above is actually bothering you. If you do not know what you have, start with an assessment — it is the engagement that most often pays for itself immediately, because discovery finds things nobody remembered. If the problem is that your team cannot cover nights and weekends, start there instead: it needs no restructuring and it is the lowest-risk way to evaluate any provider, including us.
Do we have to take everything from one provider?
No, and you should be wary of anyone who implies otherwise. Plenty of our engagements are a single service alongside other suppliers. Where consolidation genuinely helps is when the same team both designs and watches something — the people who built the network answering the alert about it — but that is a benefit to weigh, not a reason to move everything at once.
What is the difference between your NOC and SOC services?
A NOC watches availability and performance: is it up, is it fast, is it saturated. A SOC watches for attack: is someone in, is this authentication normal, is this traffic exfiltration. Different alerts, different skills, different people. We run both, deliberately separated rather than one desk wearing two hats — see NOC as a Service and managed SOC services.
Can you work with the tools we already own?
Yes, and it is common. Where you have already licensed a capable SIEM, EDR or monitoring platform, the sensible engagement is people and process on top of it rather than a replacement. We will tell you plainly what your existing platform does not cover before proposing anything additional.
Do you only work with Fortinet?
We are a Fortinet partner and it is what we deploy most, which is worth knowing when you read our recommendations. We also work across Cisco, Dell, Palo Alto and Sophos, and we manage mixed estates containing all of them. What your team can already operate confidently usually matters more than any feature comparison — see technology partners.
How are engagements usually structured?
Most begin narrow and widen: a single assessment, or after-hours cover, or one service that was clearly missing. Contracts should be able to change shape without renegotiation, and a provider whose agreement cannot accommodate that is a provider you will outgrow awkwardly.
Do you work with organisations outside India?
Yes. Our operations run from Delhi NCR, and P J Networks LLC in Dallas, Texas is the entity a US client contracts with. Several pages here are written without Indian regulatory framing for exactly that reason — the underlying engineering does not change with the jurisdiction, but the obligations do.
What size of organisation do you work with?
From single-site businesses to multi-site enterprises with plant networks. The honest constraint is not size but coverage expectation: an organisation wanting genuine 24/7 response is buying a different thing from one wanting business-hours support, and the arithmetic behind that difference is set out on the NOC and SOC pages.
Will you tell us if we do not need something?
It is the most useful thing a provider can do and we try to make a habit of it. Several pages here argue against buying things — that business email compromise is stopped by a finance process rather than a product, that a scanner-only programme is not application security, that SOAR fixes nothing about detection. Those positions cost us sales and they are the reason the advice is worth reading.
How do we get a quote?
Tell us the estate rather than the requirement: how many sites and devices, what hours you need covered, what you already run, and what you would least like to lose. We will scope against that and say where a smaller engagement would serve you better.
Next step
Tell us the estate, not the requirement
How many sites and devices, which hours need covering, what you already run, and what you would least like to lose. That is enough to scope properly — and if a smaller engagement than you were planning would serve you better, we will say so before quoting the larger one.