<!-- Copyright (c) 2026 defconxt. All rights reserved. -->
<!-- Licensed under AGPL-3.0 — see LICENSE file for details. -->
<!-- NERF is a trademark of defconxt. -->

---
id: compliance-3ea749ad
title: Monitoring Zero Trust Compliance
description: >
  Track and report on zero trust maturity metrics
  using automated analysis and remediation techniques.
mode: BLUE
tags:
  - zero-trust
  - compliance
  - monitoring
  - metrics
metadata:
  mitre-attack: ["T1078"]
---

# Monitoring Zero Trust Compliance

> **`[MODE: BLUE]`** — Track and report on zero trust maturity metrics.

## Quick Reference

```bash
# Run the monitoring-zero-trust-compliance agent
node scripts/agent.js --target <TARGET> --mode assess

# Generate a report
node scripts/agent.js --target <TARGET> --mode report --output report.json

# Analyze with verbose output
node scripts/agent.js --target <TARGET> --mode verify --verbose
```

## Overview

Monitoring Zero Trust Compliance is a critical zero trust technique that addresses
common security risks in modern environments. This skill provides automated
tooling and structured methodology for practitioners to track and report on zero trust maturity metrics.

### Key Concepts

- **Identification**: Detect relevant indicators and patterns
- **Analysis**: Evaluate severity and business impact
- **Remediation**: Apply targeted fixes with verification
- **Monitoring**: Establish ongoing detection coverage

## Workflow

### Phase 1 — Discovery

Enumerate the target environment and identify the attack surface
relevant to monitoring zero trust compliance.

```bash
node scripts/agent.js --target <TARGET> --mode assess --phase discovery
```

**Expected output**: JSON inventory of identified targets and initial findings.

### Phase 2 — Analysis

Perform deep analysis of discovered items to determine risk level
and exploitability.

```bash
node scripts/agent.js --target <TARGET> --mode verify --phase analysis
```

**Expected output**: Categorized findings with severity ratings.

### Phase 3 — Remediation

Apply recommended fixes and generate compliance evidence.

```bash
node scripts/agent.js --target <TARGET> --mode report --phase remediation
```

**Expected output**: Remediation report with before/after comparison.

## Verification

### Automated Verification

```bash
# Verify remediation was applied correctly
node scripts/agent.js --target <TARGET> --mode assess --verify

# Run regression check
node scripts/agent.js --target <TARGET> --mode verify --regression
```

### Manual Verification Checklist

- [ ] All identified issues have been addressed
- [ ] Remediation does not break functionality
- [ ] Detection rules are deployed and tested
- [ ] Documentation is updated with findings
- [ ] Stakeholders have been notified of changes

### Validation Criteria

| Check | Expected Result | Tool |
|-------|----------------|------|
| Configuration audit | No critical findings | `agent.js --mode assess` |
| Regression test | All tests pass | `agent.js --verify` |
| Detection coverage | Rules firing on test data | SIEM validation |

## Detection Opportunities

When operating in BLUE mode, consider these detection angles:

- Monitor for configuration changes related to monitoring zero trust compliance
- Alert on anomalous patterns that indicate exploitation attempts
- Correlate findings with threat intelligence feeds
- Baseline normal behavior to identify deviations

```yaml
title: Zero Trust Compliance Detection
id: 812068a9-09e8-4ad9-a39e-44ca062e2f62
status: experimental
description: Detects suspicious activity related to monitoring zero trust compliance techniques in zero trust context
logsource:
  category: authentication
  product: windows
detection:
  selection:
    EventType: authentication
    Status: failure
  condition: selection
level: medium
tags:
  - attack.t1078
  - attack.lateral_movement
falsepositives:
  - Zero trust policy engine evaluating routine access requests
```

## References

- [MITRE ATT&CK](https://attack.mitre.org/) — Technique mapping
- [CIS Benchmarks](https://www.cisecurity.org/cis-benchmarks) — Hardening standards
- [NIST SP 800-53](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final) — Security controls
- [OWASP](https://owasp.org/) — Web application security guidance
- See also: `references/api-reference.md` for API documentation
