Security and Compliance Requirements
What you'll learn: How to identify the security and legal rules that shape what your system can and cannot do.
The Core Idea
When designing a system, you can't just focus on making it work well—you must also keep it safe and legal. Security and compliance requirements define who can access what, how sensitive data must be protected, and which laws or regulations your system must follow.
Think of it like building a house: you need locks on doors (security) and must follow building codes (compliance). Both constrain your design choices before you write a single line of code.
Four Key Constraint Categories
Authentication
Who are you? Your system needs a way to verify user identity. Will users log in with passwords, biometric data, or multi-factor authentication? This affects your database design and user flow.
Authorization
What can you do? Once authenticated, different users have different permissions. An admin can delete accounts; a regular user cannot. You must design role-based access controls into your system from the start.
Data Privacy
How do we protect sensitive information? Personal data, payment details, and health records require encryption at rest and in transit. You might need to anonymize data or support "right to be forgotten" deletion requests.
Regulatory Requirements
What laws apply? GDPR in Europe, HIPAA for healthcare in the US, PCI-DSS for payment processing—these aren't optional. They dictate data retention policies, audit logs, geographic data storage, and more.
Why This Matters Early
You cannot bolt security onto a finished system. If your design stores unencrypted passwords or mixes customer data across regions, fixing it later means rebuilding everything.
Key Takeaway: Security and compliance requirements are non-negotiable constraints that must inform your architecture decisions from day one—they determine how you authenticate users, control access, protect data, and stay within the law.