Who we are.
Pavak Technologies is a vendor-agnostic NAC implementation firm. We were founded to solve a specific problem: every NAC deployment we had seen in India's enterprises failed for implementation reasons, not product reasons.
Peeyush Trivedi
CISSP · 28 years in enterprise NAC
- CISSP
- Vendor-agnostic
- FortiNAC
- Aruba ClearPass
- Forescout
- Cisco ISE
- Ruckus Cloudpath
Peeyush has spent the last 28 years designing, deploying, and fixing NAC across BFSI, manufacturing, healthcare, and IT services organisations in India. CISSP-certified. Vendor-agnostic by conviction, not coincidence. His hands-on record runs from salvaging a private-sector bank's stalled ClearPass rollout — brought to production in 12 weeks — to segmenting operational technology from IT across a six-plant manufacturing estate with no unplanned outages since cut-over.
Before Pavak, he operated under the Smart IT Solutions banner as an independent consultant. Pavak Technologies is the formalisation of that practice into a Private Limited company. peeyushtrivedi.com continues as his personal thought-leadership presence.
His framework PVESIC has been applied across many audit engagements. His R-P-Po-V-E-A troubleshooting tree has resolved broken NAC deployments across all five major platforms. Both started as field notes. Neither were invented for a pitch.
The product was never the problem. The implementation was.
Every failed NAC deployment we have investigated — and there have been many — failed because somebody rushed the implementation, not because the product was broken. Good NAC is boring. It just works. Bad NAC is dramatic. It's usually drama we could have avoided with better discipline.
Four commitments.
Customer-first
Features of the engagement are driven by what your environment needs, not what we're fastest at selling.
Technical depth
We speak NOC, SOC, and network fluently. Your infrastructure lead won't have to translate down for us.
Quality over speed
No "move fast and break things" for production networks. Our cadence matches the risk profile of what we're touching.
Transparent engagements
Written statement of work. Agreed price and timeline. Change control if scope moves. No surprises on the invoice.
Why our names
Our names come from Nyāya, the classical Indian school of logic, and from its best-known example of reasoning.
parvato vahnimān, dhūmāt — "The mountain has fire, because it has smoke."
-
Claim pratijñā
The mountain has fire
Pāvak (पावक) — fire.- Literally "the purifier", an ancient name of Agni. It is what an inference sets out to establish.
- We took the conclusion as the company's name because the conclusion is what we answer for: NAC that works in production, shown and not assumed.
-
Reason hetu
Because it has smoke
Hetuk (हेतुक) — the reason.- From hetu, the smoke: the evidence that must be shown before a claim is accepted.
- Hetuk holds technical compliance to that test: an answer is drafted as "Comply" only when a cited vendor document supports it; where there is no evidence, the row goes to a person.
-
Example udāharaṇa
Wherever there is smoke there is fire, as in a kitchen hearth
Anvay (अन्वय) — the rule that connects them.- "Wherever there is smoke, there is fire": the agreement that makes a reason count as proof.
- The word also means a connection that follows through. Anvay, our CRM, connects the dots from lead to opportunity to payment, so every payment traces back to the lead it began with.
-
Application upanaya
This mountain has smoke of that kind
Upanay (उपनय) — the application.- Literally "bringing near": the general rule is brought to the case in hand.
- This is where our work sits. A NAC product that works in general still has to be made to work on this network. The product was never the problem; the implementation was.
-
Conclusion nigamana
Therefore the mountain has fire
Pāvak, restated
It is also how we work. A claim is accepted only with its reason, and a reason counts only when the rule connecting it holds.