Cisco ASA 5510 and Active Directory (part 2)

further questions on AD integrated VPN Authorisation - below is what I have theorised and need some help on so far....

ASDM -> Configuration -> AAA/Local Users -> AAA Server Groups

1.      AAA Server Group Setup (RAIDUS) to our IAS Server Internally (10.240.0.4) (This runs a policy that says only members of windows group VPN Users can authenticate)
2.      AAA Server Group Setup (LDAP) to our LDAP Server Internally (10.240.0.100) and basing its search on our LDAP Server Internally For Groups for the ASA to view

ASDM -> Configuration -> Network (Client) Access -> Dynamic Access Policies

1.      Create new policy for each network access requirement type
2.      Base Policy on AAA Attribute ldap.memberOf (AD Group Member)
3.      Ignore Endpoint attributes
4.      Set Action to Continue
5.      Apply Network ACL Filter

Thoughts and Questions
1.      From what I have read and the understanding I have of this, the following process is followed:
a.      User attempts a connection via VPN using the VPN Client.
i.      User must be a member of the AD Base Group of VPN Users of which IAS will then authenticate the user for the ASA
b.      Once the ASA has established that the user can authenticate it will establish a tunnel,
c.      The ASA will next apply the Dynamic Access Policies which contain further group membership rules and ACLs.

Now, if the above theory is correct, then there are a few things that need to be dealt with
a)      The default DAP Is set to Continue All connections. This is the last policy that is applied, so obviously, we would need to change this to Terminate All connections. If a match is found in a policy before the default is applied, then the connection will continue without processing the Default Access policy

Adding to this, the Network ACL Filters Assigned within the DAP Itself, will only allow ACLs that have specific Allow or specific Deny meaning that ACLs must be independently built for each group requirement, so if a member of VPN RDP Allowed is authenticated, it would need an ACL containing only allowed RDP traffic to certain servers. Same theory for each different server. We cant have an ACL with allow and deny together. Must be split (We can however have multiple ACLs assigned to each DAP)

How do we go about assigning new ACLs to just VPN Dial in sessions considering that our dial in users have a certain IP range specified by the ASA (172.X.X.X)? My concern is that I dont want these ACLs affecting anything bar VPN dial in and only want them applied to a group