HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

5 Security The security model used by ABS and MDMS is designed to provide flexibility in both the level of security and ease-of-use. ABS uses the MDMS security model, which is based on two main elements: • Rights - The assignment of individual rights to particular users or classes of users that allow them to perform specific operations across the domain. Rights allow users to perform operations on all objects or certain object classes across the domain. This is a task-based form of security. • Access Control - The assignment of access control is on a per-object basis, and allows specific users to perform specific types of operations on the object. This is an object-based form of security. In addition, you can assign your MDMS domain one of three levels of access-control based security as follows: • No Access Control - As the name implies, MDMS and ABS perform no access control based checking, even if individual objects have access control entries defined. However, rights continue to be checked. • Loose Access Control - This option supports access control checking on objects, but only on those objects that have at least one access control entry. If there is at least one entry, access to the object is restricted to users with access control entries supporting the requested access. With objects with no access control entries, access to the object is implicitly granted. • Tight Access Control - Designed for secure environments, this option supports access control checking on all objects. If there is at least one access control entry on an object, access to the object is restricted to users with access control entries supporting the requested access. With objects with no access control entries, access to the object is implicitly denied.This basically requires that all objects have appropriate access controls to be defined for the object to be used. Certain domain users may access normally inaccessible objects to prevent accidental lock-out due to insufficient access controls. In general, the security model requires that both rights and access control are applied to users wanting to perform operations. In other words, having the “super” right MDMS_ALL_RIGHTS does not necessarily mean that you can do anything - any access control restrictions must also be satisfied. This chapter discusses the security model in more detail. Security 5–1

5<br />

Security<br />

The security model used by ABS and MDMS is designed <strong>to</strong> provide flexibility in both the level<br />

of security and ease-of-use. ABS uses the MDMS security model, which is based on two main<br />

elements:<br />

• Rights - The assignment of individual rights <strong>to</strong> particular users or classes of users that allow<br />

them <strong>to</strong> per<strong>for</strong>m specific operations across the domain. Rights allow users <strong>to</strong> per<strong>for</strong>m operations<br />

on all objects or certain object classes across the domain. This is a task-based <strong>for</strong>m of<br />

security.<br />

• Access Control - The assignment of access control is on a per-object basis, and allows specific<br />

users <strong>to</strong> per<strong>for</strong>m specific types of operations on the object. This is an object-based <strong>for</strong>m<br />

of security.<br />

In addition, you can assign your MDMS domain one of three levels of access-control based<br />

security as follows:<br />

• No Access Control - As the name implies, MDMS and ABS per<strong>for</strong>m no access control based<br />

checking, even if individual objects have access control entries defined. However, rights<br />

continue <strong>to</strong> be checked.<br />

• Loose Access Control - This option supports access control checking on objects, but only on<br />

those objects that have at least one access control entry. If there is at least one entry, access<br />

<strong>to</strong> the object is restricted <strong>to</strong> users with access control entries supporting the requested<br />

access. With objects with no access control entries, access <strong>to</strong> the object is implicitly granted.<br />

• Tight Access Control - Designed <strong>for</strong> secure environments, this option supports access control<br />

checking on all objects. If there is at least one access control entry on an object, access<br />

<strong>to</strong> the object is restricted <strong>to</strong> users with access control entries supporting the requested<br />

access. With objects with no access control entries, access <strong>to</strong> the object is implicitly<br />

denied.This basically requires that all objects have appropriate access controls <strong>to</strong> be defined<br />

<strong>for</strong> the object <strong>to</strong> be used. Certain domain users may access normally inaccessible objects <strong>to</strong><br />

prevent accidental lock-out due <strong>to</strong> insufficient access controls.<br />

In general, the security model requires that both rights and access control are applied <strong>to</strong> users<br />

wanting <strong>to</strong> per<strong>for</strong>m operations. In other words, having the “super” right MDMS_ALL_RIGHTS<br />

does not necessarily mean that you can do anything - any access control restrictions must also be<br />

satisfied.<br />

This chapter discusses the security model in more detail.<br />

Security 5–1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!