mcpField
C
cloud-provider-assessment

cloud-provider-assessment

github.com/mukul975Security32338 installsUpdated 32w ago
Repository

About cloud-provider-assessment

A cloud-provider privacy assessment skill for teams conducting vendor due diligence. It organizes review around cloud service models, privacy frameworks, residency, tenant isolation, and shared responsibilities.

Key features

  1. 01IaaS, PaaS, and SaaS responsibility mapping
  2. 02Data residency and sovereignty questions
  3. 03Multi-tenant isolation review
  4. 04ISO 27018, CSA STAR, and SOC 2 checks
  5. 05Weighted assessment scoring

Use cases

  1. 01Assess a cloud provider before procurement
  2. 02Review data locations and cross-region processing
  3. 03Identify responsibility gaps across service models

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill cloud-provider-assessment

After installing, type/cloud-provider-assessmentin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
template.md
references/
standards.md
workflows.md
scripts/
process.py

Details

From the project README

Cloud Service Provider Privacy Assessment

Overview

Cloud service providers present unique privacy assessment challenges due to shared responsibility models, multi-tenancy architectures, global infrastructure, and the abstraction of physical processing locations. GDPR Article 28 obligations apply fully to cloud processing relationships, but the assessment approach must account for cloud-specific characteristics.

ISO/IEC 27018:2019 provides the international standard for protecting personally identifiable information (PII) in public clouds, supplementing ISO 27001 with cloud-specific privacy controls. The Cloud Security Alliance (CSA) STAR program provides a cloud-specific security assurance framework. SOC 2 Type II with the Privacy trust services criterion addresses personal data handling controls.

At Summit Cloud Partners, cloud providers undergo enhanced assessment incorporating these cloud-specific frameworks alongside standard vendor due diligence.

Cloud Service Models and Privacy Implications

IaaS (Infrastructure as a Service)
AspectController ResponsibilityProvider Responsibility
Data encryption at restConfigure and manage keysProvide encryption infrastructure
Access management (app level)Define and manageProvide IAM platform
Network security (app level)Configure security groups, firewall rulesProvide network infrastructure
Physical securityNoneFull responsibility
Patch management (OS)Controller (or managed service)Hypervisor and below
Data backupConfigure and manageProvide backup infrastructure
Incident detection (app)Application-level monitoringInfrastructure-level monitoring
PaaS (Platform as a Service)
AspectController ResponsibilityProvider Responsibility
Application code securityFull responsibilityNone
Data handling in applicationFull responsibilityNone
Runtime and middlewareLimited — configuration onlyManage platform components
OS and infrastructureNoneFull responsibility
Platform security patchingNoneFull responsibility
Identity managementConfigureProvide identity platform
SaaS (Software as a Service)
AspectController ResponsibilityProvider Responsibility
Data entered by usersDetermine what data to processProcess per controller instructions
Application securityNone (except configuration)Full responsibility
Infrastructure securityNoneFull responsibility
Data portabilityDefine export requirementsProvide export functionality
Data deletionRequest deletionImplement deletion per DPA
Access configurationConfigure user rolesProvide RBAC platform

Assessment Framework

Domain 1: Data Residency and Sovereignty

Assessment Questions:

#QuestionExpected Evidence
1.1In which regions/availability zones will personal data be stored at rest?Architecture documentation specifying data storage locations
1.2Can the controller restrict processing to specific geographic regions?Configuration documentation showing region-locking capability
1.3Are there any circumstances where data may be processed outside the selected region?Disclosure of any cross-region processing (DR, support, analytics)
1.4Where is metadata and telemetry data stored?Often stored in provider's home jurisdiction — must be disclosed
1.5Where do support staff access data from?List of countries from which support personnel may access data
1.6What government access or disclosure obligations apply in processing jurisdictions?Legal analysis of government access powers per EDPB Recommendations 01/2020
Domain 2: Multi-Tenancy and Data Isolation
#QuestionExpected Evidence
2.1How is tenant data isolated from other customers' data?Architecture documentation — logical/physical separation details
2.2Are encryption keys unique per tenant?Key management architecture documentation
2.3Can one tenant's operations affect another tenant's data?Side-channel and cross-tenant risk assessment
2.4How are shared infrastructure components secured?Hypervisor security, shared storage controls
2.5What tenant isolation testing has been performed?Penetration test results covering cross-tenant attacks
Domain 3: ISO 27018 Cloud Privacy Controls

