# Compliance Frameworks

> Security and privacy compliance patterns for B2B SaaS (SOC 2, GDPR). Use for audit preparation, control design, compliance gap analysis, or building compliance into features. Use when this capability is needed.

- Skill: `tomevault-io/compliance-frameworks` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/compliance-frameworks`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/compliance-frameworks/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/compliance-frameworks

---


# Compliance Frameworks Skill

Security and privacy compliance patterns for B2B SaaS products.

## When to Use

- Preparing for SOC 2 Type II audit
- Implementing GDPR data handling requirements
- Conducting compliance gap analysis
- Designing controls for audit evidence
- Building compliance into new features

## Quick Reference

### SOC 2 Trust Principles

| Principle | Key Controls | Priority |
|-----------|--------------|----------|
| **Security** | Access control, encryption, monitoring | Required |
| **Availability** | Uptime SLAs, redundancy, backups | Required |
| **Processing Integrity** | Input validation, error handling | Conditional |
| **Confidentiality** | Data classification, encryption | Common |
| **Privacy** | Consent, access requests, retention | If PII handled |

### GDPR Rights (Data Subject)

| Right | Implementation | Response Time |
|-------|----------------|---------------|
| Access | Data export endpoint | 30 days |
| Erasure | Deletion workflow | 30 days |
| Rectification | Edit profile | Reasonable |
| Portability | Machine-readable export | 30 days |
| Objection | Opt-out mechanisms | Immediate |

### Common Control Categories

| Category | Examples |
|----------|----------|
| **Preventive** | Access controls, input validation, encryption |
| **Detective** | Audit logging, anomaly detection, SIEM |
| **Corrective** | Incident response, patching, rollback |

## Key Patterns

### Control Design

```
Risk Identification → Control Selection → Implementation → Evidence Collection → Audit
```

### Evidence Types

| Type | Examples |
|------|----------|
| **Documentation** | Policies, procedures, diagrams |
| **Configuration** | Terraform, IAM policies, firewall rules |
| **Logs** | Audit trails, access logs, change records |
| **Screenshots** | Dashboard configs, settings, approvals |

## Integration with Development

### PR Checklist (Security-Sensitive Changes)

- [ ] No hardcoded secrets
- [ ] Access controls implemented
- [ ] Audit logging added
- [ ] Input validation present
- [ ] Error messages sanitized

### Compliance by Design

Build compliance into features from the start:

1. **Data Classification** - What data is being handled?
2. **Access Control** - Who can access it?
3. **Audit Trail** - What operations are logged?
4. **Retention** - How long is data kept?
5. **Deletion** - How is data removed?

## Files

- `reference.md` - Detailed checklists, control mappings
- `examples.md` - Implementation patterns, evidence templates

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/ai-enhanced-engineer) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-14 -->