Re: Avoiding IBAC

"Karp, Alan H" <[email protected]>
Newsgroups gmane.comp.capabilities.general
Message-ID <8AD823089998C849A832D86972E69CD54194CAB8@G4W3222.americas.hpqcorp.net>
The key point OwnCloud is missing is the fact that there are often good reasons to violate policy.  Which is more likely to get you fired, violating a security policy or losing an important customer?  If you don't give people a safe way to violate policy when they must, such as VOC, they will use unsafe mechanisms, such as sharing credentials.  At any rate, if OwnCloud insists on implementing this policy, there are any number of Data Loss Prevention systems they can buy.

Of course, that doesn't answer your question, does it?  The approach used by PubShare does.  Each object supports a delegate method that takes a reference to the delegatee as an argument.  All the delegate method needs is the policy to enforce, e.g., a way to distinguish people inside the company from people outside.  The nice thing about this approach is that the easy way is the secure way, so there's no incentive for people to find a workaround.

________________________
Alan Karp
Principal Scientist
Enterprise Services, Office of the CTO
Hewlett-Packard Company
1501 Page Mill Road
Palo Alto, CA 94304
1 (650) 386-4568
http://www.hpl.hp.com/personal/Alan_Karp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.