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 · Maintenance

MA.2.116 — Supervise maintenance activities without required access authorization

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

Supervise the maintenance activities of maintenance personnel without required access authorization.

What MA.2.116 means in plain English

If a maintenance technician does not have a security clearance or formal authorization to access your CUI systems, you must have an authorized employee physically present with them while they work — or at minimum watching their remote session in real time. A repairman who comes to fix a broken hard drive in your server has no clearance and no authorization to see your government files; an authorized employee must watch them the entire time. This is about accountability: you are responsible for what happens on your systems, so when an uncleared person is working on them, one of your cleared people stays with them.

The assessment question

“Is there a documented procedure requiring that an authorized employee supervises any maintenance technician who does not have the required access authorization — and is this supervision actually occurring and being logged?”

How to implement MA.2.116

  1. Define "authorized maintenance personnel" in your Maintenance Policy: people who have been background-checked, trained, and formally granted access to systems containing CUI.
  2. For all other maintenance personnel (repair technicians, hardware vendors, building contractors who must access server rooms), create a "Supervised Maintenance" procedure: an authorized employee must escort and observe the technician for the entire duration.
  3. For remote supervision, use your remote access tool's session recording feature — the authorized employee watches the live session and the recording is retained for audit.
  4. Create a Supervision Log entry for every supervised maintenance event: Date, Technician Name/Company, Work Performed, Authorized Supervisor Name, Duration, and any concerns noted.
  5. Train all employees on the rule: if an uncleared vendor or contractor needs access to company IT systems, they must call an authorized employee to supervise — no exceptions.

Evidence your assessor will ask for

  • Maintenance Policy defining authorized vs. unauthorized maintenance personnel
  • Supervised Maintenance Procedure document
  • Supervision Log with entries for the past 12 months
  • Session recording files or screenshots for remote supervised maintenance sessions
  • Physical visitor log showing escorted access for any on-premises maintenance visits

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

MA.2.116 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 Maintenance controls

MA.2.111

Perform maintenance on organizational systems

MA.2.112

Provide controls on tools and personnel for maintenance

MA.2.113

Ensure equipment removed for offsite maintenance is sanitized

MA.2.114

Check media containing diagnostic programs for malicious code

MA.2.115

Require multifactor authentication for nonlocal maintenance

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