Skip to content
Back to skills

Network Communications Deny By Default

ASecurity

Network Communications – Deny by Default – Allow by Exception

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
securitygoawsgcpazuregitsecuritydocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill network-communications-deny-by-default --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Network Communications Deny By Default?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Network Communications Deny By Default
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-network-communications-deny-by-default/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-network-communications-deny-by-default)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "Network Communications – Deny by Default – Allow by Exception (03.13.06)_network-communications-deny-by-default-allow-by-exception"
description: "Network Communications – Deny by Default – Allow by Exception"
category: "configuration"
version: "3.0"
author: "cyberstrike-official"
tags:
  - nist
  - sp800-171
  - rev3
  - network communications – deny by default – allow by exception (03-13-06)
  - family-03.13
  - cui-protection
  - cmmc
tech_stack:
  - aws
  - azure
  - gcp
  - linux
  - windows
  - network
cwe_ids:
  - CWE-311
chains_with: []
prerequisites: []
severity_boost: {}
---

# Network Communications – Deny by Default – Allow by Exception (03.13.06) Network Communications – Deny by Default – Allow by Exception

## High-Level Description

**Family:** System and Communications Protection
**Framework:** NIST SP 800-171 Rev 3
**Applicability:** Systems processing, storing, or transmitting CUI

Network Communications – Deny by Default – Allow by Exception

## What to Check

- [ ] Verify Network Communications – Deny by Default – Allow by Exception (03.13.06) Network Communications – Deny by Default – Allow by Exception is implemented for CUI systems
- [ ] Review SSP documentation for Network Communications – Deny by Default – Allow by Exception (03.13.06)
- [ ] Validate CMMC Level 2 assessment objective for Network Communications – Deny by Default – Allow by Exception (03.13.06)
- [ ] Confirm POA&M addresses any gaps for Network Communications – Deny by Default – Allow by Exception (03.13.06)

## How to Test

### Step 1: Review System Security Plan

Examine the SSP for Network Communications – Deny by Default – Allow by Exception (03.13.06) implementation description and responsible parties.

### Step 2: Assess Implementation

```
# Verify security controls protecting CUI
# Check access controls, encryption, monitoring as applicable

# For Linux systems:
ls -la /etc/security/ 2>/dev/null
grep -r "CUI\|controlled" /etc/security/ 2>/dev/null

# For cloud:
# Use cloud-audit-mcp tools to assess posture
```

### Step 3: CMMC Assessment Validation

Verify this requirement passes CMMC Level 2 assessment methodology per SP 800-171A Rev 3.

## Tools

| Tool            | Purpose                      | Usage                  |
| --------------- | ---------------------------- | ---------------------- |
| cloud-audit-mcp | Assess cloud CUI environment | `cloud_audit_*` tools  |
| Manual Review   | SSP and POA&M review         | Documentation analysis |

## Remediation Guide

### Requirement Statement

Implement Network Communications – Deny by Default – Allow by Exception per NIST SP 800-171 Rev 3.

### Supplemental Guidance

This requirement applies to inbound and outbound network communications traffic at the system boundary and at identified points within the system. A deny-all, allow-by-exception network communications traffic policy ensures that only essential and approved connections are allowed.

## Risk Assessment

| Finding                                                                                                                                                | Severity | Impact                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ----------------------------------------------------- |
| Network Communications – Deny by Default – Allow by Exception (03.13.06) Network Communications – Deny by Default – Allow by Exception not implemented | High     | CUI Protection - System and Communications Protection |
| Network Communications – Deny by Default – Allow by Exception (03.13.06) partially implemented (POA&M)                                                 | Medium   | CMMC certification risk                               |

## CWE Categories

| CWE ID  | Title                                |
| ------- | ------------------------------------ |
| CWE-311 | Missing Encryption of Sensitive Data |

## References

- [NIST SP 800-171 Rev 3](https://csrc.nist.gov/pubs/sp/800/171/r3/final)
- [NIST SP 800-171A Rev 3 (Assessment)](https://csrc.nist.gov/pubs/sp/800/171/a/r3/final)
- [CMMC Model Overview](https://www.acq.osd.mil/cmmc/)
- [NIST OSCAL Content](https://github.com/usnistgov/oscal-content)

## Checklist

- [ ] SSP documents Network Communications – Deny by Default – Allow by Exception (03.13.06) implementation
- [ ] Evidence of operating effectiveness collected
- [ ] POA&M addresses any gaps
- [ ] CMMC assessment objective met
- [ ] Continuous monitoring active

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.