diff options
| author | mo khan <mo@mokhan.ca> | 2025-03-17 11:42:15 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-03-17 11:42:15 -0600 |
| commit | d981d42202701b3bcd39399cb7f06e0825dff06d (patch) | |
| tree | 5783f0f16a66b30bc5f0e11fb352e721929a6cd7 | |
| parent | 877469fb38fc505abe80aa7234d1399e8e73dda0 (diff) | |
docs: start reading another paper on rebac
| -rw-r--r-- | doc/share/authz/ReBAC.md | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/share/authz/ReBAC.md b/doc/share/authz/ReBAC.md index 9e458fe..4c9deb7 100644 --- a/doc/share/authz/ReBAC.md +++ b/doc/share/authz/ReBAC.md @@ -2,7 +2,7 @@ > Authorization decisions are based on the relationship between the resource owner > and the resource accessor in a social network maintained by the protection -> system. +> system. [1] A Social Network System (SNS) maintains a social network for at least two reason: @@ -113,10 +113,14 @@ relationships can be "activated" simultaneously. ## Conclusion -Relationship-Based Access Control works best in application domains in which -binary relations are more natural for expressing authorization decisions than -unary relations (e.g., roles). +>Relationship-Based Access Control works best in application domains in which +>binary relations are more natural for expressing authorization decisions than +>unary relations (e.g., roles). ## See also -* [Relationship-Based Access Control: Protection Model and Policy Language by Philip W. L. Fong](https://cspages.ucalgary.ca/~pwlfong/Pub/codaspy2011.pdf) +* [Relationship-Based Access Control: Protection Model and Policy Language by Philip W. L. Fong][1] +* [Learning Relationship-Based Access Control Policies from Black-Box Systems][2] + +[1]: https://cspages.ucalgary.ca/~pwlfong/Pub/codaspy2011.pdf +[2]: https://dl.acm.org/doi/pdf/10.1145/3517121 |