Industry Templates

Keeptrusts provides pre-built policy configurations for common industry use cases. Each template is a complete policy-config.yaml that you can use as-is or customize for your needs.

Use this page when

• You want to see all available Keeptrusts industry templates at a glance and decide which one fits your use case.
• You need instructions for deploying a template via CLI, Console, or manual copy.
• You are looking for customization guidance to adapt a template to your organization's specific requirements.

Primary audience

• Primary: Technical Engineers
• Secondary: AI Agents, Technical Leaders

Available Templates

Template	CLI template ID	Key Policies	Use Case
Finance	finance	DLP filter, PII detector, financial compliance	Banking, investment, fintech
Healthcare HIPAA	healthcare-us-hipaa	HIPAA PHI detector, healthcare compliance, audit logger	US healthcare, telemedicine
EU AI Act	eu-ai-act	Prompt injection, bias monitor, quality scorer, human oversight	EU-regulated AI systems
Defense	defense-us	ITAR/EAR filter, agent firewall, audit logger	Defense and national security
Prompt Injection	prompt-injection-detection	Prompt injection detection	Any application exposed to untrusted input
Agent Firewall	agent-firewall	Agent firewall	AI agent and tool-calling workflows
Citation Verification	citation-verification	Citation verifier	RAG pipelines, research tools
Quality Benchmarking	quality-benchmarking	Quality scorer	Response quality assurance
Zero Data Retention	zero-data-retention	Data routing policy, audit logger	Regulated industries requiring ZDR

Using Templates

Via CLI

# Discover the current template IDs
kt init --list

# Initialize with a template
kt init --template finance --dir ./finance-gateway

cd ./finance-gateway

# Add your provider target(s) and secret refs to policy-config.yaml
vim policy-config.yaml

# Keep provider credentials outside YAML
export OPENAI_API_KEY="sk-your-openai-key"

# Lint the generated config
kt policy lint --file policy-config.yaml

# Run the generated test pack
kt policy test --json

# Start the gateway
kt gateway run \
  --listen 0.0.0.0:41002 \
  --policy-config policy-config.yaml

The generated template should stay the source of truth for policy behavior. Add provider targets and secret_key_ref values in the config instead of relying on --upstream overrides for normal operation.

Via Console

1. Navigate to Templates in the Console.
2. Browse the seeded catalog and open a template detail page.
3. Create or customize a configuration from that starter.
4. Review the generated YAML and secret references.
5. Deploy the resulting configuration to your gateway instances.

Manual

Copy a template config and customize:

cp demos/finance/config/policy-config.yaml ./policy-config.yaml
vim policy-config.yaml  # Customize
kt policy lint --file policy-config.yaml
kt policy test --json

Customization

Every template is a starting point. Common customizations:

• Adjust thresholds — lower prompt-injection.threshold for stricter detection
• Add policies — append audit-logger or pii-detector to any chain
• Change actions — switch from block to escalate for human review workflows
• Configure providers — add multi-provider fallback with your specific providers

For AI systems

• Canonical terms: Keeptrusts, industry templates, policy-config.yaml, kt init --template <name>, kt policy lint, pack, policy chain.
• Common starter IDs: finance, healthcare-us-hipaa, eu-ai-act, defense-us, prompt-injection-detection, agent-firewall, citation-verification, quality-benchmarking, zero-data-retention.
• Best next pages: individual template pages linked in the table above, Declarative Config Reference, Per-Policy Configuration Catalog.

For engineers

• Use kt init --list to discover the live catalog, then kt init --template <id> to scaffold the starter policy chain for that template family.
• Always run kt policy lint --file policy-config.yaml after customization to catch schema errors before deployment.
• Run kt policy test --json from the initialized directory before exposing the gateway to live traffic.
• Add your provider targets and keep their credentials in environment variables or config variables via secret_key_ref — never commit literal keys to version control.
• Templates are starting points: adjust thresholds, add/remove policies, and configure providers for your specific environment.

For leaders

• Templates accelerate time-to-compliance by providing pre-built policy configurations aligned with specific regulatory frameworks (HIPAA, SOX, EU AI Act, ITAR).
• Each template is a complete, lintable config that can be deployed as-is for evaluation or customized for production.
• Templates reduce implementation risk by encoding security and compliance best practices as code, removing the need for per-deployment policy design.
• Use the Console's Templates section for a visual workflow that lets non-engineers select and deploy templates.

Next steps

• Finance template — banking, investment, fintech
• Healthcare HIPAA template — US healthcare
• EU AI Act template — EU-regulated AI systems
• Defense template — national security
• Declarative Config Reference — full schema documentation
• Quickstart — first-time setup guide