Resposta de referência
| Framework | Scope | Key Security Requirements |
|---|---|---|
| PCI DSS | Payment card data | Network segmentation, encryption, access control, logging, vulnerability management |
| HIPAA | Protected health information | Access controls, audit trails, encryption, risk assessments, business associate agreements |
| SOC 2 | Service organization controls | Security, availability, processing integrity, confidentiality, privacy |
| NIST CSF | General cybersecurity | Identify, Protect, Detect, Respond, Recover — risk-based framework |
| ISO 27001 | Information security management | ISMS implementation, risk assessment, control selection from Annex A |
| GDPR | EU personal data | Data minimization, consent, breach notification, right to erasure, DPO requirement |
Practical impact: Compliance frameworks provide a baseline, not a ceiling. I use them to structure security programs — NIST CSF for the overall framework, with specific controls mapped to regulatory requirements (PCI, HIPAA) based on the organization's data types and business operations.