COBUNDU API and all apps/touchpoints communicate over https i.e. 443 should be good enough.
Specific to Qbic devices -> The device control platform (1st DC tab specific to Qbic) communicates to the Qbic devices for hardware control over http (port 80). This is just how Qbic exposes the API, so we can't change that. If port 80 is not available, Qbic remote hardware management won't work. This is also the reason why Qbic hardware control is only available for PCs inside the same network. It's an additional security condition so that external devices don't access the Qbic API over http.
If we're talking QBIC and they want to be able to use the 1st tab in device control: they need to open port 80 + 443
If not (no qbic but standing kiosk; or they don't care about scanning qbic devices in device control): from a purely Cobundu perspective, only port 443 is needed. Yet generally PCs/devices all do have port 80 open for web communication from other apps/services, so we're not sure what impact closing it might have.
Small example: if currently you enter http://go.cobundu.com/ on your browser, you are automatically redirected to httpS://go.cobundu.com/ -> you asked for an insecure URL, but either the application or the browser automatically redirected you to the secure one.
On the other hand, if port 80 was disabled, your http request might just show an error "connection refused" on the browser - and not redirect anymore, because port 80 could not capture your request
