Enterprise SaaS tenant isolation
archimatev1/01 Views
/02 About
Define tenant identity, provisioning, enforcement, data separation, key custody and cross-tenant auditing
Purpose: Define tenant identity, provisioning, enforcement, data separation, key custody and cross-tenant auditing. Reading the diagrams: Architecture landscape contains the complete semantic model. Governance and delivery isolates organizational decisions and enabling services. Delivery and assurance isolates runtime capabilities, controls, stewardship and evidence. Adoption: this is a reference architecture, not proof of implementation or regulatory compliance. Replace generic roles with actual owners and solutions. Record decisions, scope, constraints, interfaces, data classification, implementation status and evidence. Verify all applicable policies and control objectives against the current official source. Source and attribution: original Arq interpretation informed by https://cloudsecurityalliance.org/artifacts/security-guidance-v5/. No official source artwork is reproduced, and no endorsement or certification by the source publisher is implied.
Published by Lattix · 12 elements · 13 relationships · validated on publish
/03 Contents
- Business Actor
- Tenant admin
- Application Component
- Tenant provisioning, Identity broker, Tenant-aware routing, Policy enforcement, Shared execution, Tenant key management, Isolation testing, Tenant audit export
- Data Store
- Tenant inventory, Tenant-partitioned information
- Role
- Platform security owner