Difference between revisions of "Access Control"
(→Problems) |
(→Problems) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
==Problems== | ==Problems== | ||
Security boundaries seem to be mixing two security features which basically describes why cross-site scripting attacks are so common. The basic rule is this - Don't mix control messages with data messages. The two rules are: | Security boundaries seem to be mixing two security features which basically describes why cross-site scripting attacks are so common. The basic rule is this - Don't mix control messages with data messages. The two rules are: | ||
| − | # Bell–LaPadula model focuses on data confidentiality (privacy - | + | # Bell–LaPadula model focuses on data confidentiality (privacy - MAC = Mandatory Access Control) |
| − | # Biba Integrity Model is for the protection of data integrity (control - | + | # Biba Integrity Model is for the protection of data integrity (control - MIC = Mandatory Integrity Control) |
Applying both rules means that no security boundary should be crossed without clear permission to do so. And a security policy that allows data flow (MAC) should not allow control flow (MIC). | Applying both rules means that no security boundary should be crossed without clear permission to do so. And a security policy that allows data flow (MAC) should not allow control flow (MIC). | ||
So, security boundaries need to distinguish between the two. | So, security boundaries need to distinguish between the two. | ||
| − | *As a side note Microsoft Vista | + | *As a side note Microsoft Vista UAC (user access control) is not a boundary of any sort, it is a UX that applies policy to override MAC. (Tom Jones wrote the spec.) |
*It is the rainbow books that described MAC & MIC rules. | *It is the rainbow books that described MAC & MIC rules. | ||
Latest revision as of 10:59, 14 November 2024
Contents
Full Title or Meme
Authorization of Access to a Resource is the primary end goal for nearly all Identity Management.
Context
There are a variety of reasons to limit access to a resource on the web. The primary ones are:
- Embarrassment - there are some things we just don't want others to know about us.
- Financial - there are some things that we want to make a profit from releasing.
Problems
Security boundaries seem to be mixing two security features which basically describes why cross-site scripting attacks are so common. The basic rule is this - Don't mix control messages with data messages. The two rules are:
- Bell–LaPadula model focuses on data confidentiality (privacy - MAC = Mandatory Access Control)
- Biba Integrity Model is for the protection of data integrity (control - MIC = Mandatory Integrity Control)
Applying both rules means that no security boundary should be crossed without clear permission to do so. And a security policy that allows data flow (MAC) should not allow control flow (MIC). So, security boundaries need to distinguish between the two.
- As a side note Microsoft Vista UAC (user access control) is not a boundary of any sort, it is a UX that applies policy to override MAC. (Tom Jones wrote the spec.)
- It is the rainbow books that described MAC & MIC rules.
Solutions
In general the wiki page on Authorization deals with Access Control in an Identity Management ecosystem.
In the following cases Access Control is addressed independently from Identity Management.
Also note that the use of Verifiable Credentials can be tied to a one-time or Pseudonym thus avoiding any Identity Management between the holder and the verifier.
Access Control Encryption
or ACE is a scheme for using attribute encryption to acquire access.[1]
References
- ↑ Made Sedaghat +1, Cross-Domain Attribute-Based Access Control Encryption in Cryptology and Network Security Springer ISBN 9783030925475
Other Material
- See wiki page on Access Token.
