This website uses cookies to ensure you get the best experience.
Learn more.
An organization wants supported visibility for another-cloud workloads in Defender for Cloud. What should the connector design enforce?
Published
- Ignore which account the connector targets
- The documented trust, permissions, scope, and onboarding requirements
- Public disclosure of the other cloud's root credential
- Assume a resource name creates the cross-cloud trust
Comments — 0
Sign in to comment