sentry-security-basics

Configure Sentry security settings and data protection.Use when setting up data scrubbing, managing sensitive data,or configuring security policies.Trigger with phrases like "sentry security", "sentry PII","sentry data scrubbing", "secure sentry".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill automates the configuration of Sentry security settings and data protection protocols. It helps developers and security teams implement robust data scrubbing, manage sensitive PII (Personally Identifiable Information), and enforce security policies to ensure compliance with global standards such as GDPR, HIPAA, and SOC 2.

Use Cases

  • Compliance Readiness: Automating the setup of data scrubbing and PII protection to meet strict regulatory and audit requirements.
  • Sensitive Data Management: Configuring server-side and client-side scrubbing patterns to prevent passwords, tokens, and API keys from being leaked into error logs.
  • Access Control Enforcement: Implementing the principle of least privilege by managing team permissions, creating scoped API tokens, and rotating DSN keys.
  • Secure SDK Configuration: Ensuring best practices like using environment variables for DSNs and disabling default PII collection in SDK settings.
namesentry-security-basics
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Security Basics

Prerequisites

  • Security requirements documented
  • Compliance standards identified (GDPR, SOC 2, HIPAA)
  • Sensitive data patterns known
  • Access control needs defined

Instructions

  1. Enable server-side data scrubbing in project settings
  2. Configure client-side scrubbing in beforeSend for user data and request bodies
  3. Add sensitive field patterns for passwords, tokens, and API keys
  4. Store DSN in environment variables, never hardcode
  5. Set sendDefaultPii to false in SDK configuration
  6. Configure team permissions with principle of least privilege
  7. Create API tokens with minimal required scopes
  8. Rotate DSN keys and disable old ones after deployment
  9. Enable audit logging for compliance tracking
  10. Complete security checklist and document compliance status

Output

  • Data scrubbing configured
  • DSN secured in environment variables
  • Access controls implemented
  • Security checklist completed

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources