[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF0A4K604D4S6RQXFAHDFN":3,"skill-same:01M6AF0A4K604D4S6RQXFAHDFN":90},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6AF0A4K604D4S6RQXFAHDFN","nist-pf-protect",null,"Implement the NIST Privacy Framework PROTECT function covering PR.AC access control, PR.DS data security, and PR.PO protective policies. Provides technical control implementation guidance, encryption standards, access management architectures, and security-privacy integration patterns.","mukul975\u002FPrivacy-Data-Protection-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADNKWX1HF4Q5DKEXT5M774",338,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect\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],"NIST","nist pf protect","security","implement","pr","framework","integration","engineering","privacy","data","encryption","access-control","2026-11-10 10:12:30",false,"---\nname: nist-pf-protect\ndescription: >-\n  Implement the NIST Privacy Framework PROTECT function covering PR.AC access\n  control, PR.DS data security, and PR.PO protective policies. Provides\n  technical control implementation guidance, encryption standards, access\n  management architectures, and security-privacy integration patterns.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: privacy-engineering\n  tags: \"nist-privacy-framework, protect-function, access-control, data-security, protective-policies\"\n---\n\n# NIST Privacy Framework — PROTECT Function\n\n## Overview\n\nThe PROTECT function develops and implements appropriate data processing safeguards to prevent cybersecurity-related privacy events. This function directly bridges the NIST Cybersecurity Framework and Privacy Framework, addressing the overlap where security controls serve privacy objectives. It covers access control, data security, and protective policies.\n\n## PROTECT Function Subcategories\n\n### PR.AC — Access Control\n\nManaging access to data and systems to protect privacy.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| PR.AC-P1 | Identities and credentials are issued, managed, verified, revoked, and audited for authorized individuals, processes, and devices | Implement identity lifecycle management. Enforce MFA for systems processing personal data. Conduct quarterly access reviews. |\n| PR.AC-P2 | Physical access to data and devices is managed | Restrict physical access to data centers and server rooms. Implement visitor logging. Secure endpoint devices with encryption and remote wipe capability. |\n| PR.AC-P3 | Remote access is managed | Enforce VPN for remote access to personal data systems. Implement zero-trust network architecture. Monitor and log all remote sessions. |\n| PR.AC-P4 | Access permissions and authorizations are managed with least privilege and separation of duties | Implement role-based access control (RBAC). Enforce separation of duties for sensitive operations. Regular privileged access reviews. |\n| PR.AC-P5 | Network integrity is protected | Network segmentation for systems processing personal data. Intrusion detection\u002Fprevention systems. Encrypted network communications. |\n| PR.AC-P6 | Individuals and devices are proofed and bound to credentials | Implement strong identity verification for data subject account creation. Device certificate management. Biometric authentication where appropriate. |\n\n### PR.DS — Data Security\n\nProtecting data at rest, in transit, and during processing.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| PR.DS-P1 | Data-at-rest are protected | AES-256 encryption for stored personal data. Key management with HSM. Database-level encryption (TDE). |\n| PR.DS-P2 | Data-in-transit are protected | TLS 1.3 for all data transmissions. Certificate pinning for mobile applications. End-to-end encryption for sensitive communications. |\n| PR.DS-P3 | Systems\u002Fproducts\u002Fservices and associated data are formally managed throughout removal, transfers, and disposition | Secure media sanitization (NIST SP 800-88). Certificate of destruction for physical media. Verified data deletion from cloud services. |\n| PR.DS-P4 | Adequate capacity to ensure availability is maintained | Capacity planning for privacy-critical systems. DDoS protection. Redundancy for data subject rights portals. |\n| PR.DS-P5 | Protections against data leaks are implemented | DLP solutions monitoring egress points. Email DLP for personal data. Cloud access security broker (CASB) deployment. |\n| PR.DS-P6 | Integrity checking mechanisms are used to verify software, firmware, and information integrity | File integrity monitoring for privacy-critical systems. Code signing for privacy-related applications. Checksum verification for data transfers. |\n| PR.DS-P7 | The development and testing environment(s) are separate from the production environment | Separate environments with no production personal data in dev\u002Ftest. Synthetic data generation for testing. Access controls between environments. |\n| PR.DS-P8 | Data disclosures are consistent with the purposes for which the data were collected | Technical enforcement of purpose limitation. API-level access controls tied to documented purposes. Automated purpose verification at query time. |\n\n### PR.PO — Protective Policies\n\nPolicies governing protective measures for privacy.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| PR.PO-P1 | A baseline configuration of information technology\u002Findustrial control systems is created and maintained | Establish secure baselines for all systems processing personal data. Configuration management database. Automated compliance scanning. |\n| PR.PO-P2 | Configuration change control processes are in place | Change advisory board review for privacy-impacting changes. Impact assessment for configuration changes. Rollback procedures documented. |\n| PR.PO-P3 | Backups of information are conducted, maintained, and tested | Encrypted backups of personal data. Regular restoration testing. Backup retention aligned with data retention policies. |\n| PR.PO-P4 | Policy and regulations regarding the physical operating environment are met | Environmental controls for data processing facilities. Compliance with data residency requirements. Physical security audits. |\n| PR.PO-P5 | Data destruction processes are defined and managed | Documented destruction procedures per data classification. Verification and certification of destruction. Compliant disposal of hardware containing personal data. |\n| PR.PO-P6 | Maintenance and repair of organizational assets are performed and logged | Vendor supervision during maintenance. Data sanitization before equipment service. Maintenance activity logging. |\n| PR.PO-P7 | Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed | Privacy-integrated incident response plan. Business continuity for privacy-critical services. Regular tabletop exercises. |\n| PR.PO-P8 | Response and recovery plans are tested | Annual incident response exercises including privacy scenarios. DR testing with privacy recovery objectives. Post-exercise improvement plans. |\n| PR.PO-P9 | Privacy procedures are included in human resources practices | Background checks for privacy-sensitive roles. Confidentiality agreements. Exit procedures including access revocation. |\n| PR.PO-P10 | A vulnerability management plan is developed and implemented | Vulnerability scanning for privacy-critical systems. Patch management prioritizing privacy-impacting vulnerabilities. Penetration testing including privacy controls. |\n\n## Technical Control Architecture\n\n### Access Control Architecture\n\n```\nIdentity Provider (IdP)\n    |\n    v\nMulti-Factor Authentication\n    |\n    v\nAuthorization Engine (RBAC + ABAC)\n    |\n    +-- Role-Based Access Control\n    |   ├── Privacy Administrator\n    |   ├── Data Steward\n    |   ├── Data Processor\n    |   ├── Data Analyst (aggregated only)\n    |   └── Data Subject (own data only)\n    |\n    +-- Attribute-Based Access Control\n    |   ├── Purpose attribute (why accessing)\n    |   ├── Data classification (sensitivity level)\n    |   ├── Time-based restrictions\n    |   └── Location-based restrictions\n    |\n    v\nAudit Logging Engine\n```\n\n### Encryption Standards\n\n| Data State | Minimum Standard | Recommended Standard | Key Management |\n|-----------|-----------------|---------------------|----------------|\n| At Rest | AES-128 | AES-256 | HSM-managed keys, annual rotation |\n| In Transit | TLS 1.2 | TLS 1.3 | Certificate management with auto-renewal |\n| In Processing | Application-level encryption | Envelope encryption | Per-session keys |\n| Backup | AES-256 | AES-256 + separate key | Offline key escrow |\n| Archive | AES-256 | AES-256 + integrity check | Long-term key management |\n\n### Data Loss Prevention Configuration\n\n| Channel | DLP Control | Detection Method | Action |\n|---------|------------|-----------------|--------|\n| Email | Email gateway DLP | Pattern matching (SSN, CC, IBAN) | Block + notify |\n| Web upload | Web proxy DLP | Content inspection | Block + notify |\n| Cloud storage | CASB | Classification labels | Encrypt + restrict sharing |\n| Endpoint | Endpoint DLP | File content scanning | Prevent copy to removable media |\n| Database | Database activity monitoring | Query analysis | Alert on bulk extraction |\n| API | API gateway | Payload inspection | Rate limit + log |\n\n## Network Security for Privacy\n\n### Segmentation Architecture\n\n```\nInternet\n    |\n    v\n[DMZ \u002F WAF]\n    |\n    v\n[Application Tier] ── TLS 1.3 ── [API Gateway]\n    |                                    |\n    v                                    v\n[Business Logic Tier]            [Privacy Services Tier]\n    |                            ├── Consent Manager\n    v                            ├── DSR Processor\n[Data Tier]                      ├── Anonymization Engine\n├── PII Database (encrypted)     └── Audit Logger\n├── Analytics Database (aggregated)\n└── Backup Storage (encrypted, isolated)\n```\n\n## Control Mapping\n\n| NIST PF PROTECT | NIST CSF | ISO 27701 | GDPR Article |\n|-----------------|----------|-----------|--------------|\n| PR.AC-P1 | PR.AC-1 | A.7.2.2 | Art. 32(1)(b) |\n| PR.AC-P4 | PR.AC-4 | A.7.2.2 | Art. 25(2) |\n| PR.DS-P1 | PR.DS-1 | A.7.4.9 | Art. 32(1)(a) |\n| PR.DS-P2 | PR.DS-2 | A.7.4.9 | Art. 32(1)(a) |\n| PR.DS-P5 | PR.DS-5 | A.7.4.9 | Art. 32(1)(b) |\n| PR.DS-P7 | PR.DS-7 | A.7.4.9 | Art. 32(1)(a) |\n| PR.DS-P8 | N\u002FA | A.7.2.2 | Art. 5(1)(b) |\n| PR.PO-P3 | PR.IP-4 | A.7.4.9 | Art. 32(1)(c) |\n| PR.PO-P5 | PR.IP-6 | A.7.4.7 | Art. 17(1) |\n| PR.PO-P7 | PR.IP-9 | A.7.2.8 | Art. 33, 34 |\n| PR.PO-P10 | PR.IP-12 | A.7.4.9 | Art. 32(1)(d) |\n\n## References\n\n- NIST Privacy Framework Version 1.0 (January 16, 2020)\n- NIST Cybersecurity Framework Version 1.1 (April 16, 2018)\n- NIST SP 800-53 Rev. 5 — Security and Privacy Controls for Information Systems\n- NIST SP 800-88 Rev. 1 — Guidelines for Media Sanitization\n- NIST SP 800-175B — Guideline for Using Cryptographic Standards\n","# NIST Privacy Framework — PROTECT Function\n\n## Overview\n\nThe PROTECT function develops and implements appropriate data processing safeguards to prevent cybersecurity-related privacy events. This function directly bridges the NIST Cybersecurity Framework and Privacy Framework, addressing the overlap where security controls serve privacy objectives. It covers access control, data security, and protective policies.\n\n## PROTECT Function Subcategories\n\n### PR.AC — Access Control\n\nManaging access to data and systems to protect privacy.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| PR.AC-P1 | Identities and credentials are issued, managed, verified, revoked, and audited for authorized individuals, processes, and devices | Implement identity lifecycle management. Enforce MFA for systems processing personal data. Conduct quarterly access reviews. |\n| PR.AC-P2 | Physical access to data and devices is managed | Restrict physical access to data centers and server rooms. Implement visitor logging. Secure endpoint devices with encryption and remote wipe capability. |\n| PR.AC-P3 | Remote access is managed | Enforce VPN for remote access to personal data systems. Implement zero-trust network architecture. Monitor and log all remote sessions. |\n| PR.AC-P4 | Access permissions and authorizations are managed with least privilege and separation of duties | Implement role-based access control (RBAC). Enforce separation of duties for sensitive operations. Regular privileged access reviews. |\n| PR.AC-P5 | Network integrity is protected | Network segmentation for systems processing personal data. Intrusion detection\u002Fprevention systems. Encrypted network communications. |\n| PR.AC-P6 | Individuals and devices are proofed and bound to credentials | Implement strong identity verification for data subject account creation. Device certificate management. Biometric authentication where appropriate. |\n\n### PR.DS — Data Security\n\nProtecting data at rest, in transit, and during processing.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| PR.DS-P1 | Data-at-rest are protected | AES-256 encryption for stored personal data. Key management with HSM. Database-level encryption (TDE). |\n| PR.DS-P2 | Data-in-transit are protected | TLS 1.3 for all data transmissions. Certificate pinning for mobile applications. End-to-end encryption for sensitive communications. |\n| PR.DS-P3 | Systems\u002Fproducts\u002Fservices and associated data are formally managed throughout removal, transfers, and disposition | Secure media sanitization (NIST SP 800-88). Certificate of destruction for physical media. Verified data deletion from cloud services. |\n| PR.DS-P4 | Adequate capacity to ensure availability is maintained | Capacity planning for privacy-critical systems. DDoS protection. Redundancy for data subject rights portals. |\n| PR.DS-P5 | Protections against data leaks are implemented | DLP solutions monitoring egress points. Email DLP for personal data. Cloud access security broker (CASB) deployment. |\n| PR.DS-P6 | Integrity checking mechanisms are used to verify software, firmware, and information integrity | File integrity monitoring for privacy-critical systems. Code signing for privacy-related applications. Checksum verification for data transfers. |\n| PR.DS-P7 | The development and testing environment(s) are separate from the production environment | Separate environments with no production personal data in dev\u002Ftest. Synthetic data generation for testing. Access controls between environments. |\n| PR.DS-P8 | Data disclosures are consistent with the purposes for which the data were collected | Technical enforcement of purpose limitation. API-level access controls tied to documented purposes. Automated purpose verification at query time. |\n\n### PR.PO — Protective Policies\n\nPolicies governing protective measures for privacy.\n\n| Subcategory | Description | Implementation Guidance |\n|-------------|-------------|------------------------|\n| PR.PO-P1 | A baseline configuration of information technology\u002Findustrial control systems is created and maintained | Establish secure baselines for all systems processing personal data. Configuration management database. Automated compliance scanning. |\n| PR.PO-P2 | Configuration change control processes are in place | Change advisory board review for privacy-impacting changes. Impact assessment for configuration changes. Rollback procedures documented. |\n| PR.PO-P3 | Backups of information are conducted, maintained, and tested | Encrypted backups of personal data. Regular restoration testing. Backup retention aligned with data retention policies. |\n| PR.PO-P4 | Policy and regulations regarding the physical operating environment are met | Environmental controls for data processing facilities. Compliance with data residency requirements. Physical security audits. |\n| PR.PO-P5 | Data destruction processes are defined and managed | Documented destruction procedures per data classification. Verification and certification of destruction. Compliant disposal of hardware containing personal data. |\n| PR.PO-P6 | Maintenance and repair of organizational assets are performed and logged | Vendor supervision during maintenance. Data sanitization before equipment service. Maintenance activity logging. |\n| PR.PO-P7 | Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed | Privacy-integrated incident response plan. Business continuity for privacy-critical services. Regular tabletop exercises. |\n| PR.PO-P8 | Response and recovery plans are tested | Annual incident response exercises including privacy scenarios. DR testing with privacy recovery objectives. Post-exercise improvement plans. |\n| PR.PO-P9 | Privacy procedures are included in human resources practices | Background checks for privacy-sensitive roles. Confidentiality agreements. Exit procedures including access revocation. |\n| PR.PO-P10 | A vulnerability management plan is developed and implemented | Vulnerability scanning for privacy-critical systems. Patch management prioritizing privacy-impacting vulnerabilities. Penetration testing including privacy controls. |\n\n## Technical Control Architecture\n\n### Access Control Architecture\n\n```\nIdentity Provider (IdP)\n    |\n    v\nMulti-Factor Authentication\n    |\n    v\nAuthorization Engine (RBAC + ABAC)\n    |\n    +-- Role-Based Access Control\n    |   ├── Privacy Administrator\n    |   ├── Data Steward\n    |   ├── Data Processor\n    |   ├── Data Analyst (aggregated only)\n    |   └── Data Subject (own data only)\n    |\n    +-- Attribute-Based Access Control\n    |   ├── Purpose attribute (why accessing)\n    |   ├── Data classification (sensitivity level)\n    |   ├── Time-based restrictions\n    |   └── Location-based restrictions\n    |\n    v\nAudit Logging Engine\n```\n\n### Encryption Standards\n\n| Data State | Minimum Standard | Recommended Standard | Key Management |\n|-----------|-----------------|---------------------|----------------|\n| At Rest | AES-128 | AES-256 | HSM-managed keys, annual rotation |\n| In Transit | TLS 1.2 | TLS 1.3 | Certificate management with auto-renewal |\n| In Processing | Application-level encryption | Envelope encryption | Per-session keys |\n| Backup | AES-256 | AES-256 + separate key | Offline key escrow |\n| Archive | AES-256 | AES-256 + integrity check | Long-term key management |\n\n### Data Loss Prevention Configuration\n\n| Channel | DLP Control | Detection Method | Action |\n|---------|------------|-----------------|--------|\n| Email | Email gateway DLP | Pattern matching (SSN, CC, IBAN) | Block + notify |\n| Web upload | Web proxy DLP | Content inspection | Block + notify |\n| Cloud storage | CASB | Classification labels | Encrypt + restrict sharing |\n| Endpoint | Endpoint DLP | File content scanning | Prevent copy to removable media |\n| Database | Database activity monitoring | Query analysis | Alert on bulk extraction |\n| API | API gateway | Payload inspection | Rate limit + log |\n\n## Network Security for Privacy\n\n### Segmentation Architecture\n\n```\nInternet\n    |\n    v\n[DMZ \u002F WAF]\n    |\n    v\n[Application Tier] ── TLS 1.3 ── [API Gateway]\n    |                                    |\n    v                                    v\n[Business Logic Tier]            [Privacy Services Tier]\n    |                            ├── Consent Manager\n    v                            ├── DSR Processor\n[Data Tier]                      ├── Anonymization Engine\n├── PII Database (encrypted)     └── Audit Logger\n├── Analytics Database (aggregated)\n└── Backup Storage (encrypted, isolated)\n```\n\n## Control Mapping\n\n| NIST PF PROTECT | NIST CSF | ISO 27701 | GDPR Article |\n|-----------------|----------|-----------|--------------|\n| PR.AC-P1 | PR.AC-1 | A.7.2.2 | Art. 32(1)(b) |\n| PR.AC-P4 | PR.AC-4 | A.7.2.2 | Art. 25(2) |\n| PR.DS-P1 | PR.DS-1 | A.7.4.9 | Art. 32(1)(a) |\n| PR.DS-P2 | PR.DS-2 | A.7.4.9 | Art. 32(1)(a) |\n| PR.DS-P5 | PR.DS-5 | A.7.4.9 | Art. 32(1)(b) |\n| PR.DS-P7 | PR.DS-7 | A.7.4.9 | Art. 32(1)(a) |\n| PR.DS-P8 | N\u002FA | A.7.2.2 | Art. 5(1)(b) |\n| PR.PO-P3 | PR.IP-4 | A.7.4.9 | Art. 32(1)(c) |\n| PR.PO-P5 | PR.IP-6 | A.7.4.7 | Art. 17(1) |\n| PR.PO-P7 | PR.IP-9 | A.7.2.8 | Art. 33, 34 |\n| PR.PO-P10 | PR.IP-12 | A.7.4.9 | Art. 32(1)(d) |\n\n## References\n\n- NIST Privacy Framework Version 1.0 (January 16, 2020)\n- NIST Cybersecurity Framework Version 1.1 (April 16, 2018)\n- NIST SP 800-53 Rev. 5 — Security and Privacy Controls for Information Systems\n- NIST SP 800-88 Rev. 1 — Guidelines for Media Sanitization\n- NIST SP 800-175B — Guideline for Using Cryptographic Standards\n",{"name":5,"license":15,"metadata":41,"description":7},{"tags":42,"author":9,"domain":32,"version":43,"subdomain":44},"nist-privacy-framework, protect-function, access-control, data-security, protective-policies","1.0","privacy-engineering","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill nist-pf-protect",{"tool":60,"command":61},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill nist-pf-protect",{"tool":63,"command":64},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill nist-pf-protect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect\u002FSKILL.md",true,[68,74,80,84],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Ftemplate.md","ASSET","资产文件",1347,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect\u002Fassets\u002Ftemplate.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstandards.md","REFERENCE","参考文档",1188,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect\u002Freferences\u002Fstandards.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fworkflows.md",1821,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect\u002Freferences\u002Fworkflows.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fprocess.py","SCRIPT","脚本",7650,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-skills-complete\u002Fskills\u002Fnist-pf-protect\u002Fscripts\u002Fprocess.py",[91,117,132,145,162,175],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":108,"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",[97,102,105],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[109,110,32,111,112,33,113,114,115,116],"email","workplace email privacy","compliance","content","policy","testing","monitoring","metadata",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":125,"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",[123,124],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[33,126,127,128,111,129,130,32,131],"whistleblower data","identity","reporting","data protection","gdpr","prevention",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"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",[138],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[33,140,141,142,143,130,32,144],"vendor termination data","planning","verification","extraction","certification",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"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",[151],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[153,154,155,156,157,158,159,160,32,33,161],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","assessment","transfer","certifications","processor",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"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",[168],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[32,170,130,171,158,172,173,33,161,154,144,174],"vendor privacy due diligence","review","onboarding","flow","analysis",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":188,"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",[181,184,187],{"categoryNo":182,"categoryName":183,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[189,190,32,191,142,192,111,130,193,161,194,195,196,141],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]