The rapid advances in cloud computing has introduced a variety of security issues; each requires certain skills and knowledge. While developing business services requires conducting analysis and design for the business activities that does not include common security functions for these services. Currently there is no framework existing from the logical level for securely orchestrating of cloud services in a heterogeneous environment. We are addressing in the paper a clear separation of concerns between the "business logic" and the "security logic" in order for any service implementing the proposed security service to be considered a high level secured service in terms of access and communication in order for it to be widely used and acceptable. A development model is proposed to write secured services without burdening the developer of continuously rewriting security routines.

Securing data is always of vital importance and because of the critical nature of cloud computing and large amounts of complex data it carries, the need is even important. Cryptographic algorithms are one of the most important areas in security. They are processes that protect data by making sure that unwanted people can't access it. Unfortunately, when the dataset size is huge, both memory use and computational cost can still be very expensive. In addition, single processor's memory and CPU resources are very limited, which make the algorithm performance inefficient.Security issues investigated in [1] requires that applications and services be capable of supporting a variety of security functionality such as authentications, authorization, and auditing and so on. Those mechanisms are likely to evolve over time because new mechanisms are developed and changed. So developer must avoid embedding security mechanisms statically and manually in order to adapt to changing requirements. The Cloud security service proposed casts those security functionalities in to a service. These strategy allows interfaces to be defined and permits an application to outsource security functionality from the cloud security service to fit it's current need. We are addressing in this paper a clear separation of concerns between the "business logic" and the "security logic" in order for any service implementing the proposed security service to be considered a high level secured service. This model is targeting developers willing to write secured services without burdening the developer of continuously rewriting security routines, and only be concerned with the business logic of the service, on the other hand it targets the end user that need to use the service as it is, and get the result or output.