TechPrufer
Sign inGet started

Blogs›Temporal›Activity Isolation for Security

Activity Isolation for Security

Activity Isolation for Security

2
posts
2025–2026

Temporal offers a layered approach to data security. This post details how to protect sensitive data in transit using TLS and at rest using application-level encryption via Payload Codecs. It explains the roles of Data Converters, Payload Converters, Failure Converters, and Payload Codecs in serializing, deserializing, and transforming data. The focus is on using Payload Codecs for encryption, ensuring that the Temporal Service only sees encrypted data, and that keys are managed externally.

2026

Using Activity isolation as a security boundary

8/4/2026

This post details a specific architectural pattern for enhancing security by consolidating PII scanning, classification, and storage within a single Temporal Activity. It addresses the trade-offs of deviating from the 'single-purpose Activity' guideline for compliance reasons. The post also elaborates on implementing a swappable storage layer using a `DataStore` protocol and demonstrates how heartbeating can be used to detect stuck Workers in long-running streaming Activities, enabling resumable processing.

2025

How to protect sensitive data in a Temporal Application

10/9/2025

This post elaborates on data security within Temporal applications by focusing on application-level encryption using Payload Codecs. It details the components of the Data Converter (Payload Converter, Failure Converter, Payload Codec) and explains how Payload Codecs can be implemented to encrypt and decrypt sensitive data before it is transmitted to or received from the Temporal Service. This enhances security by ensuring the Temporal Service never has access to unencrypted sensitive data.