Security as a Quality Attribute
What you'll learn: How security concerns translate into architectural decisions that protect your system's data and behavior.
The Core Idea
Security isn't just a feature you bolt on at the end—it's a quality attribute that shapes your architecture from day one. Just like you design for performance or scalability, you architect for security by baking in protections against threats throughout your system's structure.
When treating security as a quality attribute, you focus on four foundational pillars:
Confidentiality
Ensuring only authorized parties can access sensitive information. Think of it like sealed envelopes—your architecture must decide what data needs "envelopes," who can open them, and how they're sealed (encryption).
Architectural impact: Where do you encrypt? At rest? In transit? Which services can decrypt?
Integrity
Guaranteeing data hasn't been tampered with. Like a wax seal on that envelope—you need mechanisms to detect if someone modified your data.
Architectural impact: Checksums, digital signatures, audit logs. Where do these live? How are they verified?
Authentication
Proving "you are who you say you are." This is your system's ID check at the door.
Architectural impact: Centralized identity service? Token-based? Where does authentication happen in your service chain? How do credentials flow?
Authorization
Determining "what you're allowed to do" once identified. Authentication gets you in the building; authorization decides which rooms you can enter.
Architectural impact: Role-based access control (RBAC)? Attribute-based? Where are policies enforced—at the gateway, each service, or both?
Security Trade-offs
Like other quality attributes, security involves trade-offs. Strong encryption impacts performance. Fine-grained authorization adds complexity. Multi-factor authentication affects usability.
Key Takeaway: Security as a quality attribute means making explicit architectural decisions about confidentiality, integrity, authentication, and authorization early, understanding their trade-offs, and building them into your system's fundamental structure rather than treating them as afterthoughts.