security-config

Configure mTLS, RBAC authorization, and Kubernetes NetworkPolicy for Temporal clusters.

3|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/therealbill/mynet --skill security-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-config
Source: https://github.com/therealbill/mynet/tree/main/timelord/skills/security-config
Command: npx skills add https://github.com/therealbill/mynet --skill security-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Temporal deployments can be vulnerable to misconfigurations that expose data and services. This skill provides a structured approach to securing Temporal clusters through mTLS, authorization, namespace isolation, and network policies.

Core Features & Use Cases

  • Transport Security (mTLS): enforce encrypted, authenticated connections between Temporal components.
  • Authorization & Access Control: implement role-based access control and claim mapping for multi-tenant environments.
  • Namespace Isolation & Network Policies: apply per-namespace security boundaries and infrastructure-level restrictions to reduce blast radius.
  • Use Case: Operators securing production Temporal deployments with strict policy enforcement across teams.

Quick Start

Enable mTLS for frontend and internode, configure authorization, and apply a namespace-scoped network policy to secure a production deployment.

Frequently Asked Questions about security-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure mTLS for a Temporal cluster deployment?

mTLS for Temporal is configured by enforcing encrypted and authenticated connections between components, applying TLS certificate management to both frontend and internode communication channels to secure production deployments.

How does RBAC authorization work in multi-tenant Temporal deployments?

RBAC authorization in multi-tenant Temporal deployments works by implementing role-based access control and claim mapping to restrict permissions, ensuring teams only access authorized namespaces and operations.

Can I apply Kubernetes NetworkPolicy to isolate Temporal namespaces?

Yes, you can apply Kubernetes NetworkPolicy to enforce per-namespace security boundaries and infrastructure-level restrictions, effectively reducing the blast radius in production Temporal clusters.

What is the best way to secure a production Temporal cluster across multiple teams?

The best way to secure a production Temporal cluster across multiple teams is enforcing mTLS, configuring RBAC authorization, and applying namespace-scoped network policies for strict policy enforcement.

When do I need namespace isolation and network policies for Temporal security?

You need namespace isolation and network policies for Temporal security when operating multi-tenant deployments, requiring per-namespace security boundaries to reduce the blast radius of potential misconfigurations.