Q: Aruba’s APIs and versions keep changing. How do you keep this working reliably?

A: Keeping up with Aruba Central versions and API changes is part of the managed service:

§  We maintain our own API libraries for Aruba, including handling differences across “old” and “new” Central versions.

§  We monitor vendor changes and update GuestConnect so integrations keep working.

§  You avoid building and maintaining brittle, internal scripts every time Aruba releases an update.

Q: How does GuestConnect relate to ClearPass (or similar NAC platforms)?

A: GuestConnect and NAC platforms complement each other:

§  ClearPass (or equivalent) is excellent for policy enforcement, posture assessment and device identity.

§  GuestConnect focuses on automated, time‑bound guest credential lifecycle tied to visitor management.

In practice:

§  GuestConnect can trigger creation and removal of guest access in your NAC or Wi‑Fi controller,

§  ClearPass (or equivalent) can then enforce granular policies on those sessions.

Invise has experience across both, so we can design an integrated solution rather than choosing one or the other in isolation.

Q: How do you make sure guest devices are truly isolated from our operational and corporate systems?

A: We design GuestConnect to work with your network segmentation strategy, for example:

§  Dedicated guest VLAN(s) with strict firewall rules

§  Aruba isolation profiles to limit what guests can see and do

§  Options from “internet‑only” to more permissive for specific use cases (e.g. casting in a meeting room)

GuestConnect then:

§  Issues credentials that land guests on these controlled segments

§  Ensures each guest’s access is time‑bound and individually traceable

The result is that guests get the access they need, while critical systems (like CCTV, irrigation, BMS, operational networks) stay protected.