ISO/IEC 27018:2019 extends ISO 27001 with cloud-specific PII protection controls:

ControlRequirementAssessment Check
A.1PII processor consent — process only per controller instructionsVerify contractual terms and processing boundaries
A.2Purpose limitation — no processing beyond controller purposeReview processing scope documentation
A.3Use for marketing — no use of PII for marketing without consentConfirm no data monetization or marketing use
A.4Notification — notify controller of government access requestsVerify government access notification process
A.5Disclosure — document all disclosures of PIIReview disclosure logging mechanism
A.10Return, transfer, and disposal — secure data handling at terminationVerify deletion procedures and certification
A.11Confidentiality — binding confidentiality obligations on personnelVerify personnel agreements cover cloud-specific risks
A.12Sub-contracting — notification of sub-processor engagementVerify sub-processor management per Art. 28(2)
Domain 4: CSA STAR Assessment

The Cloud Security Alliance STAR (Security, Trust, Assurance, and Risk) program provides three levels:

LevelDescriptionAssessment Method
Level 1: Self-AssessmentProvider completes CSA Consensus Assessments Initiative Questionnaire (CAIQ)Review self-assessment for completeness and substantiation
Level 2: Third-Party AuditIndependent audit against CSA Cloud Controls Matrix (CCM)Review audit report, scope, and findings
Level 3: Continuous MonitoringReal-time monitoring of control effectivenessReview continuous monitoring dashboard and alerts

Key CCM Control Domains for Privacy:

DomainControlsPrivacy Relevance
DSP (Data Security & Privacy)DSP-01 through DSP-19Data classification, retention, inventory, privacy by design
GRC (Governance, Risk, Compliance)GRC-01 through GRC-08Governance framework, risk assessment, policy management
IAM (Identity & Access Management)IAM-01 through IAM-16Access control, credential management, MFA
SEF (Security Incident Management)SEF-01 through SEF-08Incident response, breach notification
Domain 5: SOC 2 Type II Privacy Criterion

The AICPA Trust Services Criteria Privacy criterion evaluates:

CriterionAreaAssessment Focus
P1NoticeProvider discloses privacy practices to controllers
P2Choice and consentController can configure privacy settings
P3CollectionData collection limited to stated purposes
P4Use, retention, disposalProcessing per instructions; retention per DPA; certified deletion
P5AccessController can access and retrieve their data
P6Disclosure to third partiesSub-processor disclosure and management
P7Security for privacyTechnical controls protecting PII
P8QualityData integrity and accuracy controls
P9Monitoring and enforcementCompliance monitoring and breach response
Domain 6: Shared Responsibility Model Mapping

Document the shared responsibility boundary for every control domain:

Control DomainController ResponsibilityProvider ResponsibilityGap/Risk
Data classificationClassify data before uploadProvide classification tools[Gap?]
Encryption key management[Depends on model][Depends on model][Gap?]
Access control (application)[Depends on model][Depends on model][Gap?]
Vulnerability management[Depends on model][Depends on model][Gap?]
Incident detection[Depends on model][Depends on model][Gap?]
Data backup[Depends on model][Depends on model][Gap?]
Compliance reporting[Depends on model][Depends on model][Gap?]

Assessment Scoring

DomainWeightScore (1-5)Weighted
Data residency and sovereignty20%
Multi-tenancy and isolation20%
ISO 27018 compliance15%
CSA STAR level15%
SOC 2 Privacy criterion15%
Shared responsibility clarity15%
TOTAL100%

Key Regulatory References

  • GDPR Article 28 — Controller-processor relationship applies fully to cloud
  • GDPR Article 32 — Security measures including cloud-specific controls
  • ISO/IEC 27018:2019 — Code of practice for protection of PII in public clouds
  • ISO/IEC 27017:2015 — Code of practice for information security controls for cloud services
  • CSA Cloud Controls Matrix (CCM) v4.0 — Cloud security control framework
  • EDPB Recommendations 01/2020 — Supplementary measures for cloud transfers
  • ENISA Cloud Computing Risk Assessment (2009, updated) — EU cloud risk framework

Comments

Markdown supported