Jak używać
- Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
- W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
- Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill vendor-monitoring-programPrzed rozpoczęciem
- Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
- Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill
Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.
Vendor Privacy Monitoring Program
Overview
GDPR Article 28(1) imposes a continuing obligation on controllers to ensure that processors maintain sufficient guarantees. This is not a one-time assessment — the EDPB Guidelines 07/2020 (paragraph 87) explicitly state that the controller's assessment obligation is ongoing. The Vendor Privacy Monitoring Program at Summit Cloud Partners implements continuous oversight proportionate to the risk each vendor presents.
Monitoring Framework
Tier-Based Monitoring Schedule
| Activity | Tier 1 (High Risk) | Tier 2 (Standard) | Tier 3 (Low Risk) |
|---|---|---|---|
| Full reassessment | Annual | Biennial | Triennial |
| Privacy audit | Annual (Type 2/3) | Annual (Type 1) | Biennial (Type 1) |
| Sub-processor list verification | Quarterly | Semi-annual | Annual |
| DPA compliance review | Annual | Biennial | Triennial |
| Risk score recalculation | Semi-annual | Annual | Biennial |
| Certification status check | Quarterly | Semi-annual | Annual |
| Breach monitoring | Continuous | Continuous | Monthly check |
| Contract renewal privacy gate | 120 days before | 90 days before | 90 days before |
Continuous Monitoring Signals
Automated or semi-automated monitoring sources that provide ongoing visibility:
| Signal Source | What It Monitors | Frequency | Alert Trigger |
|---|---|---|---|
| Vendor risk intelligence platform | Public breach disclosures, enforcement actions, news | Daily | New incident involving a monitored vendor |
| Certification monitoring | ISO/SOC certificate validity and scope changes | Monthly | Certificate approaching expiry (60 days) |
| CASB/DLP | Data flows to vendor — volume and category anomalies | Continuous | Data transfer exceeding baseline by 200% |
| DNS/network monitoring | Connectivity patterns to vendor endpoints | Continuous | New endpoints, geographic changes |
| Vendor security scorecard | External security posture assessment | Monthly | Score drops below threshold |
| Regulatory database monitoring | New enforcement decisions involving vendor | Weekly | New published enforcement action |
| Sub-processor registry monitoring | Vendor-published sub-processor list changes | Weekly | New or changed sub-processor detected |
Annual Reassessment Process
For each vendor due for reassessment:
Phase 1: Preparation (30 days before reassessment)
| Activity | Responsible |
|---|---|
| Pull current vendor profile and risk score | Privacy Team |
| Review monitoring signals from prior period | Privacy Team |
| Compile open audit findings and remediation status | Privacy Team |
| Identify changes since last assessment | Privacy Team |
| Send reassessment questionnaire to vendor | Privacy Team |
Phase 2: Assessment (Assessment month)
| Activity | Responsible |
|---|---|
| Review vendor's updated questionnaire responses | Privacy Team |
| Verify current certifications | Privacy Team |
| Review sub-processor list for changes | Privacy Team |
| Assess any processing scope changes | Privacy Team |
| Conduct audit (per tier schedule) | Audit Team |
| Recalculate risk score | Privacy Team |
Phase 3: Decision and Documentation
| Activity | Responsible |
|---|---|
| Update sufficiency determination | DPO |
| Update vendor risk tier (if changed) | Privacy Team Lead |
| Update monitoring schedule | Privacy Team |
| Communicate outcomes to business unit | Privacy Team |
| File reassessment documentation | Privacy Team |
Contract Renewal Privacy Gate
When a vendor contract approaches renewal, a privacy gate ensures continued compliance:
| Timing | Activity |
|---|---|
| 120 days before renewal (Tier 1) / 90 days (Tier 2/3) | Privacy Team notified of upcoming renewal |
| 90 days before renewal | Review current privacy compliance status |
| 60 days before renewal | Complete any required reassessment |
| 30 days before renewal | Issue renewal privacy recommendation (Renew / Renew with conditions / Do not renew) |
| At renewal | Execute any required DPA amendments |
Renewal Privacy Decision Matrix:
| Compliance Status | Audit Status | Risk Trend | Recommendation |
|---|---|---|---|
| Fully compliant | Clean audit | Stable/improving | Renew |
| Minor gaps | Minor findings only | Stable | Renew with conditions |
| Material gaps | Major findings pending | Deteriorating | Renew with conditions + accelerated audit |
| Significant non-compliance | Critical findings open | Deteriorating | Do not renew (initiate termination planning) |
Performance Metrics and KPIs
Vendor Privacy Program KPIs
| KPI | Target | Measurement | Frequency |
|---|---|---|---|
| DPA coverage rate | 100% of data-processing vendors | Active DPAs / vendors processing personal data | Quarterly |
| Reassessment completion rate | 100% on schedule | Completed on time / due | Quarterly |
| Audit completion rate | 100% per tier schedule | Audits completed / audits due | Annual |
| Average vendor risk score | Trending downward | Mean weighted score across all vendors | Semi-annual |
| Open audit findings (Critical) | 0 past deadline | Count of overdue Critical findings | Monthly |
| Open audit findings (Major) | 0 past deadline | Count of overdue Major findings | Monthly |
| Sub-processor notification compliance | 100% | Changes notified before engagement / total changes | Quarterly |
| Mean time to acknowledge breach | < 2 hours | Average time from vendor notification to acknowledgment | Per incident |
| Deletion certification rate | 100% within DPA timeline | Certifications received on time / terminations | Annual |
| Shadow IT detection-to-remediation | < 30 days | Average days from detection to sanctioned/blocked | Quarterly |
Vendor Privacy Scorecard
Each vendor receives a quarterly privacy scorecard:
| Dimension | Weight | Score (1-5) | Trend |
|---|---|---|---|
| DPA compliance | 25% | [X] | [Up/Down/Stable] |
| Audit performance | 20% | [X] | [Up/Down/Stable] |
| Breach history (rolling 12 months) | 15% | [X] | [Up/Down/Stable] |
| Sub-processor management compliance | 15% | [X] | [Up/Down/Stable] |
| Certification currency | 15% | [X] | [Up/Down/Stable] |
| Cooperation and responsiveness | 10% | [X] | [Up/Down/Stable] |
| Weighted Total | 100% | [X.X] |
Governance Reporting
Monthly Privacy Team Report
| Section | Content |
|---|---|
| Vendor count and tier distribution | Current state |
| New vendors onboarded | Privacy review outcomes |
| Vendors terminated | Deletion certification status |
| Open audit findings by severity | Remediation timeline |
| Monitoring alerts actioned | Signal source and resolution |
| Shadow IT detections | Discovery and remediation |
| Upcoming deadlines | Reassessments, renewals, audits due |
Quarterly DPO Report
| Section | Content |
|---|---|
| Program KPIs vs targets | Dashboard with trend analysis |
| Risk tier changes | Escalations and de-escalations with rationale |
| Significant vendor events | Breaches, enforcement, certification changes |
| Regulatory developments | New guidance affecting vendor management |
| Recommendations | Program improvements, resource needs |
Key Regulatory References
- GDPR Article 28(1) — Continuing obligation to verify processor sufficiency
- GDPR Article 5(2) — Accountability principle requires demonstrated ongoing compliance
- GDPR Article 24 — Controller responsibility for appropriate measures
- EDPB Guidelines 07/2020 — Ongoing assessment obligation (paragraph 87)
- ISO 27001:2022 — A.5.19 Information security in supplier relationships (monitoring)
- NIST CSF 2.0 — ID.SC Supply chain risk management
