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 · Audit & Accountability

AU.2.002 — Ensure User Accountability Through Unique Identifiers

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

Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.

What AU.2.002 means in plain English

Every person at your shop must have their own unique Windows login—no shared accounts like "shop_user" or "admin." When Event Viewer shows that someone deleted a file at 11 PM on a Friday, you need to know exactly which employee it was. Shared accounts make it impossible to hold anyone accountable and will cause an automatic CMMC failure. This also means each person logs out when they leave a machine—no leaving a session open for the next person.

The assessment question

“Does every individual who accesses systems containing CUI have a unique, personally assigned user account, with no shared credentials in use?”

How to implement AU.2.002

  1. Audit all current Windows accounts: open Computer Management > Local Users and Groups and list every account. Identify any shared or generic accounts (e.g., "admin," "shop," "machinist") and document who uses them.
  2. Create individual named accounts for every employee: format as firstname.lastname or first initial + last name (e.g., j.smith). Assign each person to appropriate groups (Users group for standard staff, Administrators only for IT-responsible personnel).
  3. Disable or delete all shared/generic accounts after migrating each person to their individual account. If a generic account is needed for a specific application, document the business justification and ensure it is not used for interactive login.
  4. Enforce account uniqueness with Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > enable "Interactive logon: Do not display last user name" and configure screen lock after 15 minutes of inactivity.
  5. Document all current user accounts with an account inventory spreadsheet: columns for Account Name, Full Name, Role, Date Created, and Account Type (standard/admin).

Evidence your assessor will ask for

  • Account inventory spreadsheet listing all user accounts with assigned individual
  • Screenshot from Computer Management or Active Directory showing only individually named accounts
  • Documentation that shared/generic interactive accounts have been disabled
  • Group Policy settings showing account lockout and session timeout policies
  • Sample audit log entry demonstrating individual user attribution (e.g., logon event showing a specific username)

Does AI prompt monitoring help with this control? Yes — directly.

AU.2.002 is one of the requirements a local AI prompt firewall concretely evidences. When employees send prompts to ChatGPT, Copilot, or Claude, that traffic crosses your external boundary — HoundShield inspects it on your own infrastructure (self-hosted Docker, Mode B), blocks CUI patterns before transmission, and writes every allowed/blocked event to a SHA-256 hash-chained log attributable to the user. Architecture diagram, active pattern set, and a log sample are the evidence an assessor tests this against for the AI data path.

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

More Audit & Accountability controls

AU.2.001

Create and Retain System Audit Logs

AU.2.003

Review and Update Logged Events

AU.2.004

Alert on Audit Logging Process Failure

AU.2.005

Correlate Audit Review, Analysis, and Reporting

AU.2.006

Provide Audit Record Reduction and Report Generation

AU.2.007

Provide System Clock Capability for Audit Timestamps

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