{"title":"IEEE海量存储系统参考模型中的安全性","authors":"A. Hanushevsky","doi":"10.1109/MASS.1993.289775","DOIUrl":null,"url":null,"abstract":"The author discusses the origins of the distribution topology of the IEEE Mass Storage System Reference Model, how it affects security, and the methods that can be used to provide secure resource access. He also shows how certain security considerations emphasize the importance of particular Model-defined services and impose architectural constraints on those services. It is noted that the model's security problems stem from the client-centric distribution of various Model functions. These problems are heightened in Version 5 of the Model, in which any Model component is allowed to be distributed in a client-centric manner. While a distributed security scheme can provide an appropriate security environment, the relationships between Model components must be fully defined before any particular scheme can be recommended. Furthermore, it is critical that the correct authorization agents be identified with security, usability, and performance in mind. It is clear that, in certain cases, the Name Server becomes an important, if not focal, authorization agent. The challenge is to define a security protocol appropriate to the Model, as opposed to modifying the Model to fit current security schemes.<<ETX>>","PeriodicalId":225568,"journal":{"name":"[1993] Proceedings Twelfth IEEE Symposium on Mass Storage systems","volume":"7 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-04-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Security in the IEEE Mass Storage System Reference Model\",\"authors\":\"A. Hanushevsky\",\"doi\":\"10.1109/MASS.1993.289775\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The author discusses the origins of the distribution topology of the IEEE Mass Storage System Reference Model, how it affects security, and the methods that can be used to provide secure resource access. He also shows how certain security considerations emphasize the importance of particular Model-defined services and impose architectural constraints on those services. It is noted that the model's security problems stem from the client-centric distribution of various Model functions. These problems are heightened in Version 5 of the Model, in which any Model component is allowed to be distributed in a client-centric manner. While a distributed security scheme can provide an appropriate security environment, the relationships between Model components must be fully defined before any particular scheme can be recommended. Furthermore, it is critical that the correct authorization agents be identified with security, usability, and performance in mind. It is clear that, in certain cases, the Name Server becomes an important, if not focal, authorization agent. The challenge is to define a security protocol appropriate to the Model, as opposed to modifying the Model to fit current security schemes.<<ETX>>\",\"PeriodicalId\":225568,\"journal\":{\"name\":\"[1993] Proceedings Twelfth IEEE Symposium on Mass Storage systems\",\"volume\":\"7 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1993-04-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"[1993] Proceedings Twelfth IEEE Symposium on Mass Storage systems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/MASS.1993.289775\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"[1993] Proceedings Twelfth IEEE Symposium on Mass Storage systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MASS.1993.289775","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Security in the IEEE Mass Storage System Reference Model
The author discusses the origins of the distribution topology of the IEEE Mass Storage System Reference Model, how it affects security, and the methods that can be used to provide secure resource access. He also shows how certain security considerations emphasize the importance of particular Model-defined services and impose architectural constraints on those services. It is noted that the model's security problems stem from the client-centric distribution of various Model functions. These problems are heightened in Version 5 of the Model, in which any Model component is allowed to be distributed in a client-centric manner. While a distributed security scheme can provide an appropriate security environment, the relationships between Model components must be fully defined before any particular scheme can be recommended. Furthermore, it is critical that the correct authorization agents be identified with security, usability, and performance in mind. It is clear that, in certain cases, the Name Server becomes an important, if not focal, authorization agent. The challenge is to define a security protocol appropriate to the Model, as opposed to modifying the Model to fit current security schemes.<>