Skip to main content

14.9 — Security Playbook, Interview & Production Checklist

1. Production security checklist​

Identity​

  • User lifecycle defined
  • Identity-provider mapping documented
  • Leaver process tested
  • Dormant users reviewed

Roles​

  • Least privilege applied
  • Global roles justified
  • Scoped roles used appropriately
  • Privileged roles reviewed
  • Separation of duties defined

Spaces​

  • Ownership defined
  • Data classification defined
  • Space membership reviewed
  • Cross-space sharing documented

Data​

  • DAC requirements identified
  • Authorization data owned
  • Positive and negative tests completed
  • Hierarchy authorization tested where applicable

Consumption​

  • Exposed objects reviewed
  • Consumer identities documented
  • End-to-end security tested
  • External access reviewed

Operations​

  • Audit requirements defined
  • Access review cadence defined
  • Break-glass process defined
  • Incident process defined

2. Security review questions​

Before production approval ask:

  1. Who can administer the tenant?
  2. Who can administer each space?
  3. Why does each modeler need write access?
  4. Which data is row-level restricted?
  5. What happens when a user leaves?
  6. Can an administrator bypass DAC?
  7. Which objects are exposed?
  8. How is access audited?
  9. How is emergency access controlled?
  10. How is security regression tested?

3. Interview preparation​

Question: What is the difference between global and scoped roles?​

Answer:

Global roles provide tenant-level privileges. Scoped roles apply privileges to selected spaces and can therefore provide differentiated authorization across spaces.

Question: What is Data Access Control?​

Answer:

It is a data-level security mechanism used to restrict which rows a user can access based on authorization criteria.

Question: Why are spaces important for security?​

Answer:

Spaces combine data residence, ownership and access boundaries. A user assigned to a space gains access according to the privileges associated with that assignment.

Question: Why is least privilege important?​

Answer:

It reduces blast radius, limits accidental changes and makes authorization auditable.

Question: How would you troubleshoot an authorization failure?​

Answer:

Start at identity, then role assignment, scope, space, privilege, object and data-level authorization. Collect evidence before changing permissions.

4. Architect answer framework​

For any security design question:

REQUIREMENT | v THREAT MODEL | v SECURITY BOUNDARY | v AUTHORIZATION CONTROL | v TEST | v AUDIT | v OPERATE

5. Final architect takeaway​

Enterprise Datasphere security is not a role-assignment exercise.

It is the controlled intersection of:

  • identity;
  • authorization;
  • space topology;
  • object privileges;
  • data-level security;
  • sharing;
  • consumption;
  • audit;
  • governance;
  • operations.

If you can explain every access path and every denial path, you are thinking like an enterprise architect.