|
>I have had a request from a client to add security to media volumes. For >example, John can't use volume 123456. He would get a NOT AUTHORIZED to >this volume. This would mean that you could do with a media volume that >you can do with an object of the 400. The idea is to restrict certain >users to confidential data on volumes. >I would like to know what the 400 community thinks of this and if has any >value. It has validity. The tape management product we use has volume security but we don't use it. Problems I see with this are: 1.) There will be an increased workload for security 2.) The security may not match (most likely) OS/400 security. For example, OBJ#1 is secured from user on the AS/400. OBJ#2 is not secured. Both objects are on the same volume. What do you do, modify you backup and volume control? Our approach is to secure save and restore commands and to store tapes in a controlled environment. People who have access to these commands and this environment have to be trusted. Of course, there may be data and security issues that are more stringent for other folks. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.