Return to User28_SecurityLevel.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIMPrelim28 |
File: [Pegasus] / pegasus / Schemas / CIMPrelim28 / Attic / User28_SecurityLevel.mof
(download)
Revision: 1.1, Tue Sep 2 17:59:16 2003 UTC (20 years, 10 months ago) by tony Branch: MAIN CVS Tags: test, pegasus25BeforeLicenseUpdate, local, TEST, SLPPERFINST-root, SLPPERFINST-branch, RELEASE_2_4_FC_CANDIDATE_1, RELEASE_2_4_3, RELEASE_2_4_2, RELEASE_2_4_1-BETA3, RELEASE_2_4_1-BETA2, RELEASE_2_4_1-BETA1, RELEASE_2_4_1, RELEASE_2_4_0-RC3, RELEASE_2_4_0-RC2, RELEASE_2_4_0, RELEASE_2_4-root, RELEASE_2_4-branch, RELEASE_2_3_2-testfreeze, RELEASE_2_3_2-root, RELEASE_2_3_2-releasesnapshot, RELEASE_2_3_2-branch-freeze, RELEASE_2_3_2-branch, RELEASE_2_3_1-root, RELEASE_2_3_1-branch, RELEASE_2_3_0-root, RELEASE_2_3_0-msg-freeze, RELEASE_2_3_0-branch, PRE_LICENSE_UPDATE_2003, POST_LICENSE_UPDATE_2003, PEP217_PRE_BRANCH, PEP217_POST_BRANCH, PEP217_BRANCH, PEP213_SIZE_OPTIMIZATIONS, MONITOR_CONSOLIDATION_2_5_BRANCH, IBM_241_April1405, CQL_2_5_BRANCH, CHUNKTESTDONE_PEP140 PEP 73 - Add CIMPrelim28 schema |
// =================================================================== // Title: User-Security Security Level // Filename: User28_SecurityLevel.mof // Version: 2.8 // Release: Preliminary // Date: 05/30/2003 // =================================================================== // Copyright 1998-2003 Distributed Management Task Force, Inc. (DMTF). // All rights reserved. // DMTF is a not-for-profit association of industry members dedicated // to promoting enterprise and systems management and interoperability. // DMTF specifications and documents may be reproduced for uses // consistent with this purpose by members and non-members, // provided that correct attribution is given. // As DMTF specifications may be revised from time to time, // the particular version and release date should always be noted. // // Implementation of certain elements of this standard or proposed // standard may be subject to third party patent rights, including // provisional patent rights (herein "patent rights"). DMTF makes // no representations to users of the standard as to the existence // of such rights, and is not responsible to recognize, disclose, or // identify any or all such third party patent right, owners or // claimants, nor for any incomplete or inaccurate identification or // disclosure of such rights, owners or claimants. DMTF shall have no // liability to any party, in any manner or circumstance, under any // legal theory whatsoever, for failure to recognize, disclose, or // identify any such third party patent rights, or for such party's // reliance on the standard or incorporation thereof in its product, // protocols or testing procedures. DMTF shall have no liability to // any party implementing such standard, whether such implementation // is foreseeable or not, nor to any patent owner or claimant, and shall // have no liability or responsibility for costs or losses incurred if // a standard is withdrawn or modified after publication, and shall be // indemnified and held harmless by any party implementing the // standard from any and all claims of infringement by a patent owner // for such implementations. // // For information about patents held by third-parties which have // notified the DMTF that, in their opinion, such patent may relate to // or impact implementations of DMTF standards, visit // http://www.dmtf.org/about/policies/disclosures.php. // =================================================================== // Description: The User Model extends the management concepts that // are related to users and security. // This file defines the concepts and classes related to // Security Levels. // // The object classes below are listed in an order that // avoids forward references. Required objects, defined // by other working groups, are omitted. // =================================================================== // Change Log for v2.8 Preliminary - // CR1011 - Created this file. // =================================================================== #pragma Locale ("en_US") // ================================================================== // SecuritySensitivity // ================================================================== [Experimental, Version ("2.7.1000"), Description ( "Defines a security sensitivity level, which can be associated " "with a ManagedElement. A simple example is to define security " "levels representing 'low sensitivity', 'moderately sensitive', " "'high sensitivity' and 'national security' classification " "levels. An element is assigned a security level via the " "association, ElementSecurityLevel. It can be assigned to any " "ManagedElement, such as Locations, Identities, Roles, Systems, " "Services and LogicalFiles.\n" "\n" "A security level is determined by a business, organization " "and/or government based on the need to protect data and " "entities from attack, loss, abuse or unauthorized disclosure, " "and the ramifications if this protection is not maintained.") ] class CIM_SecuritySensitivity : CIM_ManagedElement { [Key, Description ( "Within the scope of the instantiating Namespace, InstanceID " "opaquely and uniquely identifies an instance of this " "class. In order to ensure uniqueness within the NameSpace, " "the value of InstanceID SHOULD be constructed using the " "following 'preferred' algorithm:\n" "<OrgID>:<LocalID>\n" "Where <OrgID> and <LocalID> are separated by a colon ':', " "and where <OrgID> MUST include a copyrighted, trademarked " "or otherwise unique name that is owned by the business " "entity creating/defining the InstanceID, or is a registered " "ID that is assigned to the business entity by a recognized " "global authority (This is similar to the <Schema " "Name>_<Class Name> structure of Schema class names.) In " "addition, to ensure uniqueness <OrgID> MUST NOT contain a " "colon (':'). When using this algorithm, the first colon to " "appear in InstanceID MUST appear between <OrgID> and " "<LocalID>.\n" "<LocalID> is chosen by the business entity and SHOULD not " "be re-used to identify different underlying (real-world) " "elements. If the above 'preferred' algorithm is not used, " "the defining entity MUST assure that the resultant " "InstanceID is not re-used across any InstanceIDs produced " "by this or other providers for this instance's NameSpace.\n" "For DMTF defined instances, the 'preferred' algorithm MUST " "be used with the <OrgID> set to 'CIM'.") ] string InstanceID; [Description ( "A string defining the security sensitivity level.") ] string SecurityLevel; }; // ================================================================== // ElementSecuritySensitivity // ================================================================== [Association, Experimental, Version ("2.7.1000"), Description ( "This association relates a security sensitivity level to a " "ManagedElement. It describes the level assigned to the " "element.") ] class CIM_ElementSecuritySensitivity { [Key, Description ( "The security sensitivity level of the element.") ] CIM_SecuritySensitivity REF SecurityLevel; [Key, Description ( "The element which is assigned a sensitivity level.") ] CIM_ManagedElement REF ManagedElement; }; // =================================================================== // end of file // ===================================================================
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |