Beginning AWS Security
Apress (Verlag)
978-1-4842-9680-6 (ISBN)
You'll start by understanding why security is important in the cloud and then review the relevant services offered to meet an organization's needs. You'll then move on to the finer points of building a secure architecture and take a deep look into the differences of responsibility of managed services and those that allow customers more control.
With multiple AWS services available, organizations must weigh the tradeoffs between those that provide granular control (IaaS), a managed service (PaaS), delivering applications remotely over the internet instead of locally on machines (SaaS). This book will help you to identify the appropriate resources and show you how to implement them to meet an organization's business, technical, and security perspective in the Cloud Adoption Framework. Finally, you'll see how organizations can launch a secure and optimized cloud architecture and use monitoring tools to be proactive in security measures.
With Beginning AWS Security, you'll understand frameworks, models, and the services needed to build a secure architecture.
You will:
- Review the similarities and differences between cloud and traditional computing. See how security changes when using on-site, hybrid, and cloud models
- Develop an understanding that security is not "one and done"
- Reinforce the need for updates and monitoring as a continued part of AWS security
Cloud computing architects, security professionals, security engineers, and software professionals interested in Cloud security.
Tasha Penwell is an AWS Educator, AWS Authorized Instructor, solutions architect, and community builder with a focus on security. In her career, she served as the computer science program manager for a community college in Ohio. Tasha has trained professionals on AWS, web development and data analytics. She is the founder and educator of Bytes and Bits, an organization that provides computer science education in Ohio and West Virginia. She is an active presenter and hosts computer science workshops on subjects like cloud computing at high schools around the country.
Chapter 1: Why Do I Care About Security? Isn't that AWS's problem?Chapter Goal: Identify why security is important in the cloud.No of pages: 40 -50 pagesSub -Topics1.Introduce some real life security breaches and outcomes that have happened in the cloud.2.Describe how AWS provides resources to build a cloud architecture but it's important to understand the tradeoffs of each service.3.Introduce the Shared Responsibility Model (covered more in Chapter 2)4.Introduce the Well-Architected Framework (will be used as reference throughout the book)5.Describe the similarities and differences between cloud and traditional computing.
Chapter 2: Who is Responsible Again?Chapter Goal: Develop an understanding of the Shared Responsibility Model and the tradeoffs of responsibilities based on services used.No of pages: 40 -50Sub - Topics1. Detailed overview of the Shared Responsibility Model2. Elaborate what is meant by "tradeoffs" and why understanding this is important.3. Review of AWS's security precautions 4. Align how the Well-Architected Framework supports the Shared Responsibility Model5.Describe the purpose and responsibilities for Identity and access management
Chapter 3: How Do I Build a Secure Architecture?Chapter Goal: Dive deeper into the differences of responsibility of managed services and those that allow customers more control. Identify tradeoffs on specific categories.No of pages : 40 - 50Sub - Topics: 1.Identify and understand services, responsibilities, and tradeoffs for computing services.2.Identify and understand services, responsibilities, and tradeoffs for storage services.3. Identify and understand services, responsibilities and tradeoffs for networking services.4. Identify and understand services, responsibilities and tradeoffs for database services.6.Identify and understand services to protect data at rest and in transit.7.Identify and understand services to monitor access and notifications.
Chapter 4: Security is Not Built in a DayChapter Goal: Develop an understanding that security is not "one and done" and that updates and monitoring is a continued part of AWS security.No of pages: 40 - 50Sub - Topics: 1.Identify and describe what it means to be proactive and reactive in security.2.Identify and implement monitoring services into architecture 3.Identify and understand the costs of the monitoring services4.Identify how to make updates and patches to software - and who is responsible for what.
Chapter 5: Is This the End?
Chapter Goal: Reinforce the need for lifelong learning. Just as security is not a "one and done", learning should be continuous as well. No of pages: 10 - 20Sub - Topics: 1.Identify resources available to continue learning from AWS (AWS Educate, AWS Academy, AWS Skillbuilder)2.Identify resources available to continue learning from the publisher3.A final review of the Shared Responsibility Model.4.A final review of the Well-Architected Framework
| Erscheinungsdatum | 02.09.2023 |
|---|---|
| Zusatzinfo | Illustrationen |
| Verlagsort | Berkeley |
| Sprache | englisch |
| Maße | 155 x 235 mm |
| Gewicht | 244 g |
| Einbandart | kartoniert |
| Themenwelt | Informatik ► Netzwerke ► Sicherheit / Firewall |
| Schlagworte | AWS • AWS Compute Security • AWS Database Security • AWS Networking Security • AWS Storage Security • Cloud Computing • security |
| ISBN-10 | 1-4842-9680-X / 148429680X |
| ISBN-13 | 978-1-4842-9680-6 / 9781484296806 |
| Zustand | Neuware |
| Informationen gemäß Produktsicherheitsverordnung (GPSR) | |
| Haben Sie eine Frage zum Produkt? |
aus dem Bereich
