Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Assumption is the Mother of all Failures — why ...

Assumption is the Mother of all Failures — why having a detailed SRM is key to 100% customer satisfaction

More than 10 years ago AWS introduced their initial version of the infamous AWS Shared Responsible Model. As an MSP Partner, Schuberg Philis took this model to the next level, as in their view, it’s not just AWS and the Customer who share responsibility.

Starting at AWS’ model, Stephen and Daan will take you on a journey to an actual implementation of Schuberg Philis’ Enablement Platform.

Stephen Hoekstra

October 03, 2022
Tweet

Other Decks in Technology

Transcript

  1. Assumption is the Mother of all … Failures! • Why

    having a detailed SRM is key to 100% customer satisfaction
  2. • Information Security Officer • Past: Smiths Group plc, ABN

    and Unilever • 6 years @ Schuberg Philis • Involved with Customer Teams in the Financial industry and Government • Mission Critical Engineer • Past: Claranet • 7 years @ Schuberg Philis • Involved with Customer Teams in the Payment industry Develop scalable, reliable services Engaged with customers from day 1 End goal: 100% Customer Satisfaction
  3. AWS’ Shared Responsibility Model Responsible for Security IN the Cloud

    Responsible for Security OF the Cloud https://aws.amazon.com/compliance/shared-responsibility-model/
  4. Shared Responsibility Model vX,01 AWS SRM and Platform Team Responsible

    for Security IN the Cloud Responsible for Security OF the Cloud Responsible for Security OF the Platform
  5. Workload Team Functional Management Team Audit Team Security Operations Team

    ackup Team Business 3rd party Services Network Team Platform Team CCoE
  6. Consumable Services Optional Services Cloud Foundation Code Control Tagging and

    Naming Disaster Recovery Image Management Monitoring Domain Management Automation Pipelines User Management Logging & Metrics CI CD Artifact Management Engineer Access Advanced Data Protection Cost & Resource Management Advanced WAF & DDoS Connectivity Exit Management Cloud Vendor Management Platform IAM Environment Management Cloud Networking Cloud Security Auditing Security & Audit Dashboards Container Orchestration License Management Enabling Corporate Integrations ITSM EDR & Virus Management Directory Services Compliance Code Quality IPAM Patch Management Application Tracing Native Backup Automation Operations & Systems Management SOC DXP Sustainability Privacy Operations Chaos Engineering Integration Platform Orchestration
  7. The Cloud Foundation is comprised of two parts: • Organisation

    management • Identity Access Management • Organisation wide policies • Governance via centralised auditing and reporting • Account vending machine • Repeatable deployment of workload accounts & pipelines consumable services workload cloud foundation Cloud Foundation workload workload workload
  8. Consumable Services The consumable service layer covers everything the workload

    needs to be successful. These come either in the form of platform components or service management. Platform components are run by us to support workload requirements, such as: • Backups • DNS management • Image management • Monitoring • Network management • Cost Management • Risk & Compliance • Vulnerability Management consumable services workload cloud foundation workload workload workload
  9. Workload AWS Definition: A workload is a collection of resources

    and code that delivers business value, such as a customer-facing application or a backend process. A workload might consist of a subset of resources in a single AWS account or be a collection of multiple resources spanning multiple AWS accounts. consumable services workload cloud foundation workload workload workload