CLOUD-DIGITAL-LEADER · Question #42
An organization has had a data leak scare because one employee made a sensitive Cloud Storage bucket available to the public. Given the nature of the company's business, it is understood that there…
The correct answer is B. Set an organizational policy constraint to restrict bucket access set to the public. The straightforward way to set it is using Organizational Policy constraint. Any attempts to change the organizational setting will be rejected for any project and resource. https://cloud.google.com/resource-manager/docs/organization-policy/overview…
Question
An organization has had a data leak scare because one employee made a sensitive Cloud Storage bucket available to the public. Given the nature of the company's business, it is understood that there is never any reason to give the public direct access to any file. The security head wants to ensure that such an event never occurs again. How can you ensure this?
Options
- ARemove Edit access rights of all Cloud Storage buckets so that no user can make any edits.
- BSet an organizational policy constraint to restrict bucket access set to the public.
- CUse Cloud Scheduler to run a job at a specified interval to scan buckets. Any public permissions
- DWrite Cloud Functions code connected to Cloud Storage. Any changes will be notified to the
How the community answered
(30 responses)- A3% (1)
- B70% (21)
- C17% (5)
- D10% (3)
Explanation
The straightforward way to set it is using Organizational Policy constraint. Any attempts to change the organizational setting will be rejected for any project and resource. https://cloud.google.com/resource-manager/docs/organization-policy/overview https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints
Topics
Community Discussion
No community discussion yet for this question.