Abstract
This
paper aims to compare the strengths of various encryption algorithms and the
access control methods in AWS S3. One important factor in the use of cloud
storage is data privacy and security whenever there is an investment in cloud
storage. Based on an analysis of various encryption techniques as well as the
various modes of client-oriented access control methods, this paper offers
blueprints for the best practices of data security in AWS S3.
Keywords: AWS S3, Data Privacy, Encryption Algorithms, Access Control Mechanisms, Cloud Security
1. Introduction
Cloud preservation has
become a crucial topic in current research since many organisations share their
data in cloud storage systems. AWS S3 commonly known as Amazon Simple Storage
Service is one of the most popular cloud-based storage solutions providing
Storage as a Service. However, there is a security issue when storing data
through AWS S3. This paper seeks to discuss several encryption algorithms and
several access control measures to increase S3 data privacy in AWS.
2. Literature Review
A. Cryptographic
Methods
A comparative
evaluation of various forms of cryptographic techniques adopted by cloud
service suppliers with a special focus on the relevance of encryption as a
shield in data protection1. Different
methods of data security and privacy preservation for cloud storage, where
encryption is found to be a prominent solution2.
Homomorphic encryption can be applied to protect data privacy in clouds as computations can be made on the encrypted database without the need to decrypt them11. One technique of applying data privacy can be performed with the use of symmetric cryptographic algorithms that establish the efficiency of such methods in protecting cloud data stored on other servers12.
Figure 1: Cryptographic Technique.
Figure 2: Homomorphic Encryption.
B. Access Control Mechanisms
Security measures are a critical component that is required to implement in implement cloud environment specifically AWS S3. Although RBAC is a simple solution for user permission, it is the same as the previous one and involves roles, it implies overprivileged users11. Attribute-Based Access Control (ABAC) is more refined than the previous models; focuses on user attributes as well as resource characteristics to set the access privilege of a user, which makes it more secure12. The client-centric approach of access control entails making data encrypted on the client side and only the permitted client can decrypt the data which means more security1 3. The method of access control with an emphasis on the client is an effective way to increase cloud security24.
The issue of security vs. convenience in the context of a/c and its frameworks13. A form of encryption, attribute-based encryption (ABE) with multiple benefits for the secure access of data13. Altogether these mechanisms considered some security issues in AWS S3 according to the literature.
Fig 3: ABE.
3. Methodology
A. Encryption
Algorithms
In the method, the
authors have compared various encryption algorithms based on their security
measures, computational capability, and simplicity considering numerous
research articles.
Advanced Encryption Standard (AES): AES is well known to be highly secure and also efficient which is a huge benefit. It employs the use of symmetric key encryption, which despite being quite efficient in terms of computation, is, however, closely associated with key management issues that if not managed properly, can lead to compromised security. AES is used in those applications that require higher performance because the computing overhead of AES is low12.
Figure 4: AES.
Rivest-Shamir-Adleman (RSA): RSA is a criterion of symmetric encryption key distributing high security through public and private keys. Although it provides good security, it is rather slow, and thus not recommended for real-time scenarios6. RSA is used commonly for the encryption of data and the distribution of the keys8.
Attribute-Based
Encryption (ABE): In ABE,
optional attributes can be tied with a Key so that the number of access
conditions can be controlled precisely8.
This also offers flexibility in the policies of access control since a complex
policy can easily be implemented, and the security of the data is boosted since
only people with correct attributes in the equation can decrypt the data.
B. Access Control Mechanisms
The methodology reviews several emphasis points whereby different kinds of access controls used in AWS S3 are uniformly assessed concerning the security strength of the access control measure, usability and implementation to a large extent from the literature.
Role-Based Access Control (RBAC): RBAC distributes permissions based on the user roles, thus easy to manage and no overhead in control. On the other hand, the authors found that when roles are not well controlled, the system can end up with overprivileged users21. RBAC works well where there is a clear role hierarchy and clear definitions of permissions15.
Figure 5: RBAC.
Attribute-Based Access Control (ABAC): Due to its utilization of characteristics such as user characteristics and type of a resource as its basic control parameter, ABAC finally offer fine-grained access control7. It also improves security in a way that provides the flexibility of gaining access according to many factors, yet at the same time provides secure and specific control20,23. ABAC is most appropriate in environments that are constantly changing since access requirements are also frequently changing10,18.
Client-Centric Access Control: This mechanism involves encrypting data at the client level to make sure that only those clients should be able to decrypt the said data18. This approach improves security by ensuring that the data in transit as well as the data at rest is encrypted all the time6. This type of access control is good if end-to-end security is essential, especially for the clients.
4. Analysis and Results
A. Performance
Evaluation
Assessing the
performance of the encryption algorithms, it is clear that AES has the least
overhead and is thus recommended where performance is key. Relatively, RSA
provides high security compared to the other two while it is more
resource-consuming and thus not very appropriate for real-time use9. Attribute-based encryption allows much more
flexible and precise access control of the encrypted contents but the attribute
management should be done precisely10.
Another disadvantage of RSA draws focus on the high computational costs of
modern RSA in cloud computing15.
Proper encryption mechanism to avoid them being a performance degrader22.
B. Security Assessment
The security analysis of encryption algorithms reveals that AES, RSA and ABE have good security in guarding AWS S3. These algorithms’ effectiveness is highly dependent on the key management practices that have been adopted. AES is highly secure and it incurs small computational costs so it is appropriate for a whole lot of applications9. RSA although very secure, needs to manage keys in a very efficient manner due to the use of asymmetric keys4. ABE also guarantees a more precise level of access control; moreover, increased safety is achieved when attributes are linked to the data encryption keys7. Encryption and access control measures should be well-initially put in place and implemented for successfully eliminating security threats in cloud environments17. Furthermore, the significance of the key management is to keep the data safe10.
5. Implementation in AWS S3
AWS S3 offers different encryption models such as SSE and CSE where the above statement is partially correct because AWS S3 provides SSE and other encryption models not mentioned in the statement. SSE enables the AWS to manage the encryption keys; while this facilitates key management, it reduces the ownership since it is trusted by the AWS19. On the other hand, CSE allows clients to retain key control all the time and this provides the greatest security though the management may be slightly complicated25.
A. Server-Side Encryption (SSE)
AWS S3 provides several features for server-side encryption (SSE) for the purpose of increasing the scope of security. SSE-S3 entails the aspect where AWS holds the keys to the encryption; they are easy to use, and data is well protected. SSE-KMS exploits AWS Key Management Service (KMS) to perform key management and provides extra security features and audited logs [5]. The capabilities of SSE-C comprise the opportunity for customers to transmit their keys for encryption which means the ultimate control of the process14,16.
Figure 6: Encrypted File System.
B. Client-Side Encryption (CSE)
AWS S3 CSE enables customers to encrypt data in their client application before uploading to S3, which means data is encrypted at customers’ sites and throughout the lifecycle of data in S3. This means is a lot more secure as the keys for the encryption are not held by AWS but instead, it is held by the client10,14. This approach is particularly beneficial for raw data as it incorporates various levels of keys for purposed data extraction hence only the authorized personnel can obtain the sensitive data7,12. CS encryption also improves data security since the users’ data cannot be accessed by third parties during transmission and storage20. This method also helps to decrease risks connected with server-side vulnerabilities as well as possible breaches at the level of the service provider19,22.
6. Conclusion
This paper’s findings
suggest that AWS S3 is best encrypted with AES and that ABAC and client-centric
access control methods offer the highest levels of security. This approach
explains how client-side encryption helps to solve various issues related to data
security at the different stages of the data life cycle. In cryptography, often
is said that key management is half the battle which implies that managed keys
are secure keys. Therefore, future research should concentrate on the option of
automating key management for client-side encryption. This paper therefore
establishes a correlation between the efficiency of the encryption algorithms
and access control mechanisms to improve on the data privacy in cloud storage
systems.
7. References