Most AI policies fail because they live on paper. Back yours with 17,410+ classified domains for enforcement from day one.
Existing AUPs were built for installed software, sanctioned SaaS, and managed devices. AI tools break every one of those assumptions.
Explicitly define what counts as an AI tool. Distinguish embedded AI features from standalone services.
Map AI tool categories to organizational risk tolerance. Not all tools carry equivalent risk.
Specify what can be typed into a prompt, uploaded, or must never leave the organization.
If exception requests take six weeks, employees bypass the process entirely.
Domain blocklists, DLP, and network monitoring transform policy into an active security layer.
A comprehensive starting point for your first AI-specific AUP. Adapt to your regulatory environment before publication.
============================================================ ENTERPRISE AI ACCEPTABLE USE POLICY Version: 1.0 | Effective Date: [DATE] Classification: Internal — All Employees ============================================================ 1. PURPOSE This policy establishes the rules and guidelines governing the use of Artificial Intelligence (AI) tools by all employees, contractors, and third-party personnel. It defines approved and prohibited uses, data handling requirements, and enforcement mechanisms to protect organizational data while enabling responsible AI adoption. 2. SCOPE This policy applies to: - All employees, contractors, and temporary staff - All devices (corporate-managed and personal/BYOD) - All networks (corporate, remote, and personal) - All AI tools (browser-based, installed, API-accessed) 3. DEFINITIONS "AI Tool": Any software, service, or API that uses machine learning, large language models, generative AI, or neural networks to process, generate, or transform content — including text, code, images, audio, and video. "Approved AI Tool": An AI tool that has completed the organization's vendor security assessment and is listed in the Approved AI Tools Registry maintained by IT. "Restricted AI Tool": An AI tool approved for limited use cases with specific data handling constraints. "Prohibited AI Tool": Any AI tool not listed as Approved or Restricted. Access is blocked at the network level. 4. AI TOOL TIERS AND APPROVED TOOLS Tier 1 — APPROVED (Full Use): - [Platform A] Enterprise (with SSO, data retention off) - [Platform B] Business (approved contract on file) - [Internal AI tools deployed on corporate infrastructure] Tier 2 — RESTRICTED (Limited Use): - [Platform C] (approved for non-sensitive content only) - AI-powered features in approved SaaS (e.g., Copilot) - Requires manager approval for each use case Tier 3 — PROHIBITED (Blocked): - All AI tools not listed in Tier 1 or Tier 2 - Enforced via network blocklist (17,410+ domains) - No exceptions without CISO written approval 5. DATA HANDLING REQUIREMENTS 5.1 PUBLIC data .......... Approved and Restricted tools 5.2 INTERNAL data ........ Approved tools only 5.3 CONFIDENTIAL data .... Prohibited from ALL AI tools 5.4 REGULATED data ....... Prohibited from ALL AI tools (PII, PHI, PCI, attorney-client, trade secrets) Employees MUST NOT: - Paste source code into any non-Approved AI tool - Upload documents containing customer data - Submit financial projections or M&A materials - Use AI tools to process employee personal data - Disable or circumvent network-level AI tool blocks 6. MANDATORY TRAINING AND ACKNOWLEDGMENT 6.1 All employees must complete AI Acceptable Use training within 30 days of policy effective date. 6.2 New hires must complete training during onboarding. 6.3 Annual refresher training is required. 6.4 Signed acknowledgment is stored in HR records. 7. EXCEPTION REQUEST PROCESS 7.1 Submit request via [ticketing system] under category "AI Tool Exception Request". 7.2 Required information: tool name, URL, business justification, data types involved, user count. 7.3 Review by: IT Security → Legal → CISO. 7.4 SLA: 5 business days for initial review. 7.5 Approved exceptions are time-limited (90 days) and subject to quarterly renewal. 8. INCIDENT REPORTING Employees who suspect a data exposure through an AI tool must report immediately to [[email protected]] or via the incident reporting hotline. Do NOT attempt to delete or modify AI tool conversation histories, as this may complicate forensic investigation. 9. ENFORCEMENT 9.1 TECHNICAL: Network-level blocking of prohibited AI tool domains via continuously-updated blocklist. 9.2 MONITORING: DNS/proxy log correlation against the AI tools domain feed identifies policy violations. 9.3 DISCIPLINARY: Violations are subject to progressive discipline per HR policy, up to and including termination for intentional data exposure. 10. POLICY REVIEW SCHEDULE - Quarterly review by AI Governance Committee - Annual full revision with Legal and Compliance - Ad-hoc updates triggered by regulatory changes - Approved Tools Registry updated monthly by IT ============================================================ Approved by: [CISO Name] Date: [DATE] Legal Review: [GC Name] Date: [DATE] Next Review: [DATE + 90 days] ============================================================
Blocked at the network level via firewall EDL.
Logged and monitored with DLP inspection on uploads.
Standard SIEM logging with no blocking applied.
Map each of the 18 functional categories to a policy tier. Adjust based on your industry and risk appetite.
Every policy statement must map to at least one technical control.
| Policy Tier | Enforcement Action | Infrastructure |
|---|---|---|
| Prohibited | Domain blocking | Firewall EDL + DNS layer |
| Restricted | Log + alert; DLP inspection on uploads | Proxy / SWG + SIEM |
| Approved | Standard monitoring, no blocking | SIEM logging |
This script generates category-filtered blocklists, creating separate feeds for each policy tier.
#!/usr/bin/env python3 """Generate tier-based blocklists from the AI Tools Blocklist database. Maps policy tiers to AI tool categories for firewall/proxy feeds.""" import csv import json from datetime import datetime # Define your policy tier mappings TIER_CONFIG = { "prohibited": [ "Text & Language", "Code & Development", "Data & Analytics", "Voice & Speech", "Autonomous Agents", "Aggregators & Platforms", ], "restricted": [ "Image & Visual", "Video & Animation", "Music & Audio", "Design & Creative", "Research & Knowledge", "Education & Training", ], } def generate_tier_feeds(db_path: str, output_dir: str): """Read AI tools database and generate per-tier domain lists.""" feeds = {"prohibited": [], "restricted": [], "unclassified": []} with open(db_path, "r") as f: reader = csv.DictReader(f) for row in reader: domain = row["domain"].strip().lower() category = row.get("primary_category", "Unknown") placed = False for tier, categories in TIER_CONFIG.items(): if category in categories: feeds[tier].append(domain) placed = True break if not placed: feeds["unclassified"].append(domain) for tier, domains in feeds.items(): out_path = f"{output_dir}/blocklist_{tier}.txt" with open(out_path, "w") as out: out.write(f"# AI Tools Blocklist — {tier.upper()} tier\n") out.write(f"# Generated: {datetime.now().isoformat()}\n") out.write(f"# Domains: {len(domains)}\n\n") for d in sorted(domains): out.write(d + "\n") print(f" [{tier.UPPER():>14}] {len(domains):>6} domains → {out_path}") return feeds if __name__ == "__main__": print("AI AUP Tier Feed Generator") print("=" * 50) generate_tier_feeds("ai_tools_database.csv", "./feeds")
Loaded into your firewall EDL. Access blocked outright.
Configured for log-and-alert mode in your proxy or SIEM.
Newly discovered tools. Default to Prohibited until reviewed.
No monitoring means no policy. Effective compliance operates on three timescales.
Firewall and DNS block prohibited access instantly. Violations are prevented, not just detected.
Aggregate blocked requests, flagged uploads, and anomalous patterns via SIEM.
Board-level governance covering trends, tier reassignments, and regulatory updates.
This SIEM query generates a daily AUP compliance summary with repeat offenders and high-violation departments.
-- Daily AI AUP Compliance Report (Splunk SPL) -- Correlates firewall blocks against AI blocklist feed index=firewall action=blocked [| inputlookup ai_tools_blocklist.csv | fields domain category | rename domain AS dest_domain] | stats count AS total_blocks dc(src_ip) AS unique_users dc(dest_domain) AS unique_tools values(category) AS categories BY src_department | sort - total_blocks | eval risk_level = case( total_blocks > 100, "CRITICAL", total_blocks > 50, "HIGH", total_blocks > 10, "MEDIUM", 1=1, "LOW" ) | table src_department risk_level total_blocks unique_users unique_tools categories
risk_level classification prioritizes follow-up actionsThis is where the AI AUP evolves to match reality. The AI Governance Committee leads the review.
The exception process is your policy's pressure valve. Too slow and employees bypass it. Too permissive and it undermines the policy.
Provides business justification for the tool and use case.
Evaluates data handling, privacy policy, and security posture.
Reviews terms of service for data rights. Compliance adds a 4th stage for regulated data.
Employee was unaware or didn't realize the tool was prohibited.
Employee circumvents controls or deliberately submits classified data.
This pipeline automates progressive discipline with a twelve-month lookback window.
#!/usr/bin/env python3 """Automated AUP violation alerting and escalation pipeline. Tracks repeat offenders and triggers HR escalation workflows.""" import json from datetime import datetime, timedelta from collections import defaultdict ESCALATION_THRESHOLDS = { "notice": 1, # First violation — notify user + manager "counseling": 3, # Third violation — HR counseling session "incident": 5, # Fifth violation — formal security incident "critical": 10, # Tenth violation — legal review + suspend access } def process_violations(violations: list, lookback_days: int = 365): """Aggregate violations per user within lookback window. Generate appropriate escalation actions.""" cutoff = datetime.now() - timedelta(days=lookback_days) user_counts = defaultdict(int) escalations = [] for v in violations: if datetime.fromisoformat(v["timestamp"]) >= cutoff: user_counts[v["user_id"]] += 1 for user_id, count in user_counts.items(): for level, threshold in sorted( ESCALATION_THRESHOLDS.items(), key=lambda x: x[1], reverse=True ): if count >= threshold: escalations.append({ "user_id": user_id, "violation_count": count, "escalation_level": level, "action": get_action(level), }) break return escalations def get_action(level: str) -> str: actions = { "notice": "Send email notification to user and direct manager", "counseling": "Create HR ticket for mandatory counseling session", "incident": "Open security incident — preserve evidence, notify CISO", "critical": "Suspend network access — escalate to Legal and CISO", } return actions.get(level, "Manual review required")
One-time violations get a proportionate response. No overreaction to honest mistakes.
Repeated violations escalate automatically through the discipline chain.
A policy employees don't understand is a policy they won't follow. Communicate on three levels.
Establishes policy authority. Share anonymized shadow AI stats to make risk concrete.
Context-specific guidance per team. Engineering, legal, and marketing each get tailored details.
Training modules, periodic reminders, and visible enforcement keep the policy top of mind.
Blocked attempts per employee per month. Declining = policy internalized.
Active exceptions vs. total employees. Above 15% = policy too restrictive.
Target 100% within 60 days of launch. Maintain 95%+ via annual refreshers.
Confirmed data exposures via AI tools per quarter. The ultimate effectiveness measure.
Get the AI Tools Blocklist to power your AUP enforcement layer. Our 17,410+ classified domains map directly to your policy tiers.
Tell us about your organization and AI governance requirements.