Link to home
Start Free TrialLog in
Avatar of Centamin-SGM

asked on

Authentication, Authorization, Accounting procedures from Microsoft side.

Hi All,

you all know about AAA  from Cisco side, that you can authenticate, authorize, and Account all access to the Network device through radius, or tacacs+ server.
the same thing happens from Microsoft side. such as every access the user can make to any resource is controlled through active directory, which in my point of view is AAA schema. the user first authenticates to the server required, then get authorized to access the required resources, then his access is getting logged.

what I'm looking for is. any articles or documents that provides detailed explanation about the procedures used for AAA from Microsoft side. like Exchange, File Server, print server, SharePoint resources access rules.

any help is appreciated.

Avatar of btan

Microsoft has a listing of Infrastructure Planning and Design (IPD) for its portfolio which is useful. You may want to check out the NAP, Forefront Identity mgmt, Forefront UAG. I see the NAP as the first guardian to route as RADIUS  (with NAP incorporated with necessary extension DLLs) for other AAA entity check if need to and enforce consistent NAP client to be check prior to granting access to resource mentioned with a cleared remediation health state (using Network Access Protection)

e.g. NPS architecture
e.g. Example 1: Validate Health of NAP Client for IPsec Communication
Avatar of Centamin-SGM


Thanks btan for your comment,
but actually, I have Cisco ISE installed and Access control is already applied.
and I use Cisco ISE as a radius server for authenticating device Admins too.
what I'm trying to clarify is that, when the end user wants to access any resource in the network, there many steps required for the user to get access.
1. authentication through active directory.
2. authorization to get access to whatever the resources required.
3. accounting of what he has done.

that's what I'm looking for, the hierarchy of authentication, Authorization, accounting from Microsoft view.

thanks and regards.
Avatar of Rich Rumble
Rich Rumble
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks rich,
now I've got the point.

Microsoft has advice on doing these activities, but not the holistic approach of AAA.They recommend you do them around critical infrastructure and data, but AAA isn't how they label it. The concepts are the same, but then the auditing piece, at least where you and I would review what happened, isn't easy without a SEIM or some 3rd party log parsing software.
in fact NPS is ike ISE on the basic AAA. so the IDP will still help.

1. ISE will perform LDAP call to AD which will then verify against the credential pass over, this will be as per like "login" into your machine in domain. The LDAP filter CN for matching username tends to be the usual "cn=user" group, with the attribute as per in the entity field such as displayname etc. There is no much different from Microsoft usual AD check. Probably to note that the DNS, NTP will need to be synchronised as well since ISE is supposed to joined the AD domain too.

2. ISE ACL is based on RADIUS-vendor dictionaries that comes with Microsoft support as well. So when access to the authenticated user is successful, it is as if the login is alright and when the usual Windows security permission for file/folder (NTFS) will apply with ISE passing the identity to the resource requested.

3. Accounting is the usual audit log and security/appl/system event log that the domain controller will be tracking as well.
Thanks Guys for your support.

much appreciated.