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 · Media Protection

MP.2.121 — Mark media with necessary CUI markings and distribution limitations

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

Mark media with necessary CUI markings and distribution limitations.

What MP.2.121 means in plain English

Any physical or digital media that contains CUI must be labeled so anyone who handles it knows it contains sensitive government information and knows who is authorized to receive it. For printed documents, this means a "CUI" header/footer on every page. For a USB drive or external hard drive containing CUI, it needs a physical label saying "CUI" and possibly the specific category and distribution limitation (like "CUI//SP-CTI" for specific Controlled Technical Information). The government provides free templates and labeling guidance — this is mostly about creating a labeling habit and applying sensitivity labels in Microsoft 365.

The assessment question

“Are all documents, files, and physical media containing CUI marked with the appropriate CUI designation and distribution/dissemination limitations — and is this marking applied consistently by all employees?”

How to implement MP.2.121

  1. Download the official CUI marking templates from the National Archives CUI Registry (archives.gov/cui) — use these as your standard document headers and footers.
  2. Configure Microsoft Word and Outlook templates with a pre-built CUI header/footer so employees do not have to remember to add it manually.
  3. Enable Microsoft Purview sensitivity labels in Microsoft 365 (available in Business Premium) and create a "CUI" label that automatically adds a header/footer to documents and emails and restricts forwarding.
  4. Purchase pre-printed CUI label stickers or a label printer for physical media (USB drives, external hard drives, printed binders) — label every piece of physical media that contains CUI.
  5. Include CUI marking requirements in your annual security awareness training and add it as a checklist item in the new employee onboarding process.

Evidence your assessor will ask for

  • Sample CUI-marked documents showing correct header/footer format
  • Microsoft Purview sensitivity label configuration screenshot
  • Photograph of CUI-labeled physical media (USB drives, binders)
  • Employee acknowledgment that CUI marking requirements were covered in training

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

MP.2.121 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 Media Protection controls

MP.1.118

Protect system media containing CUI

MP.1.119

Limit access to CUI on system media

MP.1.120

Sanitize or destroy system media before disposal or reuse

MP.2.122

Control access to media containing CUI during transport

MP.2.123

Implement cryptographic mechanisms to protect CUI during transport

MP.2.124

Control use of removable media on system components

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