21.8 Enterprise Security Architecture
Security architecture should be layered.
Security layers
- Identity
- Tenant access
- Space access
- Object privileges
- Data access controls
- Consumption authorization
- Audit and operational monitoring
Least privilege
A developer should not receive production administration rights merely because they can build models.
Separate:
Build | Approve | Deploy | Operate | Audit
where organizational controls require it.
Sensitive data
Classify data before modeling:
- public
- internal
- confidential
- restricted
Then map classifications to roles, access controls, sharing rules and monitoring.
Row-level security
Use data access controls where different users need different subsets of the same governed asset.
Security architecture test
For every exposed asset answer:
- who can discover it?
- who can query it?
- who can modify it?
- who can share it?
- who can administer the security rule?
- how is access audited?
Architect rule
Security must be designed into the data contract, not added after the dashboard is built.