[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADP971SPC67HFKXWP3G94F":3,"skill-same:01M6ADP971SPC67HFKXWP3G94F":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6ADP971SPC67HFKXWP3G94F","ai-deployment-checklist",null,"Pre-deployment privacy compliance checklist for AI\u002FML systems covering DPIA completion, lawful basis verification, transparency notices, human oversight mechanisms, bias testing, and post-deployment monitoring setup. Keywords: AI deployment, privacy checklist, go-live, model deployment, compliance gate.","mukul975\u002FPrivacy-Data-Protection-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADNKWX1HF4Q5DKEXT5M774",337,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36],"deployment","ai deployment checklist","testing","go","setup","governance","ml","model deployment","release","verification","monitoring","compliance","privacy","2026-11-10 10:12:30",false,"---\nname: ai-deployment-checklist\ndescription: >-\n  Pre-deployment privacy compliance checklist for AI\u002FML systems covering DPIA\n  completion, lawful basis verification, transparency notices, human oversight\n  mechanisms, bias testing, and post-deployment monitoring setup. Keywords:\n  AI deployment, privacy checklist, go-live, model deployment, compliance gate.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: ai-privacy-governance\n  tags: \"ai-deployment, privacy-checklist, compliance-gate, model-release, pre-deployment\"\n---\n\n# AI System Pre-Deployment Privacy Checklist\n\n## Overview\n\nDeploying an AI system that processes personal data requires verification of privacy compliance across multiple dimensions before the system goes live. This checklist serves as a compliance gate in the Cerebrum AI Labs ML deployment pipeline. No AI system may be deployed to production until all mandatory items are verified and signed off by the Data Protection Officer (DPO). The checklist is structured around GDPR requirements, the EU AI Act obligations (for high-risk systems), and internal governance standards.\n\n## Pre-Deployment Compliance Gate\n\n### Gate 1: Legal Basis and DPIA\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Lawful basis documented | Art. 6(1) basis identified and recorded for all personal data processing | Required | LIA or consent records |\n| Special categories assessed | Art. 9 data identified; explicit consent or Art. 9(2) exception documented | Required | Data classification report |\n| DPIA completed | Art. 35 DPIA completed for high-risk processing (profiling, systematic monitoring, large-scale special categories) | Required if applicable | DPIA document signed by DPO |\n| DPIA risks mitigated | All high\u002Fcritical risks from DPIA have documented mitigations | Required | Risk treatment plan |\n| Prior consultation | Art. 36 consultation with supervisory authority if residual risk remains high | Required if applicable | Consultation record |\n| Legitimate interest assessment | If relying on Art. 6(1)(f), LIA balancing test completed | Required if LI basis | LIA document |\n\n### Gate 2: Transparency and Information\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Privacy notice updated | Art. 13-14 information includes AI processing details | Required | Updated privacy notice |\n| Logic described | \"Meaningful information about the logic involved\" documented for data subjects | Required for automated decisions | Explanation document |\n| Significance disclosed | Envisaged consequences of AI processing disclosed | Required for automated decisions | Privacy notice section |\n| Profiling disclosed | If system profiles individuals, this is disclosed in privacy notice | Required if profiling | Privacy notice section |\n| AI Act transparency | Art. 52 transparency obligations met (if applicable): inform that they are interacting with AI | Required for AI Act | User interface disclosure |\n\n### Gate 3: Data Subject Rights\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Access process defined | Process for responding to access requests for AI data (inputs, outputs, profiles) | Required | Documented SOP |\n| Explanation mechanism | Individual explanations can be generated on request | Required for Art. 22 | Technical capability verified |\n| Human intervention available | Art. 22(3) human review process established | Required for solely automated decisions | Process document + trained staff |\n| Contestation channel | Data subjects can contest AI decisions and have them reviewed | Required for Art. 22 | Appeal process document |\n| Rectification process | Process for correcting AI input data and regenerating outputs | Required | Documented SOP |\n| Erasure process | Process for deleting data from training sets, inference logs, embeddings | Required | Documented SOP |\n\n### Gate 4: Data Quality and Bias\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Training data documented | Data sources, size, collection method, preprocessing documented | Required | Data card \u002F dataset documentation |\n| Bias testing completed | Model tested for bias across protected attributes (gender, race, age, disability) | Required | Bias test report |\n| Fairness metrics acceptable | Disparate impact ratio >0.8 (four-fifths rule) or equivalent metric within acceptable range | Required | Fairness metrics report |\n| Data quality verified | Training data completeness, accuracy, representativeness verified | Required | Data quality report |\n| Art. 9 data removed or justified | Special category data either removed or lawful basis documented | Required | Data classification report |\n\n### Gate 5: Security and Technical Controls\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Data encryption at rest | Training data and model weights encrypted (AES-256 or equivalent) | Required | Security configuration |\n| Data encryption in transit | All API endpoints use TLS 1.2+ | Required | SSL certificate |\n| Access controls | Role-based access to model, training data, and inference logs | Required | IAM policy |\n| Audit logging | All model invocations logged with timestamp, input hash, output, user | Required | Logging configuration |\n| Adversarial robustness | Model tested against common adversarial attacks relevant to its domain | Recommended | Security test report |\n| Model versioning | Model versioned in registry with rollback capability | Required | MLflow \u002F model registry |\n\n### Gate 6: Monitoring and Governance\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Performance monitoring | Dashboard tracking accuracy, latency, error rates in production | Required | Monitoring setup |\n| Drift detection | Data drift and concept drift detection implemented | Required | Drift monitoring configuration |\n| Bias monitoring | Post-deployment bias metrics tracked continuously | Required | Fairness monitoring dashboard |\n| Incident response | Process for handling AI-related privacy incidents (e.g., discriminatory output, data leak) | Required | Incident response plan |\n| Retraining schedule | Defined schedule for model retraining with fresh data | Required | Retraining plan |\n| Retention enforcement | Automated deletion of inference logs and training data per retention schedule | Required | Retention policy + automation |\n\n### Gate 7: EU AI Act (High-Risk Systems Only)\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Risk classification | System classified per Annex III | Required | Classification document |\n| Technical documentation | Annex IV documentation complete | Required | Tech doc package |\n| Risk management system | Art. 9 continuous risk management implemented | Required | Risk register + process |\n| Conformity assessment | Internal or third-party conformity assessment completed | Required | Assessment report |\n| EU Declaration of Conformity | Art. 47 declaration prepared | Required | Signed declaration |\n| EU database registration | Art. 49 registration completed | Required | Registration confirmation |\n\n## Sign-Off\n\n| Role | Name | Approval | Date |\n|------|------|----------|------|\n| ML Engineering Lead | | [ ] Approved \u002F [ ] Blocked | |\n| Data Protection Officer | | [ ] Approved \u002F [ ] Blocked | |\n| Information Security Officer | | [ ] Approved \u002F [ ] Blocked | |\n| Product Owner | | [ ] Approved \u002F [ ] Blocked | |\n| Legal Counsel | | [ ] Approved \u002F [ ] Blocked (high-risk only) | |\n\n## Key Legal References\n\n- **GDPR Articles 5, 6, 9** — Data processing principles, lawful basis, special categories\n- **GDPR Article 22** — Automated individual decision-making safeguards\n- **GDPR Article 25** — Data protection by design and by default\n- **GDPR Article 35** — Data Protection Impact Assessment\n- **EU AI Act Articles 9-15** — High-risk AI system requirements\n- **EU AI Act Article 52** — Transparency obligations for certain AI systems\n- **EDPB Guidelines on Automated Decision-Making (WP 251 rev.01)** — Art. 22 interpretation\n- **ISO\u002FIEC 42001:2023** — AI management system standard\n","# AI System Pre-Deployment Privacy Checklist\n\n## Overview\n\nDeploying an AI system that processes personal data requires verification of privacy compliance across multiple dimensions before the system goes live. This checklist serves as a compliance gate in the Cerebrum AI Labs ML deployment pipeline. No AI system may be deployed to production until all mandatory items are verified and signed off by the Data Protection Officer (DPO). The checklist is structured around GDPR requirements, the EU AI Act obligations (for high-risk systems), and internal governance standards.\n\n## Pre-Deployment Compliance Gate\n\n### Gate 1: Legal Basis and DPIA\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Lawful basis documented | Art. 6(1) basis identified and recorded for all personal data processing | Required | LIA or consent records |\n| Special categories assessed | Art. 9 data identified; explicit consent or Art. 9(2) exception documented | Required | Data classification report |\n| DPIA completed | Art. 35 DPIA completed for high-risk processing (profiling, systematic monitoring, large-scale special categories) | Required if applicable | DPIA document signed by DPO |\n| DPIA risks mitigated | All high\u002Fcritical risks from DPIA have documented mitigations | Required | Risk treatment plan |\n| Prior consultation | Art. 36 consultation with supervisory authority if residual risk remains high | Required if applicable | Consultation record |\n| Legitimate interest assessment | If relying on Art. 6(1)(f), LIA balancing test completed | Required if LI basis | LIA document |\n\n### Gate 2: Transparency and Information\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Privacy notice updated | Art. 13-14 information includes AI processing details | Required | Updated privacy notice |\n| Logic described | \"Meaningful information about the logic involved\" documented for data subjects | Required for automated decisions | Explanation document |\n| Significance disclosed | Envisaged consequences of AI processing disclosed | Required for automated decisions | Privacy notice section |\n| Profiling disclosed | If system profiles individuals, this is disclosed in privacy notice | Required if profiling | Privacy notice section |\n| AI Act transparency | Art. 52 transparency obligations met (if applicable): inform that they are interacting with AI | Required for AI Act | User interface disclosure |\n\n### Gate 3: Data Subject Rights\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Access process defined | Process for responding to access requests for AI data (inputs, outputs, profiles) | Required | Documented SOP |\n| Explanation mechanism | Individual explanations can be generated on request | Required for Art. 22 | Technical capability verified |\n| Human intervention available | Art. 22(3) human review process established | Required for solely automated decisions | Process document + trained staff |\n| Contestation channel | Data subjects can contest AI decisions and have them reviewed | Required for Art. 22 | Appeal process document |\n| Rectification process | Process for correcting AI input data and regenerating outputs | Required | Documented SOP |\n| Erasure process | Process for deleting data from training sets, inference logs, embeddings | Required | Documented SOP |\n\n### Gate 4: Data Quality and Bias\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Training data documented | Data sources, size, collection method, preprocessing documented | Required | Data card \u002F dataset documentation |\n| Bias testing completed | Model tested for bias across protected attributes (gender, race, age, disability) | Required | Bias test report |\n| Fairness metrics acceptable | Disparate impact ratio >0.8 (four-fifths rule) or equivalent metric within acceptable range | Required | Fairness metrics report |\n| Data quality verified | Training data completeness, accuracy, representativeness verified | Required | Data quality report |\n| Art. 9 data removed or justified | Special category data either removed or lawful basis documented | Required | Data classification report |\n\n### Gate 5: Security and Technical Controls\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Data encryption at rest | Training data and model weights encrypted (AES-256 or equivalent) | Required | Security configuration |\n| Data encryption in transit | All API endpoints use TLS 1.2+ | Required | SSL certificate |\n| Access controls | Role-based access to model, training data, and inference logs | Required | IAM policy |\n| Audit logging | All model invocations logged with timestamp, input hash, output, user | Required | Logging configuration |\n| Adversarial robustness | Model tested against common adversarial attacks relevant to its domain | Recommended | Security test report |\n| Model versioning | Model versioned in registry with rollback capability | Required | MLflow \u002F model registry |\n\n### Gate 6: Monitoring and Governance\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Performance monitoring | Dashboard tracking accuracy, latency, error rates in production | Required | Monitoring setup |\n| Drift detection | Data drift and concept drift detection implemented | Required | Drift monitoring configuration |\n| Bias monitoring | Post-deployment bias metrics tracked continuously | Required | Fairness monitoring dashboard |\n| Incident response | Process for handling AI-related privacy incidents (e.g., discriminatory output, data leak) | Required | Incident response plan |\n| Retraining schedule | Defined schedule for model retraining with fresh data | Required | Retraining plan |\n| Retention enforcement | Automated deletion of inference logs and training data per retention schedule | Required | Retention policy + automation |\n\n### Gate 7: EU AI Act (High-Risk Systems Only)\n\n| Check | Requirement | Status | Evidence |\n|-------|-------------|--------|----------|\n| Risk classification | System classified per Annex III | Required | Classification document |\n| Technical documentation | Annex IV documentation complete | Required | Tech doc package |\n| Risk management system | Art. 9 continuous risk management implemented | Required | Risk register + process |\n| Conformity assessment | Internal or third-party conformity assessment completed | Required | Assessment report |\n| EU Declaration of Conformity | Art. 47 declaration prepared | Required | Signed declaration |\n| EU database registration | Art. 49 registration completed | Required | Registration confirmation |\n\n## Sign-Off\n\n| Role | Name | Approval | Date |\n|------|------|----------|------|\n| ML Engineering Lead | | [ ] Approved \u002F [ ] Blocked | |\n| Data Protection Officer | | [ ] Approved \u002F [ ] Blocked | |\n| Information Security Officer | | [ ] Approved \u002F [ ] Blocked | |\n| Product Owner | | [ ] Approved \u002F [ ] Blocked | |\n| Legal Counsel | | [ ] Approved \u002F [ ] Blocked (high-risk only) | |\n\n## Key Legal References\n\n- **GDPR Articles 5, 6, 9** — Data processing principles, lawful basis, special categories\n- **GDPR Article 22** — Automated individual decision-making safeguards\n- **GDPR Article 25** — Data protection by design and by default\n- **GDPR Article 35** — Data Protection Impact Assessment\n- **EU AI Act Articles 9-15** — High-risk AI system requirements\n- **EU AI Act Article 52** — Transparency obligations for certain AI systems\n- **EDPB Guidelines on Automated Decision-Making (WP 251 rev.01)** — Art. 22 interpretation\n- **ISO\u002FIEC 42001:2023** — AI management system standard\n",{"name":5,"license":15,"metadata":42,"description":7},{"tags":43,"author":9,"domain":36,"version":44,"subdomain":45},"ai-deployment, privacy-checklist, compliance-gate, model-release, pre-deployment","1.0","ai-privacy-governance","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist",68,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-03-17 04:06:52",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill ai-deployment-checklist",{"tool":61,"command":62},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill ai-deployment-checklist",{"tool":64,"command":65},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill ai-deployment-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist\u002FSKILL.md",true,[69,75,81,85],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Ftemplate.md","ASSET","资产文件",1491,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist\u002Fassets\u002Ftemplate.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fstandards.md","REFERENCE","参考文档",3767,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist\u002Freferences\u002Fstandards.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fworkflows.md",5004,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist\u002Freferences\u002Fworkflows.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fprocess.py","SCRIPT","脚本",651,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fai-privacy-governance-skills\u002Fskills\u002Fai-deployment-checklist\u002Fscripts\u002Fprocess.py",[92,114,131,143,160,173],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":107,"publishedAt":37},"01M6AG6K8R3XW10ENWH2FH18RH","workplace-email-privacy","Implements email and internet monitoring compliance in the workplace per Barbulescu v Romania (ECHR Grand Chamber), EDPB guidance, and national labour law. Covers acceptable use policies, legitimate expectation of privacy, proportionality testing, and content vs metadata monitoring. Keywords: email monitoring, Barbulescu, workplace privacy, internet monitoring, acceptable use policy, ECHR, proportionality.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fworkplace-email-privacy\u002FSKILL.md",[98,103,106],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,36,35,110,111,112,26,34,113],"email","workplace email privacy","content","data","policy","metadata",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":124,"publishedAt":37},"01M6AG6FRCBJY7D061BJZMNV49","whistleblower-data","Implements data protection compliance for whistleblowing systems under EU Directive 2019\u002F1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019\u002F1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fwhistleblower-data\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[111,125,126,127,35,128,129,36,130],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":37},"01M6AG6CJP0PW3X65HC7VP9SR9","vendor-termination-data","Vendor termination data return and deletion procedures per GDPR Article 28(3)(g). Covers data extraction formats, deletion certification requirements, transition planning, residual data handling, and post-termination verification.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-termination-data\u002FSKILL.md",[137],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[111,139,140,33,141,129,36,142],"vendor termination data","planning","extraction","certification",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":37},"01M6AG69E277DXZB2NF6KV17ZA","vendor-risk-scoring","Vendor privacy risk tiering methodology for processor management. Covers scoring factors including data volume, sensitivity, transfer locations, certifications, breach history, and control maturity with weighted risk calculation and tier assignment.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-risk-scoring\u002FSKILL.md",[149],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[151,152,153,154,155,156,157,158,36,111,159],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":37},"01M6AG6655ABFKT2BBWHCP4PAT","vendor-privacy-due-diligence","Pre-contract vendor privacy due diligence per GDPR Article 28(1). Covers risk questionnaires, technical controls assessment, certification review, data flow analysis, and documented sufficiency decisions for processor engagement.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-privacy-due-diligence\u002FSKILL.md",[166],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[36,168,129,169,156,170,171,111,159,152,142,172],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":186,"publishedAt":37},"01M6AG62C3VD8SYNGH4N7RHZTE","vendor-privacy-audit","On-site and remote vendor audit procedures per GDPR Article 28(3)(h). Covers audit planning, evidence collection methodologies, finding classification, remediation tracking, and audit report generation for processor compliance verification.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-privacy-audit\u002FSKILL.md",[179,182,185],{"categoryNo":180,"categoryName":181,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[187,188,36,189,33,190,35,129,191,159,192,193,194,140],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]