DAY 04 :π Navigating AWS Security & Compliance: A Shared Responsibility Model π‘οΈ
Security and Compliance
β AWS Shared Responsibility Model
In traditional non-cloud-based deployments, all aspects of security are owned by you
Securing data center
Securing network and connectivity
Securing servers
Securing and patching operating systems
Securing application code so it isnβt susceptible to exploits and vulnerabilities Security in the cloud is a team effort between you and Amazon The Shared Responsibility model outlines the role that AWS and you, as the customer, play when it comes to security. (Who is responsible for what?)
Note:
β’ Unmanaged services need to be secured by users.
β’ Managed services offload some of the security responsibilities of a service on AWS. Compliance
Organizations in specific industries must adhere to certain rules and guidelines specific to that industry (Finance, Health, Federal Government).
Compliance and regulatory frameworks are sets of guidelines and best practices. Organizations follow these guidelines to meet regulatory requirements, improve processes, strengthen security, and achieve other business goals.
Healthcare industry β HIPAA/HITECH
Payment card industry β PCI DSS
Compliance is a shared responsibility between customers and AWS.
AWS undergoes certifications, reviews, and audits by various governing bodies.
These audit reports are made available to customers using AWS Artifact. Artifact allows customers to review and accept agreements to maintain compliance
β AWS Compliance Center
AWS Compliance Center is a central location to research cloud-related regulatory requirements and assess their impact on your industry
Identify regulatory requirements
Browse country-specific lAWS/requirements
Discover how companies in various industries solve compliance, governance challenges
Use AWS to answer key compliance questions
Get an audit and security checklist
Reference architectures with best practices
β AWS Audit Manager continuously collects data to prepare for audits and ensures that you are achieving compliance with regulatory standards. It helps build audit-ready reports.
β It tracks how the resource is configured and records the previous configuration states, so you can see how the configs for it have changed over time.
Thankyou for reading !!!!!