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.016 — Protect Confidentiality of CUI at Rest

CMMC Level 2SPRS if unmet: -5CRITICAL priority~8h to implement

Protect the confidentiality of CUI at rest.

What SC.2.016 means in plain English

CUI sitting on a hard drive, USB stick, or file server must be encrypted even when nobody is actively using it. If someone steals a laptop, the encrypted hard drive is useless to them without the password. Use BitLocker to encrypt all hard drives on computers that store CUI. For removable media like USB drives, use BitLocker To Go. For cloud storage, ensure your provider encrypts data at rest (Microsoft 365 GCC does this by default). A stolen, unencrypted laptop with CUI is a reportable incident.

The assessment question

“Is CUI encrypted at rest on all storage media including workstation hard drives, server storage, removable media, and cloud storage using FIPS-validated encryption such as BitLocker?”

How to implement SC.2.016

  1. Enable BitLocker on all Windows workstations that store or process CUI: Control Panel > BitLocker Drive Encryption > Turn on BitLocker. Use AES-256 encryption.
  2. For USB drives used with CUI, enable BitLocker To Go: insert the USB, right-click in File Explorer > Turn on BitLocker. Require a password to unlock.
  3. Configure a Group Policy to require BitLocker on all fixed and removable drives: Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption.
  4. Verify cloud storage encryption: confirm your Microsoft 365 GCC or cloud provider encrypts data at rest (M365 uses AES-256 by default). Get a letter of attestation from the provider if possible.
  5. Store BitLocker recovery keys securely in Azure AD or a printed copy in a fire-safe. Never store recovery keys on the same machine that is encrypted.

Evidence your assessor will ask for

  • BitLocker status report showing all CUI workstations are encrypted (manage-bde -status output)
  • Group Policy configuration requiring BitLocker on fixed and removable drives
  • BitLocker recovery key storage documentation (Azure AD or secure physical location)
  • Cloud provider attestation of data-at-rest encryption
  • Written policy requiring encryption of CUI at rest on all media

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

SC.2.016 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