On 08/01/2012 02:01 PM, Dries Kimpe wrote:
----> Denial of service and related events are basically accounting
for 50% of yr3, 33% of yr 4 and 50% of yr 5 (with yr 4 and yr 5 being the same deliverable). Can we really justify so much effort to this one topic? Is it an issue in similar storage systems? For example, do lustre/gpfs/... have anything in this area and if not, are they looking into adding this? Given the intended deployment of the storage system, there might be other areas that could provide more benefit? Do you have suggestions for anything you might find more useful? That would be welcome. Coming up with 5 year plans with a one day turn around is challenging. Ideas from you are very welcome at this point.... Unfortunately, no.:(
The only thing I can come up with now is to investigate and implement the authorization for the other frontends we would support? (i.e. for posix for example), but not sure if this makes a good deliverable.
(It is something we need though).
Ideas/suggestions from other people?
Dries
I'm rather late commenting on this, and I'm no security expert, but from my perspective I agree with the notion of de-emphasizing the DOS stuff in favor of other topics. I've always had the impression that DOS problems seem more critical to storage systems (or other services) that are open to the Internet at large. For the type of storage system we are building, I would expect things like unauthorized data access, how to tie in with external auth mechanisms, and how to migrate data on and off of storage safely to be bigger concerns. Some level of DOS exploration is good though, especially if there is some potential (for example) for an application to use DOS as a tool towards gaining unauthorized access, though. I don't know if that's a plausible possibility or not. -Phil