Skip to content
Back to skills

SC 46 Cross Domain Policy Enforcement

ASecurity

Implement a policy enforcement mechanism [organization-defined] between the physical and/or network interfaces for the connecting security domains.

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 3, 2026
securitygoawsgcpazuresecuritydocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill SC-46_cross-domain-policy-enforcement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of SC 46 Cross Domain Policy Enforcement?

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

Security grade badge for SC 46 Cross Domain Policy Enforcement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-sc-46-cross-domain-policy-enforcement/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-sc-46-cross-domain-policy-enforcement)

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: "SC-46_cross-domain-policy-enforcement"
description: "Implement a policy enforcement mechanism [organization-defined] between the physical and/or network interfaces for the connecting security domains."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
  - nist
  - sp800-53
  - rev5
  - sc-46
  - sc
tech_stack:
  - aws
  - azure
  - gcp
  - linux
  - windows
  - network
cwe_ids:
  - CWE-311
chains_with:
  - AC-4
  - SC-7
prerequisites: []
severity_boost:
  AC-4: "Chain with AC-4 for comprehensive security coverage"
  SC-7: "Chain with SC-7 for comprehensive security coverage"
---

# SC-46 Cross Domain Policy Enforcement

## High-Level Description

**Family:** System and Communications Protection (SC)
**Framework:** NIST SP 800-53 Rev 5

For logical policy enforcement mechanisms, organizations avoid creating a logical path between interfaces to prevent the ability to bypass the policy enforcement mechanism. For physical policy enforcement mechanisms, the robustness of physical isolation afforded by the physical implementation of policy enforcement to preclude the presence of logical covert channels penetrating the security domain may be needed. Contact [ncdsmo@nsa.gov](mailto:ncdsmo@nsa.gov) for more information.

## What to Check

- [ ] Verify SC-46 Cross Domain Policy Enforcement is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for SC-46

## How to Test

### Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SC-46 implementation details. Verify the organization has documented how this control is satisfied.

### Step 2: Validate Implementation

```
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
```

### Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

## Tools

| Tool            | Purpose                               | Usage                                |
| --------------- | ------------------------------------- | ------------------------------------ |
| cloud-audit-mcp | Check encryption and network controls | `cloud_audit_encryption`             |
| nmap            | Network scanning                      | `nmap -sV --script ssl-enum-ciphers` |

## Remediation Guide

### Control Statement

Implement a policy enforcement mechanism [organization-defined] between the physical and/or network interfaces for the connecting security domains.

### Implementation Guidance

For logical policy enforcement mechanisms, organizations avoid creating a logical path between interfaces to prevent the ability to bypass the policy enforcement mechanism. For physical policy enforcement mechanisms, the robustness of physical isolation afforded by the physical implementation of policy enforcement to preclude the presence of logical covert channels penetrating the security domain may be needed. Contact [ncdsmo@nsa.gov](mailto:ncdsmo@nsa.gov) for more information.

## Risk Assessment

| Finding                                               | Severity | Impact                                          |
| ----------------------------------------------------- | -------- | ----------------------------------------------- |
| SC-46 Cross Domain Policy Enforcement not implemented | High     | System and Communications Protection            |
| SC-46 partially implemented                           | Medium   | Incomplete System and Communications Protection |

## CWE Categories

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

## References

- [NIST SP 800-53 Rev 5 - SC-46](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=sc-46)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)

## Checklist

- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (AC-4, SC-7) reviewed

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.