Use when implement the CISA Zero Trust Maturity Model v2.0 across the
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill implementing-cisa-zero-trust-maturity-model --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Implementing Cisa Zero Trust Maturity Model?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-implementing-cisa-zero-trust-maturity-model)More formats (shields.io, HTML) on the badges page.
---
name: implementing-cisa-zero-trust-maturity-model
description: Use when implement the CISA Zero Trust Maturity Model v2.0 across the
five pillars of identity, devices, networks, applications, and data to achieve progressive
organizational zero trust maturity. Use when implementing the cisa zero trust maturity
model v2.0 across the.
domain: cybersecurity
subdomain: zero-trust-architecture
tags:
- zero-trust
- cisa
- maturity-model
- federal-compliance
- governance
- nist-800-207
- identity
- devices
- networks
- applications
- data-security
version: '1.0'
author: oyi77
license: Apache-2.0
nist_ai_rmf:
- GOVERN-1.1
- GOVERN-1.7
- MAP-1.1
- GOVERN-4.2
- MAP-2.3
nist_csf:
- PR.AA-01
- PR.AA-05
- PR.IR-01
- GV.PO-01
category: cybersecurity
---
# Implementing CISA Zero Trust Maturity Model
## Overview
The CISA Zero Trust Maturity Model (ZTMM) Version 2.0, released in April 2023, provides federal agencies and organizations with a structured roadmap for adopting zero trust architecture. The model defines five core pillars -- Identity, Devices, Networks, Applications & Workloads, and Data -- each progressing through four maturity stages: Traditional, Initial, Advanced, and Optimal. Three cross-cutting capabilities (Visibility and Analytics, Automation and Orchestration, and Governance) span all pillars. This skill covers assessment, gap analysis, and progressive implementation across all pillars and maturity levels.
## When to Use
**Trigger phrases:**
- "implementing cisa zero trust maturity model"
- "Implement the CISA Zero Trust Maturity Model v2"
- When deploying or configuring implementing cisa zero trust maturity model capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
## Prerequisites
- Familiarity with NIST SP 800-207 Zero Trust Architecture
- Understanding of federal cybersecurity mandates (EO 14028, OMB M-22-09)
- Access to organizational IT asset inventory and network architecture documentation
- Knowledge of identity and access management (IAM) fundamentals
- Understanding of network segmentation and microsegmentation concepts
## CISA ZTMM Five Pillars
This section covers cisa ztmm five pillars for implementing cisa zero trust maturity model.
- Ensure all prerequisites are met before proceeding
- Follow the documented workflow steps in sequence
- Record results and any anomalies encountered during this phase
### Pillar 1: Identity
Identity refers to attributes that uniquely describe an agency user or entity, including non-person entities (NPEs) such as service accounts and machine identities.
**Traditional Stage:**
- Password-based authentication
- Limited identity validation
- Manual provisioning and deprovisioning
**Initial Stage:**
- MFA deployed for privileged users
- Identity governance initiated
- Basic identity lifecycle management
**Advanced Stage:**
- Phishing-resistant MFA for all users (FIDO2/WebAuthn)
- Continuous identity validation
- Automated provisioning tied to HR systems
- Identity threat detection and response (ITDR)
**Optimal Stage:**
- Continuous, real-time identity verification
- Passwordless authentication across all systems
- AI-driven anomaly detection for identity behaviors
- Full integration of identity signals into access decisions
### Pillar 2: Devices
Devices include any hardware, software, or firmware asset that connects to a network -- servers, laptops, mobile phones, IoT devices, and network equipment.
**Traditional Stage:**
- Limited device inventory
- Basic endpoint protection (antivirus)
- No device compliance checks
**Initial Stage:**
- Comprehensive device inventory
- Endpoint Detection and Response (EDR) deployment
- Basic device health checks before network access
**Advanced Stage:**
- Real-time device posture assessment
- Automated compliance enforcement
- Device certificates for machine identity
- Vulnerability scanning integrated into access decisions
**Optimal Stage:**
- Continuous device trust scoring
- Automated remediation of non-compliant devices
- Full device lifecycle management integrated with zero trust policies
- Firmware integrity verification
### Pillar 3: Networks
Networks encompass all communications media including internal networks, wireless, and the internet.
**Traditional Stage:**
- Perimeter-based security (firewalls, VPNs)
- Flat internal networks
- Minimal east-west traffic inspection
**Initial Stage:**
- Initial network segmentation
- Encrypted DNS and internal traffic
- Basic network monitoring and logging
**Advanced Stage:**
- Microsegmentation of critical assets
- Software-defined networking (SDN) for dynamic policy enforcement
- Full TLS encryption for all internal communications
- Network Detection and Response (NDR)
**Optimal Stage:**
- Fully software-defined, policy-driven network
- Zero implicit trust zones
- AI-driven network anomaly detection
- Automated threat response integrated with network controls
### Pillar 4: Applications and Workloads
Applications and workloads include agency systems, programs, and services running on-premises, on mobile devices, and in cloud environments.
**Traditional Stage:**
- Perimeter-protected applications
- Manual vulnerability patching
- Limited application-level logging
**Initial Stage:**
- Application-level access controls
- Web Application Firewalls (WAF)
- Regular vulnerability scanning
- Application inventory established
**Advanced Stage:**
- Continuous integration of security testing (SAST/DAST)
- Application-aware microsegmentation
- API security gateways
- Immutable infrastructure patterns
**Optimal Stage:**
- Runtime application self-protection (RASP)
- Automated application security orchestration
- Full DevSecOps pipeline integration
- Zero-standing privileges for application access
### Pillar 5: Data
Data encompasses all structured and unstructured information, at rest, in transit, and in use.
**Traditional Stage:**
- Basic encryption for data at rest
- Limited data classification
- No data loss prevention
**Initial Stage:**
- Data classification scheme implemented
- DLP policies for sensitive data
- Encryption for data in transit (TLS 1.2+)
- Basic data inventory
**Advanced Stage:**
- Automated data classification
- Fine-grained data access controls
- Data activity monitoring
- Rights management for sensitive documents
**Optimal Stage:**
- Real-time data flow analytics
- AI-driven data classification and protection
- Automated response to data exfiltration attempts
- Full data lifecycle governance with zero trust principles
## Cross-Cutting Capabilities
This section covers cross-cutting capabilities for implementing cisa zero trust maturity model.
- Ensure all prerequisites are met before proceeding
- Follow the documented workflow steps in sequence
- Record results and any anomalies encountered during this phase
### Visibility and Analytics
```
Maturity Progression:
Traditional -> Manual log review, limited SIEM
Initial -> Centralized logging, basic SIEM correlation
Advanced -> UEBA, automated threat detection, data lake analytics
Optimal -> AI/ML-driven continuous monitoring, predictive analytics
```
### Automation and Orchestration
```
Maturity Progression:
Traditional -> Manual incident response, ad-hoc scripts
Initial -> Basic SOAR playbooks, automated alerting
Advanced -> Integrated SOAR with multi-pillar orchestration
Optimal -> Fully autonomous response, self-healing infrastructure
```
### Governance
```
Maturity Progression:
Traditional -> Ad-hoc policies, manual compliance checks
Initial -> Documented zero trust strategy, basic policy framework
Advanced -> Policy-as-code, continuous compliance monitoring
Optimal -> Dynamic policy engine, real-time governance decisions
```
## Implementation Process
1. **Scope the task** — define objectives, boundaries, and success criteria
2. **Gather information** — collect all necessary data and context before proceeding
3. **Execute the core workflow** — follow the domain-specific steps methodically
4. **Validate results** — verify outputs against expected outcomes or baselines
5. **Document findings** — record results, anomalies, and recommendations
### Phase 1: Assessment and Baseline
1. **Inventory all assets** across the five pillars
2. **Map current capabilities** to ZTMM maturity stages
3. **Conduct gap analysis** between current and target states
4. **Identify quick wins** that move from Traditional to Initial stage
5. **Document dependencies** between pillars
```python
# Example: CISA ZTMM Maturity Assessment Scoring
class ZTMMAssessment:
PILLARS = ['Identity', 'Devices', 'Networks', 'Applications', 'Data']
STAGES = ['Traditional', 'Initial', 'Advanced', 'Optimal']
CROSS_CUTTING = ['Visibility_Analytics', 'Automation_Orchestration', 'Governance']
def __init__(self):
self.scores = {}
def assess_pillar(self, pillar, capabilities):
"""
Assess a pillar against ZTMM criteria.
capabilities: dict of capability_name -> maturity_stage
"""
stage_values = {stage: i for i, stage in enumerate(self.STAGES)}
scores = [stage_values.get(stage, 0) for stage in capabilities.values()]
avg_score = sum(scores) / len(scores) if scores else 0
overall_stage = self.STAGES[int(avg_score)]
self.scores[pillar] = {
'capabilities': capabilities,
'average_score': avg_score,
'overall_stage': overall_stage
}
return self.scores[pillar]
def generate_roadmap(self):
"""Generate prioritized improvement roadmap."""
roadmap = []
for pillar, data in self.scores.items():
for capability, stage in data['capabilities'].items():
stage_idx = self.STAGES.index(stage)
if stage_idx < 3: # Not yet Optimal
next_stage = self.STAGES[stage_idx + 1]
roadmap.append({
'pillar': pillar,
'capability': capability,
'current': stage,
'target': next_stage,
'priority': 3 - stage_idx # Higher priority for lower maturity
})
return sorted(roadmap, key=lambda x: x['priority'], reverse=True)
```
### Phase 2: Identity Foundation
1. Deploy phishing-resistant MFA (FIDO2/WebAuthn)
2. Implement identity governance and administration (IGA)
3. Establish continuous identity verification
4. Integrate identity providers with all applications
5. Deploy identity threat detection and response
### Phase 3: Device Trust
1. Complete asset inventory with automated discovery
2. Deploy EDR across all endpoints
3. Implement device compliance checking
4. Establish device certificate infrastructure
5. Create device trust scoring mechanism
### Phase 4: Network Transformation
1. Implement network segmentation strategy
2. Deploy microsegmentation for critical assets
3. Enable encrypted DNS (DoH/DoT)
4. Enforce TLS 1.3 for all internal communications
5. Deploy NDR capabilities
### Phase 5: Application Security
1. Implement application-level access controls
2. Deploy WAF and API security gateways
3. Integrate security testing into CI/CD pipelines
4. Establish application inventory and classification
5. Implement runtime protection
### Phase 6: Data Protection
1. Implement data classification framework
2. Deploy DLP across endpoints and network
3. Enable data activity monitoring
4. Implement rights management
5. Establish data lifecycle governance
## Compliance Mapping
| CISA ZTMM Pillar | OMB M-22-09 Requirement | NIST 800-207 Section |
|---|---|---|
| Identity | MFA for agency staff | 3.1.1 |
| Devices | EDR for federal endpoints | 3.1.2 |
| Networks | Encrypt DNS traffic | 3.1.3 |
| Applications | Application security testing | 3.1.4 |
| Data | Data categorization | 3.1.5 |
## Metrics and KPIs
- **Identity Pillar**: Percentage of users with phishing-resistant MFA
- **Device Pillar**: Percentage of devices with real-time posture assessment
- **Network Pillar**: Percentage of network segments microsegmented
- **Application Pillar**: Percentage of applications with zero trust access controls
- **Data Pillar**: Percentage of sensitive data classified and protected
- **Overall**: ZTMM stage achieved per pillar (target: Advanced minimum)
## When NOT to Use
- You need to test the implementation (use performing-* skills)
- Task is about configuring existing tools (use configuring-* skills)
- You need to analyze security events (use analyzing-* skills)
- Task is about building detection rules (use building-* skills)
- You don't have access to the target environment
- Task requires vendor-specific expertise (consult vendor docs)
## Red Flags
- Performing actions without explicit written authorization from the asset owner
- Testing against production systems without a defined scope and rules of engagement
- Capturing traffic on networks without authorization or privacy considerations
- Leaving packet captures containing sensitive data unencrypted on disk
- Deploying inline blocking rules without testing for false positives first
## Verification
- All steps executed successfully against a test environment before production use
- Output documented with screenshots or logs demonstrating expected behavior
- Captures verified as complete with no dropped packets
- Detection rules tested against known-benign traffic for false positive rate
- Alert thresholds validated and tuned to reduce noise
## References
- [CISA Zero Trust Maturity Model v2.0](https://www.cisa.gov/zero-trust-maturity-model)
- [CISA ZTMM v2.0 PDF](https://www.cisa.gov/sites/default/files/2023-04/zero_trust_maturity_model_v2_508.pdf)
- [NIST SP 800-207 Zero Trust Architecture](https://csrc.nist.gov/publications/detail/sp/800-207/final)
- [OMB Memorandum M-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf)
- [NSA Zero Trust Pillars Guidance](https://media.defense.gov/2024/Apr/09/2003434442/-1/-1/0/CSI_DATA_PILLAR_ZT.PDF)
- [Microsoft Guidance for CISA ZTMM](https://www.microsoft.com/en-us/security/blog/2024/12/19/new-microsoft-guidance-for-the-cisa-zero-trust-maturity-model/)
## Process
1. Analyze the task requirements
2. Apply domain expertise
3. Verify output quality
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!