Confirming this is issue does not manifest when deploying the mobile-security-service locally to a cluster with the operator. When I originally logged this issue, it was when I ran the UI locally, so will just double-check that now too.