XACML Examples
XACML Examples

Example Web PEP
Web Policy Enforcement Point 

 Use case example 

 We want to define a policy to restrict access to some pages of the Soffid console. 

 The users who are assigned to the SOFFID_RRHH role (from this point forward: end-users) will have limitations to access to some Soffid console pages: 

 

 The end-users who belong to the "enterprise" group as primary group, could not access to the groups page. 

 The end-users could not access to role page. 

 En other cases permit access. 

 

 XACML Editor 

 Policy set 

 First of all, we define a policy set.  

 

 Policy 

 Then, we can define a policy to manage the access. We need to define the subject, in that case users with SOFFID_RRHH role assigned. 

 Also, we can define a variable that contains the group name to establish the restrictions. 

 

 Rule 1 

 

 The end-users who belong to the "enterprise" group as primary group, could not access to the groups page. 

 

 

 Rule 2 

 

 The end-users could not access to role page. 

 

 

 Rule 3 

 

 En other cases permit access. 

 

 

 Download XML 

 You can download a XML file with the example: policy-TestWebPEP.xml 

 Configure PEP 

 

   

  

Example Role centric PEP
Role centric Enforcement Point 

 Use case example 

 We want to define a policy to restrict access to the Soffid console role's page ( MainMenu  >  Administration  >  Resources > Roles ) . 

 The users who belong to the "enterprise" group as primary group (from this point forward:  end-users ) will have limitations to perform some actions on the Soffid console roles page. 

 

 The end-users could query all the roles information. 

 The

 end-users  could update any role in the information systems "ERP RRHH" 

 The

 end-users  could not create any role. 

 The

 end-users  could not delete any role. 

 

 XACML Editor 

 Policy set 

 First of all, we define a policy set. We need to define the subject, in that case users who belong to "enterprise" as primary group. 

 

 Then, we can define a policy to manage the different actions that the end-users could perform. 

 

 Policy 

 The policy will apply to an only one user. That policy will be to protect the role resource. 

 

 Rule 1 

 

 The end-users could query all the roles information. 

 

 We define the rule that allow to the end-users to query all the roles information. 

 

 Rule 2 

 

 The  end-users  could update any role in the information systems "ERP RRHH" 

 

 

 Rule 3 

 

 The

 end-users  could not create any role. 

 

 

 Rule 4 

 

 The

 end-users  could not delete any role. 

 

 

 Download XML 

 You can download a XML file with the example: policy-TestRoleCentricPEP.xml 

 Configure PEP 

 

   

  

Example Dynamic role PEP
Dynamic role Enforcement Point 

 Use case example 

 We want to define a policy to restrict access to the Soffid console user's page ( MainMenu  >  Administration  >  Resources  >  Users) . 

 The users who are assigned to the SOFFID_RRHH role (from this point forward: end-users ) will have limitations to perform some actions on the Soffid console users page: 

 

 The end-users only be able to query the information about the users who belong to the same primary group that them.  

 The end-users only be able to update the users with internal user type. 

 The end-users could not delete any user record. 

 

 XACML Editor 

 Policy set 

 First of all, we define a policy set. We need to define the subject, in that case users with SOFFID_RRHH role assigned. 

 

 Then, we can create the policies, in that case, we can create three policies, one for each operation that we want to manage. 

 

 Policies 

 We can define a policy for each operation, to permit or deny access. 

 Also, we can define a variable that contains the end-user primary group in order to use it when we define the conditions. 

 Policy1 

 

 The end-users only be able to query the information about the users who belong to the same primary group that them.  

 

 We need to define two rules, one to permit and other to deny access. 

 

 Rules 

 We define the rule that allow to the end-user to query users information who belong to the same primary group that the end-user. 

 

 Then, we define the rule that denies access to end-users to query users information. 

 

 Policy 2 

 

 The end-users only be able to update the users with internal user type. 

 

 We need to define two rules, one to permit and other to deny access. 

 

 Rules 

 We define the rule that allow to the end-users to update users information who are internal users. 

 

 Then, we define the rule that denies access to end-users to update users information. 

 

 Policy 3 

 

 The end-users could not delete any user record. 

 

 We need to define only one rule to deny access. 

 

 Rules 

 We define the rule that deny to the end-user delete any user. 

 

 Download XML 

 You can download a XML file with the example: policy-TestDynamicPEP.xml 

 Configure PEP 

 

  

Example Password Vault PEP
Password Vault Policy Enforcement Point 

 Use case example 1 

 We want to define a policy to restrict access to the Soffid Password Vault. 

 The users who are assigned to the SOFFID_ADMIN role (from this point forward: end-users) will have limitations to perform some actions on the folder "demoFolder" of the Soffid Password Vault 

 

 The end-users only be able to access the accounts of that folder on labor time. The permissions will be denied in another case. 

 

 Policy set 

 First of all, we define a policy set that could contain other policy sets and policies. 

 

 

 Policy set 2 

 Then, we can create another policy set as a child of the former to manage the folder and to define the subject, in that case, users with SOFFID_ADMIN role assigned. 

 

 That policy set will contain the policies. 

 

 Policies 

 Policy 1 

 

 The end-users only be able to access the accounts of that folder on labour time. The permissions will be denied in other case. 

 

 

 Rule  

 We define the rule that permit access to the end-user

 

 

 And we define other to deny access. 

 

 Use case example 2 

 We want to define a policy to restrict access to the Soffid Password Vault. 

 The users who are assigned to the SOFFID_ADMIN role (from this point forward: end-users) will have limitations to perform some actions on the folder "demoFolder" of the Soffid Password Vault 

 

 The end-users only be able to access the accounts of that folder on labor time. The permissions will be denied in another case. (Use case example 1) 

 To connect there are some obligations to fulfill 

 

 

 Use case example 3 

 We want to define a policy to restrict access to the Soffid Password Vault. 

 The access will be denied on Sunday. 

 

 Download XML 

 You can download an XML file with the example: policy-demoFolder.xml 

 Configure PEP