[1]} [2]} [3]} [4]} [5]} [6]} grant access to resources solely based on capability tokens created for each policy. Further, employing CapBAC models in authorisation processes is a time-consuming task requiring generating and distributing tokens (or capabilities) to all subjects for each resource. It is also possible that selecting a specific capability while making a request overburdens the network, which significantly impacts system performance when there are many users. Finally, the authorisation methods based on ABAC models have limitations in terms of achieving the privacy of the attributes [7]} [8]} [9]} [10]} [11]}, collecting and managing the large number of policies and achieving the flexibility and fine-grained level of access rights [8]} [9]} [11]} .
