Last reviewed: April 9, 2025
📘 In this article:
System Criticality
Every System in ArchTechLytics is classified by its criticality level — a declaration of how important the system is to your business or mission.
This allows ArchTechLytics to:
- Apply stricter evaluation rules for high-criticality systems
- Tailor recommendations based on tolerance for failure
- Highlight areas that require urgent remediation
🎯 Available Criticality Levels
You can choose from:
| Criticality | Description |
|---|---|
| Life-Critical | System failure may result in harm to life, safety, or essential services |
| Mission-Critical | Directly tied to your organization’s mission, outcomes, or continuity |
| Business-Critical | Impacts revenue, customers, or core internal processes |
| Operational-Critical | Supports business operations but has some tolerance for failure |
| Non-Critical | Dev/test, sandboxes, low-impact workloads |
🧠 Why It’s Powerful
System Criticality enables contextual scoring. For example:
- A VM without backup in a Non-Critical system? Informational warning.
- That same VM in a Life-Critical system? Severe scoring penalty.
➡️ See how scoring adapts to criticality