Portnox has design considerations that limit its applicability. If you are in a highly regulated industry with mandates requiring the solution to be completely on-premises, Portnox does not work at all. I do not think they position their products for those industries. Even for non-heavily regulated industries, if you want a self-sufficient system within your own premises, there are design constraints because at some point you must reach out to Portnox infrastructure in the cloud, and if that is unavailable, it suffers. For example, on deep-sea oil rigs without proper connectivity, it struggles. I am not sure they want to enter that particular business segment, as it may not align with their value proposition. I cannot blindly select this product and deploy it everywhere; I must make deliberate decisions first. Portnox could improve by reducing its heavy reliance on the cloud. While I do not think they want to eliminate this aspect, a complete solution for regulated entities would include some on-premises setup that is self-sufficient and does not depend on the cloud. This is the most important improvement. Second, Portnox already has a robust integration ecosystem with many vendors, but not all. Even when integration exists, the extent varies, particularly regarding vendor-specific attributes. I have never faced challenges because my security tools and stack have been standard: Cisco, Aruba access points, Cisco switches, and UniFi, all of which work well with them. However, there is room for deeper integration when compared to tools like Cisco ISE and Aruba ClearPass. Their offerings are clear, easy to onboard, and their day zero and day one onboarding activities are streamlined and straightforward. They share best practice checklists that make configuration simple.
