[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFM3VBX0TCY73ZPQT95ZFR":3,"skill-same:01M6AFM3VBX0TCY73ZPQT95ZFR":89},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6AFM3VBX0TCY73ZPQT95ZFR","data-labeling-system",null,"Implements data classification labels and tagging systems including metadata tagging, DLP integration, automated label propagation, user-applied labels, and label inheritance rules. Covers Microsoft Purview sensitivity labels and enterprise labeling architecture. Keywords: data labeling, sensitivity labels, metadata tagging, DLP integration, label propagation, Purview, classification.","mukul975\u002FPrivacy-Data-Protection-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADNKWX1HF4Q5DKEXT5M774",336,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fdata-labeling-system\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35],"data","data labeling system","microsoft","architecture","purview","metadata","integration","privacy","Enterprise","dlp","data-classification","sensitivity-labels","2026-11-10 10:12:30",false,"---\nname: data-labeling-system\ndescription: >-\n  Implements data classification labels and tagging systems including metadata\n  tagging, DLP integration, automated label propagation, user-applied labels,\n  and label inheritance rules. Covers Microsoft Purview sensitivity labels and\n  enterprise labeling architecture. Keywords: data labeling, sensitivity labels,\n  metadata tagging, DLP integration, label propagation, Purview, classification.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: data-classification\n  tags: \"data-labeling, sensitivity-labels, metadata-tagging, dlp, label-propagation, purview\"\n---\n\n# Data Classification Labels and Tagging System\n\n## Overview\n\nData classification labels are the operational mechanism through which classification policy is enforced across the enterprise. Labels attach classification metadata to data assets — documents, emails, database records, and cloud resources — enabling automated enforcement of handling requirements through DLP policies, access controls, and encryption. This skill covers the design and implementation of a labelling system using Microsoft Purview Information Protection as the primary platform, with architecture patterns for automated labelling, user-applied labelling, label inheritance, and cross-platform propagation.\n\n## Label Taxonomy\n\n### Vanguard Financial Services Label Hierarchy\n\n```\nVanguard Classification Labels\n├── Public\n│   └── (no sub-labels)\n├── Internal\n│   └── Internal - Project Confidential\n├── Confidential\n│   ├── Confidential - Customer Data\n│   ├── Confidential - Employee Data\n│   ├── Confidential - Financial Data\n│   └── Confidential - Legal\n└── Restricted\n    ├── Restricted - Special Category (Art. 9)\n    ├── Restricted - Criminal Data (Art. 10)\n    ├── Restricted - AML Investigation\n    └── Restricted - Board & Strategy\n```\n\n### Label Properties\n\n| Label | Colour | Visual Marking | Encryption | DLP Policy | Auto-Apply |\n|-------|--------|---------------|-----------|-----------|-----------|\n| Public | Green | Footer: \"Vanguard Financial Services — Public\" | None | None | No |\n| Internal | Blue | Footer: \"Vanguard Financial Services — Internal Use Only\" | Optional | Warn on external | No |\n| Confidential | Amber | Header + Footer: \"CONFIDENTIAL\" | Azure RMS (AES-256) | Warn + audit external; block personal email | Yes (when PII detected with >85% confidence) |\n| Restricted | Red | Header + Footer: \"RESTRICTED\" with red background; watermark on print | Azure RMS (AES-256, double key encryption) | Block all external; block USB\u002Fprint; alert DPO | Yes (when Art. 9\u002FArt. 10 data detected with >85% confidence) |\n\n## Microsoft Purview Implementation Architecture\n\n### Component Architecture\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                    Microsoft Purview                             │\n│                                                                  │\n│  ┌──────────────┐  ┌──────────────┐  ┌──────────────────────┐  │\n│  │ Sensitivity   │  │ Auto-labelling│  │ DLP Policies          │  │\n│  │ Labels        │  │ Policies      │  │ (endpoint, email,     │  │\n│  │ (definitions) │  │ (rules)       │  │  SharePoint, Teams)   │  │\n│  └──────┬───────┘  └──────┬───────┘  └──────────┬───────────┘  │\n│         │                  │                      │              │\n│         ▼                  ▼                      ▼              │\n│  ┌──────────────────────────────────────────────────────────┐   │\n│  │              Unified Label Application Engine             │   │\n│  └──────────────────────────────────────────────────────────┘   │\n│         │                  │                      │              │\n└─────────┼──────────────────┼──────────────────────┼──────────────┘\n          ▼                  ▼                      ▼\n   ┌─────────────┐  ┌──────────────┐  ┌──────────────────────┐\n   │ Office Apps  │  │ SharePoint\u002F  │  │ Endpoint DLP         │\n   │ (Word, Excel,│  │ OneDrive     │  │ (Windows devices)    │\n   │  Outlook)    │  │              │  │                      │\n   └─────────────┘  └──────────────┘  └──────────────────────┘\n```\n\n### Auto-Labelling Configuration\n\n#### Policy 1: Confidential — Customer PII Detection\n\n| Setting | Value |\n|---------|-------|\n| **Policy Name** | VFS-AutoLabel-Confidential-CustomerPII |\n| **Scope** | All SharePoint sites, OneDrive accounts, Exchange mailboxes |\n| **Conditions** | Content contains ANY of: UK National Insurance Number (HIGH confidence), IBAN (HIGH), Vanguard Account Number (HIGH), Credit Card (HIGH + Luhn validated) |\n| **Minimum count** | 1 instance of any SIT at HIGH confidence |\n| **Label applied** | Confidential - Customer Data |\n| **Priority** | 2 (overridden by Restricted auto-label) |\n\n#### Policy 2: Restricted — Special Category Detection\n\n| Setting | Value |\n|---------|-------|\n| **Policy Name** | VFS-AutoLabel-Restricted-SpecialCategory |\n| **Scope** | All SharePoint sites, OneDrive accounts, Exchange mailboxes |\n| **Conditions** | Content contains ANY of: ICD-10 codes (MEDIUM+), health terminology trainable classifier (HIGH), biometric template format detection, genetic marker patterns |\n| **Minimum count** | 1 instance at MEDIUM confidence or above |\n| **Label applied** | Restricted - Special Category (Art. 9) |\n| **Priority** | 1 (highest priority — overrides all other auto-labels) |\n\n#### Policy 3: Restricted — Criminal Data Detection\n\n| Setting | Value |\n|---------|-------|\n| **Policy Name** | VFS-AutoLabel-Restricted-CriminalData |\n| **Scope** | HR SharePoint sites, Compliance SharePoint sites |\n| **Conditions** | Content contains: DBS reference patterns, criminal conviction terminology, SAR reference numbers |\n| **Label applied** | Restricted - Criminal Data (Art. 10) |\n| **Priority** | 1 |\n\n### Label Inheritance Rules\n\n| Rule | Description | Implementation |\n|------|-------------|---------------|\n| **Container inheritance** | Items in a labelled SharePoint site inherit the site's label as minimum | Site sensitivity label propagates to new items; existing items retain higher label |\n| **Email attachment inheritance** | Attachments inherit the email's label if attachment label is lower | Outlook plugin checks attachment label vs email label on send |\n| **Parent-child inheritance** | Child documents inherit parent folder label as minimum | SharePoint library policy; items cannot be labelled below folder label |\n| **No downgrade without approval** | Users cannot remove or downgrade labels without justification | Label policy: require justification text for downgrade; audit log entry |\n| **Highest label wins** | When documents are merged or combined, the highest label applies | User training + DLP monitoring for combined documents |\n\n## User-Applied Labelling\n\n### Labelling Responsibilities\n\n| Scenario | Who Labels | How |\n|----------|-----------|-----|\n| New document creation | Author | Select label from Office ribbon (Word, Excel, PowerPoint) |\n| New email composition | Sender | Select label from Outlook toolbar; mandatory before sending external |\n| File upload to SharePoint | Uploader | Label prompt on upload if no label detected |\n| Data export from system | Exporter | Label selection required before export completes |\n| Physical document printing | Printer | Classification header\u002Ffooter printed automatically; user selects tier if not auto-labelled |\n\n### Mandatory Labelling Policy\n\n| Setting | Value |\n|---------|-------|\n| **Require label on documents** | Yes — all Word, Excel, PowerPoint documents must have a label before save |\n| **Require label on emails** | Yes — for emails to external recipients; recommended for internal |\n| **Default label** | Internal (applied if user does not select; user can override up or down) |\n| **Justification for downgrade** | Required — user must enter text justification; logged in audit |\n| **Justification for removal** | Required — DPO-approved exception only |\n\n## DLP Integration\n\n### DLP Policy Matrix\n\n| Label | External Email | USB\u002FRemovable | Print | Screenshot | Cloud Upload |\n|-------|---------------|---------------|-------|-----------|-------------|\n| Public | Allow | Allow | Allow | Allow | Allow |\n| Internal | Warn | Warn | Allow | Allow | Block (non-approved cloud) |\n| Confidential | Warn + audit | Block | Secure print | Allow (watermarked) | Block |\n| Restricted | Block | Block | Block (unless DPO approved) | Block | Block |\n\n### DLP Alert Routing\n\n| Alert Severity | Label Trigger | Routing |\n|---------------|--------------|---------|\n| Low | Internal label — external email warn overridden | Security team email |\n| Medium | Confidential label — external sharing attempted | Security team + Data Owner |\n| High | Restricted label — any policy trigger | DPO + CISO + immediate investigation |\n| Critical | Restricted label — data exfiltration indicators | DPO + CISO + Incident Response Team + 15-minute SLA |\n\n## Label Propagation Across Platforms\n\n### Supported Platforms\n\n| Platform | Label Method | Propagation |\n|----------|-------------|-------------|\n| Microsoft 365 (Word, Excel, PowerPoint) | Native sensitivity label in file metadata | Full support — label travels with file |\n| Outlook \u002F Exchange | Email header X-MS-Exchange-Organization-Classification | Label persists in message store and forwarded copies |\n| SharePoint Online | Document library metadata + file metadata | Dual storage — library and file level |\n| OneDrive for Business | File metadata | Same as SharePoint |\n| Teams | Channel\u002Fchat message metadata | Limited — file attachments inherit, message labels in compliance |\n| PDF export | Visual marking (header\u002Ffooter) + XMP metadata | Visual marking persists; metadata depends on PDF viewer |\n| Azure SQL Database | Column-level sensitivity classification (sys.sensitivity_classifications) | Native Azure SQL feature; integrates with Purview |\n| AWS S3 | Object tags (key: classification, value: tier) | AWS-native tagging; read by Macie and IAM policies |\n| On-premises file shares | File metadata (NTFS ADS) via AIP Unified Labelling client | Requires AIP client installed on endpoints |\n\n## Enforcement Precedents\n\n- **ICO v Interserve Group (2022)**: GBP 4.4 million — failure to implement adequate data classification and labelling contributed to staff not recognising the sensitivity of data compromised in a breach\n- **CNIL v Free Mobile (2022)**: EUR 300,000 — customer personal data stored without classification or access controls; staff could access all customer data regardless of role or need\n\n## Integration Points\n\n- **classification-policy**: Labelling system is the technical implementation of the classification policy\n- **auto-data-discovery**: Discovery results trigger auto-labelling for newly detected PII\n- **pii-in-unstructured**: PII detection in documents drives label recommendation or auto-application\n- **data-inventory-mapping**: Labels feed the data inventory with current classification status per asset\n- **data-lineage-tracking**: Labels propagate through data lineage — transformed data inherits source label\n","# Data Classification Labels and Tagging System\n\n## Overview\n\nData classification labels are the operational mechanism through which classification policy is enforced across the enterprise. Labels attach classification metadata to data assets — documents, emails, database records, and cloud resources — enabling automated enforcement of handling requirements through DLP policies, access controls, and encryption. This skill covers the design and implementation of a labelling system using Microsoft Purview Information Protection as the primary platform, with architecture patterns for automated labelling, user-applied labelling, label inheritance, and cross-platform propagation.\n\n## Label Taxonomy\n\n### Vanguard Financial Services Label Hierarchy\n\n```\nVanguard Classification Labels\n├── Public\n│   └── (no sub-labels)\n├── Internal\n│   └── Internal - Project Confidential\n├── Confidential\n│   ├── Confidential - Customer Data\n│   ├── Confidential - Employee Data\n│   ├── Confidential - Financial Data\n│   └── Confidential - Legal\n└── Restricted\n    ├── Restricted - Special Category (Art. 9)\n    ├── Restricted - Criminal Data (Art. 10)\n    ├── Restricted - AML Investigation\n    └── Restricted - Board & Strategy\n```\n\n### Label Properties\n\n| Label | Colour | Visual Marking | Encryption | DLP Policy | Auto-Apply |\n|-------|--------|---------------|-----------|-----------|-----------|\n| Public | Green | Footer: \"Vanguard Financial Services — Public\" | None | None | No |\n| Internal | Blue | Footer: \"Vanguard Financial Services — Internal Use Only\" | Optional | Warn on external | No |\n| Confidential | Amber | Header + Footer: \"CONFIDENTIAL\" | Azure RMS (AES-256) | Warn + audit external; block personal email | Yes (when PII detected with >85% confidence) |\n| Restricted | Red | Header + Footer: \"RESTRICTED\" with red background; watermark on print | Azure RMS (AES-256, double key encryption) | Block all external; block USB\u002Fprint; alert DPO | Yes (when Art. 9\u002FArt. 10 data detected with >85% confidence) |\n\n## Microsoft Purview Implementation Architecture\n\n### Component Architecture\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                    Microsoft Purview                             │\n│                                                                  │\n│  ┌──────────────┐  ┌──────────────┐  ┌──────────────────────┐  │\n│  │ Sensitivity   │  │ Auto-labelling│  │ DLP Policies          │  │\n│  │ Labels        │  │ Policies      │  │ (endpoint, email,     │  │\n│  │ (definitions) │  │ (rules)       │  │  SharePoint, Teams)   │  │\n│  └──────┬───────┘  └──────┬───────┘  └──────────┬───────────┘  │\n│         │                  │                      │              │\n│         ▼                  ▼                      ▼              │\n│  ┌──────────────────────────────────────────────────────────┐   │\n│  │              Unified Label Application Engine             │   │\n│  └──────────────────────────────────────────────────────────┘   │\n│         │                  │                      │              │\n└─────────┼──────────────────┼──────────────────────┼──────────────┘\n          ▼                  ▼                      ▼\n   ┌─────────────┐  ┌──────────────┐  ┌──────────────────────┐\n   │ Office Apps  │  │ SharePoint\u002F  │  │ Endpoint DLP         │\n   │ (Word, Excel,│  │ OneDrive     │  │ (Windows devices)    │\n   │  Outlook)    │  │              │  │                      │\n   └─────────────┘  └──────────────┘  └──────────────────────┘\n```\n\n### Auto-Labelling Configuration\n\n#### Policy 1: Confidential — Customer PII Detection\n\n| Setting | Value |\n|---------|-------|\n| **Policy Name** | VFS-AutoLabel-Confidential-CustomerPII |\n| **Scope** | All SharePoint sites, OneDrive accounts, Exchange mailboxes |\n| **Conditions** | Content contains ANY of: UK National Insurance Number (HIGH confidence), IBAN (HIGH), Vanguard Account Number (HIGH), Credit Card (HIGH + Luhn validated) |\n| **Minimum count** | 1 instance of any SIT at HIGH confidence |\n| **Label applied** | Confidential - Customer Data |\n| **Priority** | 2 (overridden by Restricted auto-label) |\n\n#### Policy 2: Restricted — Special Category Detection\n\n| Setting | Value |\n|---------|-------|\n| **Policy Name** | VFS-AutoLabel-Restricted-SpecialCategory |\n| **Scope** | All SharePoint sites, OneDrive accounts, Exchange mailboxes |\n| **Conditions** | Content contains ANY of: ICD-10 codes (MEDIUM+), health terminology trainable classifier (HIGH), biometric template format detection, genetic marker patterns |\n| **Minimum count** | 1 instance at MEDIUM confidence or above |\n| **Label applied** | Restricted - Special Category (Art. 9) |\n| **Priority** | 1 (highest priority — overrides all other auto-labels) |\n\n#### Policy 3: Restricted — Criminal Data Detection\n\n| Setting | Value |\n|---------|-------|\n| **Policy Name** | VFS-AutoLabel-Restricted-CriminalData |\n| **Scope** | HR SharePoint sites, Compliance SharePoint sites |\n| **Conditions** | Content contains: DBS reference patterns, criminal conviction terminology, SAR reference numbers |\n| **Label applied** | Restricted - Criminal Data (Art. 10) |\n| **Priority** | 1 |\n\n### Label Inheritance Rules\n\n| Rule | Description | Implementation |\n|------|-------------|---------------|\n| **Container inheritance** | Items in a labelled SharePoint site inherit the site's label as minimum | Site sensitivity label propagates to new items; existing items retain higher label |\n| **Email attachment inheritance** | Attachments inherit the email's label if attachment label is lower | Outlook plugin checks attachment label vs email label on send |\n| **Parent-child inheritance** | Child documents inherit parent folder label as minimum | SharePoint library policy; items cannot be labelled below folder label |\n| **No downgrade without approval** | Users cannot remove or downgrade labels without justification | Label policy: require justification text for downgrade; audit log entry |\n| **Highest label wins** | When documents are merged or combined, the highest label applies | User training + DLP monitoring for combined documents |\n\n## User-Applied Labelling\n\n### Labelling Responsibilities\n\n| Scenario | Who Labels | How |\n|----------|-----------|-----|\n| New document creation | Author | Select label from Office ribbon (Word, Excel, PowerPoint) |\n| New email composition | Sender | Select label from Outlook toolbar; mandatory before sending external |\n| File upload to SharePoint | Uploader | Label prompt on upload if no label detected |\n| Data export from system | Exporter | Label selection required before export completes |\n| Physical document printing | Printer | Classification header\u002Ffooter printed automatically; user selects tier if not auto-labelled |\n\n### Mandatory Labelling Policy\n\n| Setting | Value |\n|---------|-------|\n| **Require label on documents** | Yes — all Word, Excel, PowerPoint documents must have a label before save |\n| **Require label on emails** | Yes — for emails to external recipients; recommended for internal |\n| **Default label** | Internal (applied if user does not select; user can override up or down) |\n| **Justification for downgrade** | Required — user must enter text justification; logged in audit |\n| **Justification for removal** | Required — DPO-approved exception only |\n\n## DLP Integration\n\n### DLP Policy Matrix\n\n| Label | External Email | USB\u002FRemovable | Print | Screenshot | Cloud Upload |\n|-------|---------------|---------------|-------|-----------|-------------|\n| Public | Allow | Allow | Allow | Allow | Allow |\n| Internal | Warn | Warn | Allow | Allow | Block (non-approved cloud) |\n| Confidential | Warn + audit | Block | Secure print | Allow (watermarked) | Block |\n| Restricted | Block | Block | Block (unless DPO approved) | Block | Block |\n\n### DLP Alert Routing\n\n| Alert Severity | Label Trigger | Routing |\n|---------------|--------------|---------|\n| Low | Internal label — external email warn overridden | Security team email |\n| Medium | Confidential label — external sharing attempted | Security team + Data Owner |\n| High | Restricted label — any policy trigger | DPO + CISO + immediate investigation |\n| Critical | Restricted label — data exfiltration indicators | DPO + CISO + Incident Response Team + 15-minute SLA |\n\n## Label Propagation Across Platforms\n\n### Supported Platforms\n\n| Platform | Label Method | Propagation |\n|----------|-------------|-------------|\n| Microsoft 365 (Word, Excel, PowerPoint) | Native sensitivity label in file metadata | Full support — label travels with file |\n| Outlook \u002F Exchange | Email header X-MS-Exchange-Organization-Classification | Label persists in message store and forwarded copies |\n| SharePoint Online | Document library metadata + file metadata | Dual storage — library and file level |\n| OneDrive for Business | File metadata | Same as SharePoint |\n| Teams | Channel\u002Fchat message metadata | Limited — file attachments inherit, message labels in compliance |\n| PDF export | Visual marking (header\u002Ffooter) + XMP metadata | Visual marking persists; metadata depends on PDF viewer |\n| Azure SQL Database | Column-level sensitivity classification (sys.sensitivity_classifications) | Native Azure SQL feature; integrates with Purview |\n| AWS S3 | Object tags (key: classification, value: tier) | AWS-native tagging; read by Macie and IAM policies |\n| On-premises file shares | File metadata (NTFS ADS) via AIP Unified Labelling client | Requires AIP client installed on endpoints |\n\n## Enforcement Precedents\n\n- **ICO v Interserve Group (2022)**: GBP 4.4 million — failure to implement adequate data classification and labelling contributed to staff not recognising the sensitivity of data compromised in a breach\n- **CNIL v Free Mobile (2022)**: EUR 300,000 — customer personal data stored without classification or access controls; staff could access all customer data regardless of role or need\n\n## Integration Points\n\n- **classification-policy**: Labelling system is the technical implementation of the classification policy\n- **auto-data-discovery**: Discovery results trigger auto-labelling for newly detected PII\n- **pii-in-unstructured**: PII detection in documents drives label recommendation or auto-application\n- **data-inventory-mapping**: Labels feed the data inventory with current classification status per asset\n- **data-lineage-tracking**: Labels propagate through data lineage — transformed data inherits source label\n",{"name":5,"license":15,"metadata":41,"description":7},{"tags":42,"author":9,"domain":31,"version":43,"subdomain":34},"data-labeling, sensitivity-labels, metadata-tagging, dlp, label-propagation, purview","1.0","main","9b2ef9eae161c00a17241d42a388571321b33e9f","skills\u002Fprivacy\u002Fdata-labeling-system",67,"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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill data-labeling-system",{"tool":59,"command":60},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill data-labeling-system",{"tool":62,"command":63},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill data-labeling-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fdata-labeling-system\u002FSKILL.md",true,[67,73,79,83],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftemplate.md","ASSET","资产文件",3191,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fdata-labeling-system\u002Fassets\u002Ftemplate.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fstandards.md","REFERENCE","参考文档",2328,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fdata-labeling-system\u002Freferences\u002Fstandards.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fworkflows.md",2668,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fdata-labeling-system\u002Freferences\u002Fworkflows.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fprocess.py","SCRIPT","脚本",10386,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fdata-labeling-system\u002Fscripts\u002Fprocess.py",[90,115,130,143,160,173],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":107,"publishedAt":36},"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",[96,101,104],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[108,109,31,110,111,24,112,113,114,29],"email","workplace email privacy","compliance","content","policy","testing","monitoring",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":123,"publishedAt":36},"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",[121,122],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[24,124,125,126,110,127,128,31,129],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":36},"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",[136],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,138,139,140,141,128,31,142],"vendor termination data","planning","verification","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":36},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[151,152,153,154,155,156,157,158,31,24,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":36},"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":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[31,168,128,169,156,170,171,24,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":36},"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":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[187,188,31,189,140,190,110,128,191,159,192,193,194,139],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]