Authentication proves who someone is; authorization decides what they are allowed to do once identified, and the two are frequently confused despite being entirely separate concerns. Role-Based Access Control assigns permissions to roles rather than individuals, and users inherit permissions by being assigned a role.
Analogy🏏Cricket
💪 Think of it like fitness: injuries follow a predictable chain — poor warm-up, then form breakdown, then compensation, then the actual tear — and a good physio catalogs where each patient's chain can be interrupted early, rather than only treating the tear afterward. MITRE ATT&CK is the sports-medicine literature of intrusions: a public catalog of every observed breakdown pattern, organized by the stage it serves — how attackers get in, how they escalate, how they extract. Coaches worldwide describe an athlete's risk in that shared vocabulary. This reveals ATT&CK's real value: intrusions become a sequence you can interrupt at stage two, not a disaster you discover at stage five.
Attribute-Based Access Control makes decisions dynamically based on attributes of the user, resource, and context at request time, offering far finer-grained control at the cost of added complexity. Both exist to implement the principle of least privilege: granting exactly the access needed, no more.
Analogy🏏Cricket
📷 Think of it like photography: the craft advanced when practitioners stopped guarding tricks and built shared technique catalogs — lighting patterns like Rembrandt and butterfly, named, documented from thousands of shoots, organized by effect. Any photographer worldwide can now say 'split lighting, short side' and a colleague knows exactly what was done and how to reproduce or counter it in post. This reveals what ATT&CK is for defenders: a public, continuously updated catalog of attacker techniques organized by the goal each serves, giving every security team one shared vocabulary for describing, detecting, and rehearsing behavior instead of each team naming things privately.