[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPJVR2FNVX8NCTHTK9EVJT":3,"skill-same:01M7EPJVR2FNVX8NCTHTK9EVJT":82},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7EPJVR2FNVX8NCTHTK9EVJT","performing-access-review-and-certification",null,"Designs and runs access review and certification campaigns-scoping, reviewer selection, risk-based prioritization, micro-certification, and remediation tracking-to verify user access matches job roles for SOX, HIPAA, and PCI DSS compliance. Use when planning or executing periodic access recertification or preparing evidence for an IAM compliance audit.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-access-review-and-certification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-access-review-and-certification\ndescription: Designs and runs access review and certification campaigns-scoping,\n  reviewer selection, risk-based prioritization, micro-certification, and remediation\n  tracking-to verify user access matches job roles for SOX, HIPAA, and PCI DSS compliance.\n  Use when planning or executing periodic access recertification or preparing evidence\n  for an IAM compliance audit.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- access-review\n- certification\n- compliance\n- governance\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\n---\n# Performing Access Review and Certification\n\n## Overview\nConduct systematic access reviews and certifications to ensure users have appropriate access rights aligned with their roles. This skill covers review campaign design, reviewer selection, risk-based prioritization, micro-certification strategies, and remediation tracking for compliance with SOX, HIPAA, and PCI DSS requirements.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing access review and certification\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Design and execute access review campaigns across enterprise applications\n- Implement risk-based prioritization for review scope\n- Configure reviewer selection (manager, application owner, hybrid)\n- Automate entitlement data collection and presentation\n- Track remediation of inappropriate access findings\n- Generate compliance evidence for auditors\n\n## Key Concepts\n\n### Access Review Types\n1. **User Access Review**: Manager certifies all entitlements for their direct reports\n2. **Entitlement Review**: Application owner certifies all users with specific entitlement\n3. **Role Review**: Role owner certifies role membership and permissions\n4. **Privileged Access Review**: Security team reviews high-risk\u002Fprivileged access\n5. **SOD Review**: Verify no users have conflicting separation-of-duty violations\n\n### Risk-Based Prioritization\n- **High Risk**: Privileged access, financial systems, PII\u002FPHI systems, external-facing apps\n- **Medium Risk**: Internal business applications, shared drives, collaboration tools\n- **Low Risk**: Standard employee tools, read-only access, public information systems\n\n### Review Campaign Lifecycle\n1. **Planning**: Define scope, reviewers, timeline, escalation\n2. **Data Collection**: Aggregate entitlements from all identity sources\n3. **Distribution**: Assign review items to appropriate certifiers\n4. **Certification**: Reviewers approve or revoke each entitlement\n5. **Remediation**: Revoke inappropriate access, enforce timeline\n6. **Reporting**: Generate compliance evidence and metrics\n7. **Closure**: Archive campaign, feed findings into next cycle\n\n## Workflow\n\n### Step 1: Define Review Scope and Schedule\n- Identify in-scope applications and systems\n- Determine review frequency: quarterly (SOX), semi-annual, annual\n- Define campaign timeline: review period, escalation dates, hard close\n- Establish escalation chain for non-responsive reviewers\n\n### Step 2: Data Collection and Aggregation\n- Extract user-entitlement mappings from each application\n- Correlate with HR data (active employees, role, department, manager)\n- Identify terminated\u002Ftransferred users still holding access\n- Flag high-risk entitlements (admin, DBA, system, privileged)\n- Calculate risk scores based on entitlement sensitivity and user role\n\n### Step 3: Reviewer Assignment\n- **Manager Reviews**: Direct manager certifies subordinate access\n- **Application Owner Reviews**: App owner certifies all users of their application\n- **Hybrid Model**: Manager reviews standard access, app owner reviews privileged\n- **Delegate Management**: Allow reviewers to delegate with audit trail\n\n### Step 4: Execute Certification Campaign\n- Send notifications to reviewers with clear instructions\n- Present entitlements with context (last used date, risk level, role justification)\n- Require reviewers to explicitly approve or revoke each item\n- Track completion percentage and send reminders\n- Escalate to management after deadline\n\n### Step 5: Remediation and Tracking\n- Automatically ticket revocations to IT operations\n- Set SLA for revocation execution (24-48 hours for high-risk)\n- Verify revocation completed (re-check entitlement)\n- Exception management for business-justified deviations\n- Document all exceptions with expiration dates\n\n### Step 6: Reporting and Evidence\n- Generate campaign completion metrics\n- Produce per-application compliance reports\n- Create audit-ready evidence packages\n- Track trends across review cycles\n- Feed findings into risk assessment process\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Access Review | AC-2(3) | Periodic review of account privileges |\n| Account Management | AC-2 | Account lifecycle management |\n| Least Privilege | AC-6 | Minimum necessary access enforcement |\n| Separation of Duties | AC-5 | SOD conflict identification |\n| Audit Logging | AU-6 | Review of access audit records |\n\n## Common Pitfalls\n- Rubber-stamping: reviewers approving all access without examination\n- Incomplete scope: missing critical applications from review campaigns\n- No remediation tracking: revoking access on paper but not in systems\n- Inconsistent reviewer assignment causing gaps in coverage\n- Not including service accounts and non-human identities\n\n## Verification\n- [ ] All in-scope applications included in campaign\n- [ ] Reviewers assigned for 100% of entitlements\n- [ ] Campaign completion rate exceeds 95%\n- [ ] Revocations executed within SLA\n- [ ] Audit evidence package complete and archived\n- [ ] SOD violations identified and documented\n- [ ] Exceptions documented with business justification and expiry\n","# Performing Access Review and Certification\n\n## Overview\nConduct systematic access reviews and certifications to ensure users have appropriate access rights aligned with their roles. This skill covers review campaign design, reviewer selection, risk-based prioritization, micro-certification strategies, and remediation tracking for compliance with SOX, HIPAA, and PCI DSS requirements.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing access review and certification\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Design and execute access review campaigns across enterprise applications\n- Implement risk-based prioritization for review scope\n- Configure reviewer selection (manager, application owner, hybrid)\n- Automate entitlement data collection and presentation\n- Track remediation of inappropriate access findings\n- Generate compliance evidence for auditors\n\n## Key Concepts\n\n### Access Review Types\n1. **User Access Review**: Manager certifies all entitlements for their direct reports\n2. **Entitlement Review**: Application owner certifies all users with specific entitlement\n3. **Role Review**: Role owner certifies role membership and permissions\n4. **Privileged Access Review**: Security team reviews high-risk\u002Fprivileged access\n5. **SOD Review**: Verify no users have conflicting separation-of-duty violations\n\n### Risk-Based Prioritization\n- **High Risk**: Privileged access, financial systems, PII\u002FPHI systems, external-facing apps\n- **Medium Risk**: Internal business applications, shared drives, collaboration tools\n- **Low Risk**: Standard employee tools, read-only access, public information systems\n\n### Review Campaign Lifecycle\n1. **Planning**: Define scope, reviewers, timeline, escalation\n2. **Data Collection**: Aggregate entitlements from all identity sources\n3. **Distribution**: Assign review items to appropriate certifiers\n4. **Certification**: Reviewers approve or revoke each entitlement\n5. **Remediation**: Revoke inappropriate access, enforce timeline\n6. **Reporting**: Generate compliance evidence and metrics\n7. **Closure**: Archive campaign, feed findings into next cycle\n\n## Workflow\n\n### Step 1: Define Review Scope and Schedule\n- Identify in-scope applications and systems\n- Determine review frequency: quarterly (SOX), semi-annual, annual\n- Define campaign timeline: review period, escalation dates, hard close\n- Establish escalation chain for non-responsive reviewers\n\n### Step 2: Data Collection and Aggregation\n- Extract user-entitlement mappings from each application\n- Correlate with HR data (active employees, role, department, manager)\n- Identify terminated\u002Ftransferred users still holding access\n- Flag high-risk entitlements (admin, DBA, system, privileged)\n- Calculate risk scores based on entitlement sensitivity and user role\n\n### Step 3: Reviewer Assignment\n- **Manager Reviews**: Direct manager certifies subordinate access\n- **Application Owner Reviews**: App owner certifies all users of their application\n- **Hybrid Model**: Manager reviews standard access, app owner reviews privileged\n- **Delegate Management**: Allow reviewers to delegate with audit trail\n\n### Step 4: Execute Certification Campaign\n- Send notifications to reviewers with clear instructions\n- Present entitlements with context (last used date, risk level, role justification)\n- Require reviewers to explicitly approve or revoke each item\n- Track completion percentage and send reminders\n- Escalate to management after deadline\n\n### Step 5: Remediation and Tracking\n- Automatically ticket revocations to IT operations\n- Set SLA for revocation execution (24-48 hours for high-risk)\n- Verify revocation completed (re-check entitlement)\n- Exception management for business-justified deviations\n- Document all exceptions with expiration dates\n\n### Step 6: Reporting and Evidence\n- Generate campaign completion metrics\n- Produce per-application compliance reports\n- Create audit-ready evidence packages\n- Track trends across review cycles\n- Feed findings into risk assessment process\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Access Review | AC-2(3) | Periodic review of account privileges |\n| Account Management | AC-2 | Account lifecycle management |\n| Least Privilege | AC-6 | Minimum necessary access enforcement |\n| Separation of Duties | AC-5 | SOD conflict identification |\n| Audit Logging | AU-6 | Review of access audit records |\n\n## Common Pitfalls\n- Rubber-stamping: reviewers approving all access without examination\n- Incomplete scope: missing critical applications from review campaigns\n- No remediation tracking: revoking access on paper but not in systems\n- Inconsistent reviewer assignment causing gaps in coverage\n- Not including service accounts and non-human identities\n\n## Verification\n- [ ] All in-scope applications included in campaign\n- [ ] Reviewers assigned for 100% of entitlements\n- [ ] Campaign completion rate exceeds 95%\n- [ ] Revocations executed within SLA\n- [ ] Audit evidence package complete and archived\n- [ ] SOD violations identified and documented\n- [ ] Exceptions documented with business justification and expiry\n",{"name":5,"tags":24,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41},[25,26,27,28,29,30,31],"iam","identity","access-control","access-review","certification","compliance","governance","mahipal","cybersecurity","1.0",[36,37,38,39],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[42,43,44,45],"T1078","T1110","T1556","T1098","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fperforming-access-review-and-certification",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-access-review-and-certification",{"tool":60,"command":61},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-access-review-and-certification",{"tool":63,"command":64},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-access-review-and-certification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-access-review-and-certification\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fapi-reference.md","REFERENCE","参考文档",1455,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-access-review-and-certification\u002Freferences\u002Fapi-reference.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fstandards.md",1058,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-access-review-and-certification\u002Freferences\u002Fstandards.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fworkflows.md",2317,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-access-review-and-certification\u002Freferences\u002Fworkflows.md",[83,92,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":93,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":91},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":91},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":91},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":91},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":91},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]