## 3 Simple Resource Algorithm
### Advertising Cloud Formulation
It is a trusted Party responsible for confirming the registration of Cloud Providers and certifying the capacity of their resources. The RAS ensures that only valid and adequately resourced Clouds participate in service migrations. Function of RAS in the Algorithm are:

* **Registration and Certification:** The RAS confirms the registration of Cloud Providers and certifies the capacity of resources available with the registered Cloud Providers. * **Request Verification:*
* When a request for resources is received from a Receiving Server (SA), the RAS verifies the resources based on specific criteria before approving the migration. Stage 2 of the RASP protocol therefore provides verification and certification. Once it receives the request from SA requested resources (SAreqr), the RAS verifies the resources based on the Algorithm below:
* 3. R \(\rightarrow\) SA: sign((CB, pkC, ResCB), pkS) [R \(\rightarrow\) SA: The Registry approves the advertisement (Advc) and sends a message to the Receiving Servers (SA), detailing the free resources (ResCB) with its signature]. Server RAS Formulation Algorithm 3 in detail:
* **Step 1-2 Verify Validity:*
* The RAS server verifies whether the CB is a valid cloud and if its Cloud resources are greater than the requested resources. If either condition is false, then it rejects the request and updates Server SA that CB is an invalid cloud. * **Step 2-5 Pass Conditions:*
* If the above conditions pass, then it sends an authenticated message to SA. This message confirms the approval of the resource migration. Server RAS Algorithm 4 Formulation in detail,
* **Step 1-2**: RAS server verifies whether it is a valid server and if Cloud resources are greater than the requested resources which is not equal 0. If either conditions are false, then it rejects the request and updates SA that its an invalid Cloud. * **Step 2-5**: If the above conditions pass, then it sends an authenticated message to SA. The RAS is essential for ensuring the integrity and efficiency of resource allocation in Cloud environments. It validates Cloud Providers, certifies their resources, and manages requests from Receiving Servers, ensuring only valid and adequately resourced Clouds participate in service migrations. This multi-step verification process helps maintain a secure and reliable resource allocation framework. ## 4 RASP Protocol--An Overview

This protocol has three roles: Server SA on Cloud CA, Cloud CB, and Registry. The Resource Allocation Security protocol (RASP) is broken into four stages. In the first stage, it uses the Resource Allocation Algorithm to manage cloud advertisements [11]. In addition, the proposed protocol was tested by ProVerif. The protocol is shown in Figure 4 as follows: Stage 1 corresponds to step 1 of the protocol; Stage 2 corresponds to steps 2-7; Stage 3 corresponds to steps 8-11, and finally, Stage 4 corresponds to step 12. The RASP protocol is followed in exactly the same way as outlined below and shows the steps for Cloud-to-Cloud migration of services. ### General Notations

Table 2 shows the parameters used in the RASP protocol. *Stage 1: Advertisement** : Server SA receives advertisements from Cloud CB advertising its resources. 1. CB \(\rightarrow\) SA: Advc (CB, ResCB)
2. **Stage 2: Authentication of SA and CB as well as migration request and response**: Server SA first requests the RAS/Registry to authenticate Cloud CB and its resources. In Step 3, the Registry (R) authenticates Cloud CB. In Step 4, Server SA sends a migration request to Cloud CB. In Step 5, Cloud CB sends a request to the Registry to verify that Server SA's request for resources is valid. In Step 6, the Registry replies to Cloud CB. In Step 7, Cloud CB sends the migration response back to Server SA. 2. SA \(\rightarrow\) R: (SA, CB, ResCB)pkR

3. R \(\rightarrow\) SA: sign((CB, pkC, ResCB), pkS)

4. SA \(\rightarrow\) CB: aenc ((Ns, SA, ResSA), pkC)

5. CB \(\rightarrow\) R: (CB, SA, ResSA)pkR

6. R \(\rightarrow\) CB: sign((SA, pkS, ResSA), pkC)

7.