|
Posted by Roger Abell [MVP] on August 24, 2006, 10:01 pm
If you were Registered and logged in, you could reply and use other advanced thread options
nomorespameventhoughthejapanesespamgivesmeachuckle
Had I thought I was informing yourself I would have surely
approached it differently.
Cheers,
Roger
>I am not familiar wih AzMan but thanks for the info on it and I will try to
>check it out more.
>
> Steve
>
>
>> It might be fair to think of AzMan as a snapshot of MS thinking around
>> W2k3 release time of how the CAS model from .Net could grow to
>> become a full-fledge access control. What AxMan can do is implemented
>> below with groups (ok, or accounts) and using these subject to the
>> existing
>> DAC and CAS models.
>>
>> "nomorespameventhoughthejapanesespamgivesmeachuckle"
>>>
>>> Steven L Umbach wrote:
>>>> What you refer to are privileged groups that have been around since the
>>>> first version of NT [nothing new here] and could be considered roles.
>>>> But by
>>>> definition DAC allows the owner of the object to set permissions on the
>>>> object and that is the case on any NT based Windows operating system.
>>>> If Joe
>>>> Blow has sensitive data on his computer because of DAC he can give ANY
>>>> user/group including everyone access to that data regardless of the
>>>> users
>>>> job role.
>>>>
>>>> Steve
>>>
>>> Thanks a lot.
>>>
>>> Do you have in familiarity with the Authorization Manager Runtime:
>>>
>>> Overview (from Microsoft)
>>> The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server
>>> version of the Windows Server 2003 Authorization Manager Role-Based
>>> Access Control (RBAC) API.
>>> Windows Server 2003 family operating systems introduced the
>>> Authorization Manager RBAC framework which includes the Authorization
>>> Manager API and Role-based MMC snap-in Administration UI (Authorization
>>> Manager Snap-in UI is only available on Windows Server 2003 family
>>> operating systems and on the Windows Server 2003 Administration Pack
>>> for Windows XP.)
>>> The Authorization Manager API provides a simplified development model
>>> in which to manage flexible groups and business rules and store
>>> authorization policies.
>>> Storage in Active Directory requires the domain to be at Windows Server
>>> 2003 functional level.
>>> Using the Windows 2000 Authorization Manager Runtime you can build
>>> server applications to use the Authorization Manager Role-based access
>>> control model that run on Windows 2000 Server family operation systems.
>>>
>>> Will using this totally negate DAC? Is there any way to not use DAC
>>> within a Windows environment using either 1st or 3rd part snap-ins?
>>>
>>
>>
>
>
| 
XML site map