Name: - Harsh Tripathi Roll No.:-B - 657 Date: - / /2022 AIM: To Study and Implement Security As A Service On AWS Theory
Name: - Harsh Tripathi Roll No.:-B - 657 Date: - / /2022 AIM: To Study and Implement Security As A Service On AWS Theory
EXPERIMENT NUMBER: 8
THEORY:
• AWS Trusted Advisor is an online tool that acts like a customized cloud expert,
helping you to configure your resources to follow best practices. Trusted
Advisor inspects your AWS environment to help close security gaps, and finds
opportunities to save money, improve system performance, and increase
reliability.
• AWS Account Teams provide a first point of contact, guiding you through your
deployment and implementation, and pointing you toward the right resources to
resolve security issues you may encounter.
• AWS Well-Architected Tool helps you review the state of your workloads and
compares them to the latest AWS architectural best practices. This free tool is
available in the AWS Management Console, and after answering a set of
questions regarding operational excellence, security, reliability, performance
efficiency, and cost optimization. The AWS Well-Architected Tool then
provides a plan on how to architect for the cloud using established best practices.
DEPARTMENT OF COMPUTER ENGINEERING
Q) How to enable encryption in a browser with the AWS
Encryption is a technique that can restrict access to sensitive data by making it
unreadable without a key. An encryption process takes data that is plainly readable or
process able (“plaintext”) and uses principles of mathematics to obscure the contents
so that it can’t be read without the use of a secret key. To preserve user privacy and
prevent unauthorized disclosure of sensitive business data, developers need ways to
protect sensitive data during the entire data lifecycle. Data needs to be protected from
risks associated with unintentional disclosure as data flows between collection,
storage, processing, and sharing components of an application. In this context,
encryption is typically divided into two separate techniques: encryption at rest for
storing data; and encryption in transit for moving data between entities or systems.
The first step of in-browser encryption is including a copy of the AWS
Encryption SDK for JavaScript with the scripts you’re already sending to the user
when they access your application. Once it’s present in the end-user environment, it’s
available for your application to make calls. To perform the encryption, the ESDK
will request a data key from the cryptographic materials provider that is used to
encrypt, and an encrypted copy of the data key that will be stored with the object
being encrypted. After a piece of data is encrypted within the browser, the cipher text
can be uploaded to your application backend for processing or storage. When a user
needs to retrieve the plaintext, the ESDK can read the metadata attached to the cipher
text to determine the appropriate method to decrypt the data key, and if they have
access to the KMS key decrypt the data key and then use it to decrypt the data.
CONCLUSION:
Hence, I have successfully studied and implemented Security as a Service on
AWS.