# How do I check whether vendor-operated BYOC fits our security model?

Canonical page: https://launchinyourcloud.com/questions/vendor-operated-byoc/

Review the vendor’s identities, permissions, data access and control-plane dependencies. Check how access is logged, restricted and revoked, and treat support access separately from installation and routine operations. Verify this for the exact deployment rather than accepting a BYOC label.

Answer page: https://launchinyourcloud.com/questions/vendor-operated-byoc/
Answer reviewed: 2026-11-21

- [Read the deployment-model guide](/guide/deployment-models/)
- [Define shared responsibility](/glossary/#shared-responsibility)
- [Use the IAM review checklist](/downloads/iam-review-checklist.md)


## Review access by task

Installation, routine operation and emergency support can require different identities and approvals. For each, identify the trusted party, allowed actions, accessible data, logging and revocation process. Ask whether the vendor’s management plane holds credentials or can change network and identity settings.

## Test loss of the vendor connection

Use an agreed trial to establish what happens when the management plane is unavailable or access is revoked. Can the workload continue? Who can restore it, rotate credentials or apply a security fix? Keep customer emergency access independent of the vendor where the documented architecture permits it.

Confirm support access separately from ordinary operations, including approval, duration and audit evidence. A BYOC data plane can fit within a customer account while still depending on external management. Your security review needs to cover both that dependency and the privileges it introduces.

