HoundShieldHoundShield
Products
Products by Industry

One firewall · every compliance framework · one deployment

TechnologySOC 2

Engineers pasting API keys & source into Copilot.

HealthcareHIPAA

Clinicians pasting PHI into AI for documentation.

DefenseCMMC L2

DoD contractors leaking CUI into proposal tools.

Legal & FinancePCI

Privileged client data shared with AI assistants.

Five EyesAUKUS

Allied suppliers navigating DISP & Essential 8.

GovernmentSoon

FedRAMP / FISMA — agency AI governance.

SOC 2 · HIPAA · CMMC L2 · 16 engines · <10msAll capabilities
Features
Core Capabilities

Inside the HoundShield firewall engine

AI Prompt Interception

Every LLM request inspected before it leaves the network.

16 Detection Engines

CUI, PII, IP, PHI, secrets, CAGE codes, clearances.

Immutable Audit Trail

SHA-256 tamper-evident logs. C3PAO-ready.

Live Threat Dashboard

Real-time blocked prompts, risk & posture.

Pricing
Pricing

All frameworks included in every plan

Free

Up to 1,000 prompts/mo

$0/mo
Pro

CMMC suite + AI gateway

$199/mo
Growth

PDF reports + C3PAO coord

$499/mo
Enterprise

On-prem · air-gapped

$999/mo
Compare all plans
Partners
Partner Program

Build & grow with HoundShield

RPO / MSP Referral

Co-brand the $499 report · keep the margin.

MSP / Agency

40% per report · 20% recurring · white-label.

Integrations

Drop-in proxy for ChatGPT, Copilot, Claude.

Docs
Documentation

Live in under 5 minutes · no code changes

Quickstart

One URL change → full compliance.

API Reference

Gateway, classifier & audit endpoints.

FAQ

Searchable answers — pricing, HIPAA, CUI.

16 engines · <10ms scan
Sign inStart free

NIST 800-171 Controls · System and Communications Protection

SC.2.006 — Deny Network Traffic by Default

CMMC Level 2SPRS if unmet: -3HIGH priority~6h to implement

Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

What SC.2.006 means in plain English

Your firewall should start by blocking everything and then you open up only the specific traffic you need. Do not start with "allow all" and try to block the bad stuff — you will miss something. For example, allow outbound web traffic on ports 80 and 443, allow your VPN port, allow email ports, and block everything else. This applies to both your network firewall and the Windows firewall on each machine. If you cannot explain why a port is open, close it.

The assessment question

“Are your firewalls (network and host-based) configured with a default-deny policy that blocks all traffic except for specifically authorized and documented exceptions?”

How to implement SC.2.006

  1. On your network firewall (pfSense, Ubiquiti, etc.), set the default rule on every interface to DENY ALL. Then add specific allow rules above it for traffic that is needed.
  2. Document each firewall allow rule with a business justification: "Allow outbound TCP 443 from internal VLAN to any — required for web browsing and cloud services."
  3. On Windows workstations, verify Windows Defender Firewall is set to block inbound connections by default: Windows Security > Firewall & Network Protection > verify all profiles show "Firewall is on" and inbound connections are blocked.
  4. Audit your firewall rules quarterly: remove any rules that no longer have a valid business need. Stale rules are security holes.
  5. Test your deny-default configuration by attempting to connect on a port you have not explicitly allowed — it should be blocked.

Evidence your assessor will ask for

  • Firewall configuration showing default-deny rule as the last rule on each interface
  • Documented firewall rule set with business justification for each allow rule
  • Windows Defender Firewall configuration screenshot showing inbound blocked by default
  • Quarterly firewall rule audit records
  • Port scan test results confirming unauthorized ports are blocked

Does AI prompt monitoring help with this control? Honestly, no.

SC.2.006 is met through the remediation steps above, not through AI traffic controls — an AI prompt firewall neither satisfies nor substitutes for it. We map AI monitoring only to the controls it genuinely evidences (flow control, boundary protection, audit, and incident support); for the full picture of where it does help, see the mapping guide linked below.

Full mapping: which 800-171 controls AI prompt monitoring evidences →

More System and Communications Protection controls

SC.1.001

Monitor and Protect Communications at Boundaries

SC.1.005

Implement Subnetworks for Public Components

SC.2.002

Employ Effective Security Architecture

SC.2.003

Separate User and System Management Functionality

SC.2.004

Prevent Unauthorized Info Transfer via Shared Resources

SC.2.007

Prevent Remote Device Split Tunneling

Score yourself against all 110 controls

The free ShieldReady assessment walks every NIST 800-171 requirement, computes your SPRS score, and shows exactly which gaps cost the most points.

Start the free assessment $499 AI risk assessment
HoundShieldHoundShield

Local-only AI compliance firewall for CMMC Level 2, HIPAA & SOC 2. Prompt content never leaves your network.

CMMC LVL 2HIPAASOC 2NIST 800-171DFARS 7012
Product
FeaturesHow it worksPricingCompareDashboardChangelog
Compliance
CMMC Level 2HIPAASOC 2NIST 800-171DFARS 7012
Company
PartnersDocumentationFAQContact salesAboutSecurity
© 2026 HoundShield. All rights reserved. · Privacy · Termshoundshield.com · local-only · zero data exfiltration