Administration, Security and Operations
Administration, Security and Operations covers the controls that keep the cloud management platform itself trustworthy: identity, roles, auditability, data handling, and operational hygiene.
Identity and access
- Use role-based access control to give administrators only the scope they need. Typical separations are full administrator, operator, monitor, and installer/onboarding roles.
- Prefer SSO with MFA for administrative access; local accounts should be limited and reviewed.
- API tokens and integrations must be scoped and rotated; a leaked token can change configuration at machine speed.
Audit and data protection
- Audit logs record administrative actions. They are evidence for change control and incident review.
- Know where tenant data is hosted and what retention applies; regulated data may require a specific region or contract.
- Back up or export critical configuration and keep firmware and configuration baselines under change control.
Operational security
- Disable unused management services and enforce secure protocols (HTTPS, SSH) for device management.
- Review firmware advisories and maintain a tested upgrade cadence.
- Separate guest, corporate, and IoT traffic with VLANs and policy; do not rely on SSID naming for security.
Worked example
A contractor needs to onboard switches for two weeks but must not change SSIDs or view client data. Reasoning: do not give administrator rights. Create or assign a limited role that permits device onboarding and inventory only, scope it to the relevant Cloud Config Group if the platform supports scoping, require SSO/MFA, and set a review date to remove access. Check the audit log afterward to confirm what the contractor changed.
Traps that cost marks
- Granting full admin because creating a custom role seems slower.
- Sharing a single local admin account, which destroys auditability.
- Ignoring data residency and retention when selecting a cloud region.
- Leaving API tokens with broad scope and no expiration.
- Assuming onboarding access cannot affect production; inventory changes can.