expanso-encrypt-data

Encrypt sensitive data fields using AES-256-GCM encryption.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-encrypt-data
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expanso-encrypt-data
Source: https://github.com/expanso-io/expanso-skills/tree/main/skills/recipes/encrypt-data
Command: npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-encrypt-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of encrypting sensitive data fields within a dataset, ensuring compliance with data privacy regulations like GDPR and CCPA.

Core Features & Use Cases

  • Field-Level Encryption: Encrypts specific fields such as payment card information (PCI-DSS) and Personally Identifiable Information (PII) using AES-256-GCM.
  • Data Preservation: Preserves essential analytics-safe fields and extracts key identifiers (e.g., last four digits of a card, email domain) for continued usability.
  • Use Case: Securely process customer transactions by encrypting credit card numbers and PII while retaining the last four digits for reference and the email domain for segmentation.

Quick Start

Run the encrypt-data pipeline with sample data using the provided run script.

Frequently Asked Questions about expanso-encrypt-data

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

FAQPage Schema
How do I encrypt PII and payment card data for GDPR compliance?▼

Encrypt PII and payment card data for GDPR compliance by applying AES-256-GCM field-level encryption to sensitive dataset fields. The process secures specific columns like credit card numbers while preserving analytics-safe fields for continued usability.

What is field-level encryption and how does it preserve analytics-safe fields?▼

Field-level encryption secures specific sensitive columns using AES-256-GCM while extracting key identifiers like the last four digits of a card or email domain. This preserves analytics-safe fields, allowing continued data segmentation and reference without exposing full PII.

Do I need Expanso Edge to encrypt sensitive data fields?▼

Yes, you need Expanso Edge to run the data encryption pipeline. You must also configure specific environment variables for encryption keys before executing the provided scripts to ensure secure AES-256-GCM processing.

Can I retain the last four digits of a card after encrypting payment data?▼

Yes, encrypting payment data with this process automatically extracts and retains key identifiers like the last four digits of a credit card. This allows you to securely process transactions while keeping reference data accessible.

What's the best way to secure customer transaction datasets with PCI-DSS requirements?▼

Secure customer transaction datasets with PCI-DSS requirements by encrypting sensitive fields using AES-256-GCM. This approach encrypts payment card information at the field level while extracting email domains for segmentation and retaining card digits for reference.