In the FAW Security framework, which mapping paradigm best describes the mapping of Security Context to Data Roles?

In the FAW Security framework, which mapping paradigm best describes the mapping of Security Context to Data Roles?

• A. ONE-to-MANY
• B. ZERO-to-ONE
• C. Security Context to Data Role is ONE-to-ONE
• D. MANY-to-MANY

Answer: (C)

In this framework, each Security Context is paired with a single, specific Data Role, and that Data Role is tied to that exact Security Context. That one-to-one relationship keeps authorization precise and unambiguous: given a security context, there’s a unique set of data permissions defined by its corresponding role, and no other context shares those same permissions. This makes policy evaluation straightforward and auditing clear, since you can trace a request directly to one role without crossing into multiple roles or overlapping access. If a context could map to multiple roles, or if many contexts could map to many roles, permissions could blur, leading to inconsistent access decisions and harder governance. A zero-to-one mapping would leave some contexts without defined access, creating gaps. So the best fit for how Security Context maps to Data Roles is a one-to-one relationship.

In this framework, each Security Context is paired with a single, specific Data Role, and that Data Role is tied to that exact Security Context. That one-to-one relationship keeps authorization precise and unambiguous: given a security context, there’s a unique set of data permissions defined by its corresponding role, and no other context shares those same permissions. This makes policy evaluation straightforward and auditing clear, since you can trace a request directly to one role without crossing into multiple roles or overlapping access. If a context could map to multiple roles, or if many contexts could map to many roles, permissions could blur, leading to inconsistent access decisions and harder governance. A zero-to-one mapping would leave some contexts without defined access, creating gaps. So the best fit for how Security Context maps to Data Roles is a one-to-one relationship.