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.014 — Control VoIP Technologies

CMMC Level 2SPRS if unmet: -1LOW priority~4h to implement

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.

What SC.2.014 means in plain English

If you use internet-based phone systems like Microsoft Teams calling, Zoom Phone, or a VoIP service, you need to make sure those calls are encrypted and the system is configured securely. VoIP calls can be intercepted if they are not encrypted. Make sure your VoIP system uses encryption (most modern ones do by default), put VoIP traffic on its own VLAN if possible, and have a policy about discussing CUI over VoIP versus regular phone lines. Document what VoIP system you use and how it is secured.

The assessment question

“Do you monitor and control VoIP usage by ensuring VoIP traffic is encrypted, VoIP devices are on a separate network segment where feasible, and policies exist regarding discussion of CUI over VoIP?”

How to implement SC.2.014

  1. Inventory your VoIP systems: document what platform you use (Microsoft Teams, Zoom, RingCentral, on-premises PBX) and verify it supports encryption for voice traffic.
  2. Verify encryption is enabled: Microsoft Teams encrypts calls by default. For other providers, check their security settings and confirm TLS/SRTP encryption is active.
  3. If using on-premises VoIP phones, configure a separate VLAN for VoIP traffic to prevent snooping from the data network.
  4. Write a short policy statement: CUI may only be discussed over encrypted VoIP systems or traditional phone lines — not over unencrypted consumer apps.

Evidence your assessor will ask for

  • Inventory of VoIP systems in use with encryption status documented
  • VoIP platform configuration showing encryption is enabled (TLS/SRTP)
  • Network diagram showing VoIP VLAN segmentation (if applicable)
  • Written policy on VoIP usage and CUI discussion restrictions

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

SC.2.014 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.006

Deny Network Traffic by Default

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