Quizlet #8 Flashcards
defense-in-depth process for storing data in Google Cloud
- Data is broken into many pieces in memory. 2. These pieces, or “chunks”, are encrypted with their own data encryption key or ‘DEK’. 3. These DEKs are then encrypted a second time with key encryption key or ‘KEK’. 4. Encrypted chunks and wrapped KEKs are distributed across Google’s infrastructure
Identity layer protection
Google Cloud operates a zero-trust model. This means that every user and every machine that tries to access data or services must strongly authenticate identity at each stage for each file
Network layer protection
Encryption in transit protects data as it moves across a network. Multiple layers of defense are in place to help protect customers against network attacks, like DDoS attacks
Operations layer of protection
Operations layer of protection A global operations team of more than 900 security experts monitor the system 24 hours a day, 365 days a year. Their role is to detect attacks and other issues and to respond to them
Front end user access
None of the 4 (view logs, modify settings, modify users, or modify applications)
Manager access
Modify users and applications
Admin user access All 4 (view logs, modify settings, modify users, or modify applications)
Admin user access All 4 (view logs, modify settings, modify users, or modify applications)
Who of IAM policy
A Google account, a Google group, a service account, or a Google Workspace or Cloud Identity domain
What of IAM policy
If you’re a viewer on a given resource, you can examine it, but not change its state. If you’re an editor, you can do everything a viewer can do plus change its state. And if you’re an owner, you can do everything an editor can do plus manage roles and permissions on the resource
“least-privilege” model
Each person in your organization is given the minimal amount of privilege needed to do their job
Resource Hierarchy
The way your IT team can organize your business’ Google Cloud environment and how that service structure maps to your organization’s actual structure.
Google Cloud Roles
Primitive, Predefined, Custom
Primitave Roles
Broad roles, such as Owner, Editor, or Viewer
Predefined Roles
Predefined Roles Collection of permissions, such as roles for Compute Engine only.
Custom Roles
Roles created specifically for each person or sets of persons, usually mapped by job function for group