Request for clarification regarding Nebula security and privileged support access
Guru Member
Dear Zyxel Support Team,
We currently use three Zyxel devices: a firewall, an access point, and a 5G FWA device. Due to licensing considerations, only the firewall is registered with and managed through the Nebula platform.
During previous support cases, after providing our Nebula organization and site details, Zyxel Support was able—following our authorization—to access the firewall configuration using a support account. In some cases, the support engineer then created an additional local administrator account on the firewall to perform further troubleshooting.
Given the increasing number and sophistication of cyberattacks, we would like to better understand how Zyxel protects the Nebula platform and manages privileged support access.
Could you please provide a written technical response addressing the following points?
- Support authorization
Does Zyxel Support always require an explicit and active invitation from one of our administrators before accessing or modifying our Nebula organization? Are there any emergency, recovery, or alternative privileged-access mechanisms that can be used without prior customer approval? If so, how are they controlled and communicated to the customer? - Protection of privileged support accounts
Are MFA, named individual accounts, least-privilege access, time-limited permissions, and approval workflows mandatory for Zyxel employees, partners, contractors, and other third parties with privileged access? - Local firewall accounts
When a support engineer creates a local administrator account on the firewall, is that account automatically time-limited? Is it automatically removed when the support case is closed or when Nebula support access is revoked? Are all associated sessions, credentials, API tokens, and keys also invalidated? - Access duration and revocation
What is the default duration of Nebula support access? Can we immediately revoke it, terminate active support sessions, and verify that no additional access remains possible?
Once the support activity or ticket has been completed, is support access automatically disabled immediately, or does it remain enabled until the configured expiration date? - Does the Zyxel support engineer manually revoke their access at the end of the intervention, or is the customer responsible for disabling it? Is closing the support ticket technically linked to the revocation of support access?
- If access remains enabled, can Zyxel Support continue to access the organization until the configured expiration date without requesting further authorization? Are customers notified when support access is enabled, used, extended, or revoked?
- Can we immediately revoke support access and terminate any already active support sessions?
- How long are these logs retained, can they be exported to an external SIEM or syslog server, and do any of these capabilities require an additional licence?
- who accessed the organization or device;
- when the access occurred;
- which configuration changes were made;
- which administrator accounts were created, modified, or deleted;
- whether the activity originated from Nebula, Zyxel Support, a partner, or direct local access?
- Nebula platform security
What technical measures protect Nebula against account compromise, attacks on its APIs, privilege escalation, supply-chain attacks, and cross-tenant access? How is separation between different customers and organizations enforced? - Independent security assessments
Which independent certifications, penetration tests, or third-party security assessments specifically cover the Nebula platform and its privileged-access processes, rather than only the underlying AWS infrastructure? Can the relevant reports or summaries be shared with customers? - Incident response and customer notification
If Nebula or a privileged Zyxel account were compromised, how and within what timeframe would affected customers be notified? What measures are available to immediately block remote management and isolate the firewall from Nebula while preserving its configuration and normal network operation? - Security advisories
Where does Zyxel publish security advisories specifically concerning the Nebula cloud platform, as distinct from vulnerabilities affecting individual device firmware?
We would also appreciate a list of Zyxel’s recommended configuration settings and operational procedures for minimizing privileged access to our organization and firewall.
Our intention is not to question the usefulness of remote support, but to ensure that every privileged access path is explicitly authorized, temporary, auditable, and fully revocable.
Kind regards
All Replies
-
Hi @Maverick87
Zyxel Support can access your Nebula organization only after your administrator enables Support Access (Help > Support Request), and there is no other method for Zyxel Support to enable it. Everyone with access to the support accounts must pass multi-factor authentication to log in. The default Support Access duration is 21 days, and access closes automatically when it expires. After that, the organization no longer appears in the support account’s organization list unless you enable Support Access again.
You can disable Support Access at any time, and support loses access to your organization immediately. Closing a support ticket does not disable it, so access ends when you turn it off or when it expires. A local administrator account created on a device has no automatic timeout and is not removed when Nebula Support Access is disabled. You can delete it at any time, and we recommend reviewing and deleting it once the case is finished.
Zyxel has a dedicated security team (PSIRT) that manages security issues across all of our products. You can find our PSIRT policy on our website, and we publish security advisories there as well.
Zyxel Melen0 -
Hi @Zyxel_Melen,
Thank you for the clarification. Could you also confirm whether disabling Support Access immediately terminates any already active support sessions?Are all actions performed through Zyxel support accounts recorded in a customer-accessible audit log, including the individual operator identity, login time and configuration changes?
Finally, when a local administrator account is created during support, is the customer explicitly notified of its username and reminded to remove it when the case is closed?
Thank you
0
Categories
- All Categories
- 442 Beta Program
- 3.1K Nebula
- 244 Nebula Ideas
- 6.9K Security
- 805 USG FLEX H Series
- 392 Security Ideas
- 1.8K Switch
- 88 Switch Ideas
- 1.5K Wireless
- 60 Wireless Ideas
- 7.3K Consumer Product
- 330 Service & License
- 540 News and Release
- 106 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 5.5K FAQ
- 34 Documents
- 89 About Community
- 124 Security Highlight
Zyxel Employee