Asset Intelligence Before AI: Teqtivity’s Hiren Hasmukh

Pairing hardware retrieval with access revocation sounds straightforward, but getting two separate teams to treat it as one single step is rarely as clean as the logic suggests. For distributed teams spanning contractors and multiple countries, where does the zero-trust principle of “never trust, always verify” start to break down, and what has to be true underneath it for the framework to work as intended?

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

Early on, most organizations treat offboarding as an HR and IT access problem. Accounts get disabled, credentials get revoked. That part happens fast. The physical device is an afterthought. Someone sends an email asking for it back and hopes for the best.

The pattern we see most often is AI tools getting pushed to endpoints that IT has lost track of. A device assigned to someone who left. Hardware in a remote office with no active management. The tool is live and running — IT just doesn’t know on what.

HH

Thank you for that introduction, Hiren. We have a clearer sense of your role and what Teqtivity is doing in the market. Across the leadership conversations we are having right now, the same technology pressures keep appearing: how AI is embedding into everyday operations, how security and trust are keeping pace, and what those shifts demand from technology leadership. What was the moment that most sharpened your own thinking about how organizations should approach AI, and was it about adopting something internally, or something else entirely?