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.004 — Alert on Audit Logging Process Failure

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

Alert in the event of an audit logging process failure.

What AU.2.004 means in plain English

If your logging system breaks—the log file fills up, Windows stops recording events, or M365 audit gets accidentally turned off—you need to know about it right away, not three months later during an assessment. Set up a simple alert so that if logging stops or the log becomes full, someone gets an email or sees a Windows alert. Otherwise you could have a gap in your audit trail and not realize it.

The assessment question

“Is there an automated or procedural mechanism in place to alert designated personnel when audit logging fails or audit logs reach capacity, with evidence of the alerting configuration?”

How to implement AU.2.004

  1. In Windows Event Viewer, configure the Security log to send an alert when it reaches a size threshold: right-click Security log > Properties > set the log size limit and choose "Archive the log when full." Then create a Windows Task Scheduler task that triggers on Event ID 1104 (Security audit log was cleared) and sends an email or creates a desktop notification.
  2. For Microsoft 365: go to Microsoft Purview Compliance Portal > Alerts > Create alert policy. Create a policy that fires if audit logging is disabled or if there is unusual activity. Route the alert to the owner or IT-responsible person.
  3. If you use a SIEM or log aggregator (even the free Wazuh), configure a rule that alerts when no new events are received from a monitored source for more than 24 hours—this catches silent failures.
  4. Test the alert annually: temporarily pause logging on a test machine, confirm the alert fires, then re-enable logging. Document the test result.
  5. Write a one-paragraph procedure describing what to do when an alert is received: who is notified, what they check, how quickly they must respond.

Evidence your assessor will ask for

  • Screenshot of Windows Event Log size/archive configuration
  • Screenshot or export of Task Scheduler task configured to alert on Event ID 1104 or log-full condition
  • Microsoft Purview alert policy configuration screenshot (if using M365)
  • Documentation of annual alert test with results
  • Written procedure for responding to audit logging failure alerts

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

AU.2.004 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 Audit & Accountability controls

AU.2.001

Create and Retain System Audit Logs

AU.2.002

Ensure User Accountability Through Unique Identifiers

AU.2.003

Review and Update Logged Events

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