Skills · Infrastructure & ops

Mtls Configuration

Unverified30/40

Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.

Originally by wshobson · MIT

Claude CodePartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
CursorPartialPlain prose you can paste in — but no Cursor rules file
CodexPartialPlain prose you can paste in — but no AGENTS.md
Gemini CLIPartialPlain prose you can paste in
CopilotPartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add mtls-configuration

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.

The whole source

No sign-in, no blur, nothing truncated
mtls-configuration/SKILL.md74 lines2.6 KBRawView on GitHub
Frontmatter — 2 properties
namemtls-configuration
descriptionConfigure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.
1---
2name: mtls-configuration
3description: Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.
4---A5No allowed-tools declared — no way to tell what this skill may touch
5 
6# mTLS Configuration
7 
8Comprehensive guide to implementing mutual TLS for zero-trust service mesh communication.
9 
10## When to Use This Skill
11 
12- Implementing zero-trust networking
13- Securing service-to-service communication
14- Certificate rotation and management
15- Debugging TLS handshake issues
16- Compliance requirements (PCI-DSS, HIPAA)
17- Multi-cluster secure communication
18 
19## Core Concepts
20 
21### 1. mTLS Flow
22 
23```
24┌─────────┐ ┌─────────┐
25│ Service │ │ Service │
26│ A │ │ B │
27└────┬────┘ └────┬────┘
28 │ │
29┌────┴────┐ TLS Handshake ┌────┴────┐
30│ Proxy │◄───────────────────────────►│ Proxy │
31│(Sidecar)│ 1. ClientHello │(Sidecar)│
32│ │ 2. ServerHello + Cert │ │
33│ │ 3. Client Cert │ │
34│ │ 4. Verify Both Certs │ │
35│ │ 5. Encrypted Channel │ │
36└─────────┘ └─────────┘
37```
38 
39### 2. Certificate Hierarchy
40 
41```
42Root CA (Self-signed, long-lived)
43
44 ├── Intermediate CA (Cluster-level)
45 │ │
46 │ ├── Workload Cert (Service A)
47 │ └── Workload Cert (Service B)
48
49 └── Intermediate CA (Multi-cluster)
50
51 └── Cross-cluster certs
52```
53 
54## Templates and detailed worked examples
55 
56Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates.
57 
58## Best Practices
59 
60### Do's
61 
62- **Start with PERMISSIVE** - Migrate gradually to STRICT
63- **Monitor certificate expiry** - Set up alerts
64- **Use short-lived certs** - 24h or less for workloads
65- **Rotate CA periodically** - Plan for CA rotation
66- **Log TLS errors** - For debugging and audit
67 
68### Don'ts
69 
70- **Don't disable mTLS** - For convenience in production
71- **Don't ignore cert expiry** - Automate rotation
72- **Don't use self-signed certs** - Use proper CA hierarchy
73- **Don't skip verification** - Verify the full chain
74 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Infrastructure & ops