ACO

(redirected from Access Control Object)
AcronymDefinition
ACOAnt Colony Optimization
ACOAccountable Care Organization (health care)
ACOAssassin's Creed Odyssey (gaming)
ACOAutomobile Club de l'Ouest (Le Mans racing governing body)
ACOAustralian Chamber Orchestra (Sydney, Australia)
ACOAnimal Control Officer
ACOAircraft Certification Office (FAA)
ACOAdministrative Contract(ing) Office(r)
ACOAdministrative Contracting Officer
ACOA Clockwork Orange (movie/book)
ACOAmerican Composers Orchestra
ACOAction Chrétienne en Orient (French: Christian Action in the East)
ACOAir Cadet Organisation (UK)
ACOAction Catholique Ouvrière (French: Catholic Workers' Action)
ACOAssistant Chief Officer (UK Probation Services)
ACOAmerican College of Orgonomy
ACOArchitectural Conservancy of Ontario (Canada)
ACOAdministrative Consent Order
ACOAustralian College of Optometry (est. 1939)
ACOAction Object
ACOAnalog Central Office
ACOAirspace Control Order
ACOAlpha Chi Omega
ACOAnglican Communion Office
ACOAnnual Cost of Ownership (finance)
ACOAccess Control Object
ACOAmerican Cornhole Organization
ACOAutomatic Cut Off
ACOAir Officer Commanding
ACOAir Control Order
ACOAMP Communications Outlet
ACOAir Control Officer
ACOAllied Command Operation
ACOAdministrative Compliance Order
ACOArmy Contracting Officer (US Army)
ACOAtlantic Classical Orchestra (Fort Pierce, FL)
ACOAnimal Control Operations
ACOAssociation of Commissioned Officers
ACOAlarm Cut Off
ACOAir Coordination Order
ACOAlgorithms, Combinatorics and Optimization (academic program)
ACOAthlétic Club de l'Ondaine (French athletic club)
ACOArea Central Office (telecom)
ACOActual Contacts for Outlook (Microsoft)
ACOAuthenticated Ciphering Offset
ACOAccess Card Office (US DoD)
ACOAction Cancer Ontario
ACOAdditional Call Offering
ACOAssembly and Checkout Officer (US NASA)
ACOAuthorized Contracting Officer
ACOAirspace Coordination Order
ACOArts Computing Office (University of Waterloo)
ACOAssociation Canadienne des Optométristes (Canadian Association of Optometrists)
ACOAssociation Canadienne des Orthodontistes (Canadian Association of Orthodontists)
ACOAlternate Contracting Officer (US DoD)
ACOAustin Civic Orchestra (Austin, TX)
ACOATOMAL control officer (NATO)
ACOAcronym Control Officer
ACOAssociation of Canadian Orchestras
ACOAuthorized Certification Official (National Plant Protection Organization)
ACOAcademy of Clinical Oncology (continuing medical education provider)
ACOAir Combat Order
ACOAdvance Change Order
ACOAtomic Coordinating Office
ACOAlvarez Chamber Orchestra (UK)
ACOAdvanced Concepts Office
ACOAirfield Coordination Officer
ACOAutomated Console Operations
ACOArmy Cryptologic Operations
ACOAtomic-Cell Orbital
ACOAssociate Contracting Officer
ACOAverage Communication Overhead
ACOAngolan Community of Ontario (Canada)
ACOAssistant Contracts Officer
ACOAssistant Commanding Officer
ACOAction Cut-Out (switch)
ACOArea Compliance Officer
References in periodicals archive ?
If the access control object used as part of a MAC rule were to allow anyone other than a security officer to update it, users could evade the intention of mandatory control.
To what has already been defined, we add a boolean function d(o) which indicates whether an object o is subject to mandatory (MAC) or discretionary access control (DAC); this is a function d(o) on the object itself, rather than part of an access control object. We represent d(o) by a value tabulated within each object's primary catalog and do the same for a(o), which identifies the access control object protecting o, for o(o), which identifies the owner of o, and for r(o), which identifies the permission function to be used to interpret the access control information.
In summary, DACM behavior depends on whether or not a permission function and/or an access control object is defined for the object o, as shown in Table II.
-- ACCESSRULE identifies an access control object, a special ADF rule, or a null.
-- ACCESSRULE identifies the access control object to be automatically attached to items this subject creates;
Items are grouped into sets with common access control lists by the ACCESSRULE field in the ITEMS table; values in this field are the item identifiers of access control objects. Each access control object is interpreted by a permission function which it selects (Section 2.6) by fields in its catalog entry (Section 3.3) and must conform to rules specified by the author of this permission function.
Each stored object can bind both an access control object and a permission function and can choose its permission function either directly or via its access control object.
We believe that most users will create fewer than 10 lists with fewer than 10 subjects or groups in each, i.e., a large access control object collection will comprise 100 x [N..sub.u] table entries for [N.sub.u] users, using less than 1MB for 1000 users.
DACM structure follows object-oriented practice in that access control information is bound to an object by having the object point to an access control object and by having the access control object point to its interpretation method.
-- one or more classes would define access control information management; an instance of such a class would be what we have called an access control object;
-- any object needing protection would bind an access control object as an attribute, by calling a polymorphic ObjectBindAccessInformation operator during its creation; such a binding would persist until explicitly changed;
-- an access check would be a message passing the current subject and an integer to the associated access control object; such messages would be issued by the protected object's sensitive methods, i.e., implemented conventionally as part of the class definition of the protected object;
Full browser ?