Incident-Affected Tenant Entity
Jump to navigation
Jump to search
A Incident-Affected Tenant Entity is a multi-tenant SaaS customer entity that experiences service disruption (during multi-tenant incidents).
- AKA: Affected Tenant, Impacted Customer Organization, Disrupted Tenant Entity.
- Context:
- It can typically experience Service Degradation through tenant service interruption and tenant functionality loss.
- It can typically suffer Configuration Loss via tenant setting override and tenant preference reset.
- It can typically face Security Exposure from tenant authentication bypass and tenant access vulnerability.
- It can typically require Incident Notification through tenant communication channels and tenant contact points.
- It can typically need Recovery Action via tenant configuration restoration and tenant service re-enablement.
- ...
- It can often have Business Impact including tenant operational disruption and tenant revenue loss.
- It can often experience Compliance Issue under tenant regulatory requirements and tenant contractual obligations.
- It can often require Compensation Consideration based on tenant SLA violation and tenant service credit.
- It can often demand Root Cause Explanation through tenant incident report and tenant management briefing.
- ...
- It can range from being a Minimally Tenant-Affected Entity to being a Severely Tenant-Affected Entity, depending on its tenant impact level.
- It can range from being a Single Tenant-Affected Entity to being a Multiple Tenant-Affected Entity, depending on its tenant incident scope.
- It can range from being a Free-Tier Tenant-Affected Entity to being a Enterprise Tenant-Affected Entity, depending on its tenant subscription level.
- It can range from being a Direct Tenant-Affected Entity to being a Indirect Tenant-Affected Entity, depending on its tenant impact pathway.
- It can range from being a Temporarily Tenant-Affected Entity to being a Persistently Tenant-Affected Entity, depending on its tenant impact duration.
- ...
- It can be identified through Tenant Impact Analysis using tenant monitoring systems.
- It can be tracked in Incident Management System for tenant incident correlation.
- It can be prioritized via Tenant Severity Matrix based on tenant business criticality.
- It can be supported through Customer Success Team with tenant recovery assistance.
- It can be compensated via Service Credit System for tenant SLA breach.
- ...
- Example(s):
- Enterprise Tenant-Affected Entitys, such as:
- Regional Tenant-Affected Entitys, such as:
- Japanese Corporation Tenant (e.g., 日鉄ソリューションズ) with SSO disablement.
- European Bank Tenant facing GDPR compliance breach.
- Australian Government Tenant with security setting override.
- Industry-Specific Tenant-Affected Entitys, such as:
- Size-Based Tenant-Affected Entitys, such as:
- SMB Tenant Entity with limited IT resources for recovery.
- Startup Tenant Entity experiencing growth plan disruption.
- Non-Profit Tenant Entity facing donor system outage.
- ...
- Counter-Example(s):
- Unaffected Tenant Entity, which maintains normal operation during platform incidents.
- Platform Provider Entity, which causes tenant incidents rather than experiencing them.
- Third-Party Integration Partner, which may be impacted differently than direct tenants.
- See: Multi-Tenant Architecture, SaaS Customer, Tenant Management System, Customer Impact Assessment, Service Level Agreement, Incident Communication Plan, Customer Success Management, Tenant Isolation, Platform Incident Management, Customer Compensation Policy.