[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFJNE8VSJVHE4X2FHYFSP9":3,"skill-same:01M6AFJNE8VSJVHE4X2FHYFSP9":161},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":94,"commitSha":95,"skillDirectory":96,"forksCount":97,"repositoryHtmlUrl":98,"repositoryHomepageUrl":99,"ownerHtmlUrl":100,"ownerBlogUrl":101,"ownerDescription":102,"updatedAt":103,"install":104,"resources":117},"01M6AFJNE8VSJVHE4X2FHYFSP9","performing-access-recertification-with-saviynt",null,"Configure and execute access recertification campaigns in Saviynt Enterprise Identity Cloud to validate user entitlements, revoke excessive access, and maintain compliance with SOX, SOC 2, and HIPAA. Use when launching or managing certification campaigns for users\u002Fentitlements, remediating access review findings, or documenting identity governance evidence for an audit.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35884,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"performing access recertification with saviynt","identity-governance","certification-campaign","access-recertification","saviynt","t1098","initial-access","t1078","defense","IGA","review","Enterprise","hipaa","soc","compliance","audit","development","pr","identity","cybersecurity","2026-11-10 10:12:30",false,"---\nname: performing-access-recertification-with-saviynt\ndescription: Configure and execute access recertification campaigns in Saviynt Enterprise\n  Identity Cloud to validate user entitlements, revoke excessive access, and maintain\n  compliance with SOX, SOC 2, and HIPAA. Use when launching or managing certification\n  campaigns for users\u002Fentitlements, remediating access review findings, or documenting\n  identity governance evidence for an audit.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- saviynt\n- access-recertification\n- identity-governance\n- compliance\n- certification-campaign\n- iga\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- T1071\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - defense-impairment\n  - resource-development\n  techniques:\n  - id: T1586\n    name: Compromise Accounts\n    tactic: resource-development\n    source: attack\n  - id: F1033\n    name: Insider Access Abuse\n    tactic: initial-access\n    source: f3\n  - id: F1005\n    name: Account Manipulation\n    tactic: positioning\n    source: f3\n  - id: F1005.002\n    name: 'Account Manipulation: Add Authorized User'\n    tactic: positioning\n    source: f3\n  - id: F1005.007\n    name: 'Account Manipulation: Enable Account Features'\n    tactic: defense-impairment\n    source: f3\n---\n\n# Performing Access Recertification with Saviynt\n\n## Overview\n\nAccess recertification (also called access certification or access review) is a periodic process where designated reviewers validate that users have appropriate access to systems and data. Saviynt Enterprise Identity Cloud (EIC) automates this process through certification campaigns that present reviewers with current access assignments and collect approve\u002Frevoke\u002Fconditionally-certify decisions. Campaigns can be triggered on schedule (quarterly, semi-annually), event-driven (department transfer, role change), or on-demand. Saviynt provides intelligence features including risk scoring, usage analytics, and peer-group analysis to help reviewers make informed decisions.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing access recertification with saviynt\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- Saviynt Enterprise Identity Cloud (EIC) tenant with admin access\n- Identity data synchronized from authoritative sources (HR, AD, cloud)\n- Entitlement data imported from target applications\n- Certifier roles assigned (managers, application owners, data owners)\n- Campaign templates defined for each certification type\n\n## Core Concepts\n\n### Campaign Types\n\n| Type | Scope | Trigger | Certifier |\n|------|-------|---------|-----------|\n| User Manager | All access for users under a manager | Scheduled (quarterly) | Direct manager |\n| Entitlement Owner | All users with a specific entitlement | Scheduled (semi-annually) | Entitlement\u002Fapp owner |\n| Application | All access to a specific application | Scheduled | Application owner |\n| Role-Based | All users assigned to a specific role | Scheduled | Role owner |\n| Event-Based | Users whose attributes changed | Attribute change trigger | New manager |\n| Micro-Certification | Single user, single entitlement | On-demand | Manager or owner |\n\n### Certification Decisions\n\n| Decision | Effect | Use Case |\n|----------|--------|----------|\n| Certify (Approve) | Access maintained | Access is still required |\n| Revoke | Access removal ticket created | Access no longer needed |\n| Conditionally Certify | Access maintained with conditions | Access needed temporarily, review again |\n| Delegate | Reassign to another certifier | Certifier lacks knowledge to decide |\n| Abstain | No decision recorded | Conflict of interest |\n\n### Campaign Lifecycle\n\n```\nCONFIGURATION → PREVIEW → ACTIVE → IN PROGRESS → COMPLETED → REMEDIATION\n       │            │         │          │             │            │\n       │            │         │          │             │            └── Revoke tickets\n       │            │         │          │             │                executed\n       │            │         │          │             │\n       │            │         │          │             └── All decisions\n       │            │         │          │                 collected\n       │            │         │          │\n       │            │         │          └── Certifiers reviewing\n       │            │         │              and making decisions\n       │            │         │\n       │            │         └── Campaign launched,\n       │            │             notifications sent\n       │            │\n       │            └── Read-only preview for validation\n       │\n       └── Campaign parameters defined\n```\n\n## Workflow\n\n### Step 1: Configure Campaign Template\n\nIn Saviynt Admin Console:\n\n1. Navigate to **Certifications > Campaign > Create New Campaign**\n2. Define campaign parameters:\n\n| Parameter | Value |\n|-----------|-------|\n| Campaign Name | Q1 2025 Manager Access Review |\n| Campaign Type | User Manager |\n| Description | Quarterly review of all user access |\n| Certifier Type | Manager (dynamic - user's direct manager) |\n| Secondary Certifier | Application Owner (fallback if manager unavailable) |\n| Due Date | 14 days from launch |\n| Reminder Schedule | Day 7, Day 10, Day 13 |\n| Escalation | Auto-revoke on Day 15 if no decision |\n\n3. Configure scope filters:\n   - Include: All active users\n   - Exclude: Service accounts, break-glass accounts\n   - Application filter: All connected applications\n\n4. Configure intelligence features:\n   - Enable risk scoring (high-risk entitlements highlighted)\n   - Enable usage data (last access date shown)\n   - Enable peer analysis (compare access to peer group)\n   - Enable SoD violation flagging\n\n### Step 2: Configure Certifier Experience\n\nCustomize what certifiers see during the review:\n\n**Columns Displayed:**\n- User name and title\n- Application name\n- Entitlement\u002Frole name\n- Risk score (1-10)\n- Last access date\n- Peer group comparison (% of peers with same access)\n- SoD violation flag\n\n**Decision Options:**\n- Certify with justification (free text)\n- Revoke with reason (dropdown: no longer needed, SoD conflict, role change)\n- Conditionally certify with expiry date\n\n**Bulk Actions:**\n- Certify all low-risk items\n- Revoke all items not accessed in 90+ days\n- Filter by application, risk level, or SoD status\n\n### Step 3: Launch Campaign via API\n\n```python\nimport requests\n\nSAVIYNT_URL = \"https:\u002F\u002Ftenant.saviyntcloud.com\"\nSAVIYNT_TOKEN = \"your-api-token\"\n\ndef create_certification_campaign(campaign_config):\n    \"\"\"Create and launch a Saviynt certification campaign.\"\"\"\n    headers = {\n        \"Authorization\": f\"Bearer {SAVIYNT_TOKEN}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n\n    # Create campaign\n    response = requests.post(\n        f\"{SAVIYNT_URL}\u002FECM\u002Fapi\u002Fv5\u002FcreateCampaign\",\n        headers=headers,\n        json={\n            \"campaignname\": campaign_config[\"name\"],\n            \"campaigntype\": campaign_config[\"type\"],\n            \"description\": campaign_config[\"description\"],\n            \"certifier\": campaign_config[\"certifier_type\"],\n            \"duedate\": campaign_config[\"due_date\"],\n            \"reminderdays\": campaign_config[\"reminder_days\"],\n            \"autorevoke\": campaign_config.get(\"auto_revoke\", True),\n            \"autorevokedays\": campaign_config.get(\"auto_revoke_days\", 15),\n            \"scope\": campaign_config.get(\"scope\", {}),\n        }\n    )\n    response.raise_for_status()\n    campaign_id = response.json().get(\"campaignId\")\n\n    # Launch campaign\n    launch_response = requests.post(\n        f\"{SAVIYNT_URL}\u002FECM\u002Fapi\u002Fv5\u002FlaunchCampaign\",\n        headers=headers,\n        json={\"campaignId\": campaign_id}\n    )\n    launch_response.raise_for_status()\n\n    return {\n        \"campaign_id\": campaign_id,\n        \"status\": \"launched\",\n        \"certifications_created\": launch_response.json().get(\"certificationCount\", 0)\n    }\n\ndef get_campaign_status(campaign_id):\n    \"\"\"Get current status and progress of a campaign.\"\"\"\n    headers = {\"Authorization\": f\"Bearer {SAVIYNT_TOKEN}\"}\n    response = requests.get(\n        f\"{SAVIYNT_URL}\u002FECM\u002Fapi\u002Fv5\u002FgetCampaignDetails\",\n        headers=headers,\n        params={\"campaignId\": campaign_id}\n    )\n    response.raise_for_status()\n    data = response.json()\n\n    return {\n        \"campaign_id\": campaign_id,\n        \"status\": data.get(\"status\"),\n        \"total_items\": data.get(\"totalLineItems\", 0),\n        \"certified\": data.get(\"certifiedCount\", 0),\n        \"revoked\": data.get(\"revokedCount\", 0),\n        \"pending\": data.get(\"pendingCount\", 0),\n        \"completion_rate\": data.get(\"completionPercentage\", 0),\n    }\n```\n\n### Step 4: Monitor Campaign Progress\n\nTrack certification progress and send escalations:\n\n- **Dashboard**: Saviynt provides real-time campaign dashboard with completion rates\n- **Reminders**: Automatic email reminders at configured intervals\n- **Escalation**: If certifier does not respond by due date, escalate to manager's manager or auto-revoke\n- **Delegation**: Allow certifiers to delegate specific items to application owners\n\n### Step 5: Execute Remediation\n\nAfter campaign closes:\n\n1. **Auto-Remediation**: Saviynt automatically creates provisioning tasks to revoke denied access\n2. **Ticket Integration**: Revocation tasks create tickets in ServiceNow\u002FJira for tracking\n3. **Grace Period**: Configure a grace period (e.g., 5 business days) before access is actually removed\n4. **Verification**: After revocation, verify access is removed from target systems\n5. **Audit Trail**: All decisions, revocations, and remediations logged for compliance evidence\n\n## Validation Checklist\n\n- [ ] Campaign templates configured for each certification type\n- [ ] Certifier roles assigned (managers, app owners, data owners)\n- [ ] Risk scoring and usage analytics enabled\n- [ ] SoD violation detection configured\n- [ ] Reminder and escalation schedules defined\n- [ ] Auto-revoke policy for non-responsive certifiers configured\n- [ ] Campaign launched and certifiers notified\n- [ ] Campaign completion rate > 95% before close\n- [ ] Revocation tasks created for all denied entitlements\n- [ ] Remediation completed within SLA\n- [ ] Campaign report generated for compliance audit\n- [ ] Evidence archived for regulatory retention period\n\n## References\n\n- [Saviynt Campaigns and Certifications Documentation](https:\u002F\u002Fdocs.saviyntcloud.com\u002Fbundle\u002FEIC-Admin-25\u002Fpage\u002FContent\u002FChapter15-Campaigns-and-Certifications\u002FCampaigns.htm)\n- [Saviynt Simplifying Certifications with Intelligence](https:\u002F\u002Fsaviynt.com\u002Fblog\u002Fsimplifying-certifications-with-intelligence)\n- [Saviynt Advanced Access Reviews](https:\u002F\u002Foxfordcomputergroup.com\u002Fresources\u002Fsaviynt-advanced-access-reviews\u002F)\n- [ISACA Access Recertification Best Practices](https:\u002F\u002Fwww.isaca.org\u002F)\n","# Performing Access Recertification with Saviynt\n\n## Overview\n\nAccess recertification (also called access certification or access review) is a periodic process where designated reviewers validate that users have appropriate access to systems and data. Saviynt Enterprise Identity Cloud (EIC) automates this process through certification campaigns that present reviewers with current access assignments and collect approve\u002Frevoke\u002Fconditionally-certify decisions. Campaigns can be triggered on schedule (quarterly, semi-annually), event-driven (department transfer, role change), or on-demand. Saviynt provides intelligence features including risk scoring, usage analytics, and peer-group analysis to help reviewers make informed decisions.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing access recertification with saviynt\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- Saviynt Enterprise Identity Cloud (EIC) tenant with admin access\n- Identity data synchronized from authoritative sources (HR, AD, cloud)\n- Entitlement data imported from target applications\n- Certifier roles assigned (managers, application owners, data owners)\n- Campaign templates defined for each certification type\n\n## Core Concepts\n\n### Campaign Types\n\n| Type | Scope | Trigger | Certifier |\n|------|-------|---------|-----------|\n| User Manager | All access for users under a manager | Scheduled (quarterly) | Direct manager |\n| Entitlement Owner | All users with a specific entitlement | Scheduled (semi-annually) | Entitlement\u002Fapp owner |\n| Application | All access to a specific application | Scheduled | Application owner |\n| Role-Based | All users assigned to a specific role | Scheduled | Role owner |\n| Event-Based | Users whose attributes changed | Attribute change trigger | New manager |\n| Micro-Certification | Single user, single entitlement | On-demand | Manager or owner |\n\n### Certification Decisions\n\n| Decision | Effect | Use Case |\n|----------|--------|----------|\n| Certify (Approve) | Access maintained | Access is still required |\n| Revoke | Access removal ticket created | Access no longer needed |\n| Conditionally Certify | Access maintained with conditions | Access needed temporarily, review again |\n| Delegate | Reassign to another certifier | Certifier lacks knowledge to decide |\n| Abstain | No decision recorded | Conflict of interest |\n\n### Campaign Lifecycle\n\n```\nCONFIGURATION → PREVIEW → ACTIVE → IN PROGRESS → COMPLETED → REMEDIATION\n       │            │         │          │             │            │\n       │            │         │          │             │            └── Revoke tickets\n       │            │         │          │             │                executed\n       │            │         │          │             │\n       │            │         │          │             └── All decisions\n       │            │         │          │                 collected\n       │            │         │          │\n       │            │         │          └── Certifiers reviewing\n       │            │         │              and making decisions\n       │            │         │\n       │            │         └── Campaign launched,\n       │            │             notifications sent\n       │            │\n       │            └── Read-only preview for validation\n       │\n       └── Campaign parameters defined\n```\n\n## Workflow\n\n### Step 1: Configure Campaign Template\n\nIn Saviynt Admin Console:\n\n1. Navigate to **Certifications > Campaign > Create New Campaign**\n2. Define campaign parameters:\n\n| Parameter | Value |\n|-----------|-------|\n| Campaign Name | Q1 2025 Manager Access Review |\n| Campaign Type | User Manager |\n| Description | Quarterly review of all user access |\n| Certifier Type | Manager (dynamic - user's direct manager) |\n| Secondary Certifier | Application Owner (fallback if manager unavailable) |\n| Due Date | 14 days from launch |\n| Reminder Schedule | Day 7, Day 10, Day 13 |\n| Escalation | Auto-revoke on Day 15 if no decision |\n\n3. Configure scope filters:\n   - Include: All active users\n   - Exclude: Service accounts, break-glass accounts\n   - Application filter: All connected applications\n\n4. Configure intelligence features:\n   - Enable risk scoring (high-risk entitlements highlighted)\n   - Enable usage data (last access date shown)\n   - Enable peer analysis (compare access to peer group)\n   - Enable SoD violation flagging\n\n### Step 2: Configure Certifier Experience\n\nCustomize what certifiers see during the review:\n\n**Columns Displayed:**\n- User name and title\n- Application name\n- Entitlement\u002Frole name\n- Risk score (1-10)\n- Last access date\n- Peer group comparison (% of peers with same access)\n- SoD violation flag\n\n**Decision Options:**\n- Certify with justification (free text)\n- Revoke with reason (dropdown: no longer needed, SoD conflict, role change)\n- Conditionally certify with expiry date\n\n**Bulk Actions:**\n- Certify all low-risk items\n- Revoke all items not accessed in 90+ days\n- Filter by application, risk level, or SoD status\n\n### Step 3: Launch Campaign via API\n\n```python\nimport requests\n\nSAVIYNT_URL = \"https:\u002F\u002Ftenant.saviyntcloud.com\"\nSAVIYNT_TOKEN = \"your-api-token\"\n\ndef create_certification_campaign(campaign_config):\n    \"\"\"Create and launch a Saviynt certification campaign.\"\"\"\n    headers = {\n        \"Authorization\": f\"Bearer {SAVIYNT_TOKEN}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n\n    # Create campaign\n    response = requests.post(\n        f\"{SAVIYNT_URL}\u002FECM\u002Fapi\u002Fv5\u002FcreateCampaign\",\n        headers=headers,\n        json={\n            \"campaignname\": campaign_config[\"name\"],\n            \"campaigntype\": campaign_config[\"type\"],\n            \"description\": campaign_config[\"description\"],\n            \"certifier\": campaign_config[\"certifier_type\"],\n            \"duedate\": campaign_config[\"due_date\"],\n            \"reminderdays\": campaign_config[\"reminder_days\"],\n            \"autorevoke\": campaign_config.get(\"auto_revoke\", True),\n            \"autorevokedays\": campaign_config.get(\"auto_revoke_days\", 15),\n            \"scope\": campaign_config.get(\"scope\", {}),\n        }\n    )\n    response.raise_for_status()\n    campaign_id = response.json().get(\"campaignId\")\n\n    # Launch campaign\n    launch_response = requests.post(\n        f\"{SAVIYNT_URL}\u002FECM\u002Fapi\u002Fv5\u002FlaunchCampaign\",\n        headers=headers,\n        json={\"campaignId\": campaign_id}\n    )\n    launch_response.raise_for_status()\n\n    return {\n        \"campaign_id\": campaign_id,\n        \"status\": \"launched\",\n        \"certifications_created\": launch_response.json().get(\"certificationCount\", 0)\n    }\n\ndef get_campaign_status(campaign_id):\n    \"\"\"Get current status and progress of a campaign.\"\"\"\n    headers = {\"Authorization\": f\"Bearer {SAVIYNT_TOKEN}\"}\n    response = requests.get(\n        f\"{SAVIYNT_URL}\u002FECM\u002Fapi\u002Fv5\u002FgetCampaignDetails\",\n        headers=headers,\n        params={\"campaignId\": campaign_id}\n    )\n    response.raise_for_status()\n    data = response.json()\n\n    return {\n        \"campaign_id\": campaign_id,\n        \"status\": data.get(\"status\"),\n        \"total_items\": data.get(\"totalLineItems\", 0),\n        \"certified\": data.get(\"certifiedCount\", 0),\n        \"revoked\": data.get(\"revokedCount\", 0),\n        \"pending\": data.get(\"pendingCount\", 0),\n        \"completion_rate\": data.get(\"completionPercentage\", 0),\n    }\n```\n\n### Step 4: Monitor Campaign Progress\n\nTrack certification progress and send escalations:\n\n- **Dashboard**: Saviynt provides real-time campaign dashboard with completion rates\n- **Reminders**: Automatic email reminders at configured intervals\n- **Escalation**: If certifier does not respond by due date, escalate to manager's manager or auto-revoke\n- **Delegation**: Allow certifiers to delegate specific items to application owners\n\n### Step 5: Execute Remediation\n\nAfter campaign closes:\n\n1. **Auto-Remediation**: Saviynt automatically creates provisioning tasks to revoke denied access\n2. **Ticket Integration**: Revocation tasks create tickets in ServiceNow\u002FJira for tracking\n3. **Grace Period**: Configure a grace period (e.g., 5 business days) before access is actually removed\n4. **Verification**: After revocation, verify access is removed from target systems\n5. **Audit Trail**: All decisions, revocations, and remediations logged for compliance evidence\n\n## Validation Checklist\n\n- [ ] Campaign templates configured for each certification type\n- [ ] Certifier roles assigned (managers, app owners, data owners)\n- [ ] Risk scoring and usage analytics enabled\n- [ ] SoD violation detection configured\n- [ ] Reminder and escalation schedules defined\n- [ ] Auto-revoke policy for non-responsive certifiers configured\n- [ ] Campaign launched and certifiers notified\n- [ ] Campaign completion rate > 95% before close\n- [ ] Revocation tasks created for all denied entitlements\n- [ ] Remediation completed within SLA\n- [ ] Campaign report generated for compliance audit\n- [ ] Evidence archived for regulatory retention period\n\n## References\n\n- [Saviynt Campaigns and Certifications Documentation](https:\u002F\u002Fdocs.saviyntcloud.com\u002Fbundle\u002FEIC-Admin-25\u002Fpage\u002FContent\u002FChapter15-Campaigns-and-Certifications\u002FCampaigns.htm)\n- [Saviynt Simplifying Certifications with Intelligence](https:\u002F\u002Fsaviynt.com\u002Fblog\u002Fsimplifying-certifications-with-intelligence)\n- [Saviynt Advanced Access Reviews](https:\u002F\u002Foxfordcomputergroup.com\u002Fresources\u002Fsaviynt-advanced-access-reviews\u002F)\n- [ISACA Access Recertification Best Practices](https:\u002F\u002Fwww.isaca.org\u002F)\n",{"name":5,"tags":54,"author":56,"domain":48,"license":15,"version":57,"mitre_f3":58,"nist_csf":82,"subdomain":87,"description":7,"mitre_attack":88},[33,32,30,43,31,55],"iga","mahipal","1.0",{"tactics":59,"version":63,"techniques":64},[35,60,61,62],"positioning","defense-impairment","resource-development","1.1",[65,69,73,76,79],{"id":66,"name":67,"source":68,"tactic":62},"T1586","Compromise Accounts","attack",{"id":70,"name":71,"source":72,"tactic":35},"F1033","Insider Access Abuse","f3",{"id":74,"name":75,"source":72,"tactic":60},"F1005","Account Manipulation",{"id":77,"name":78,"source":72,"tactic":60},"F1005.002","Account Manipulation: Add Authorized User",{"id":80,"name":81,"source":72,"tactic":61},"F1005.007","Account Manipulation: Enable Account Features",[83,84,85,86],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[89,90,91,92,93],"T1078","T1110","T1556","T1098","T1071","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fperforming-access-recertification-with-saviynt",4379,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":105,"prompt":115,"zipAvailable":116},[106,109,112],{"tool":107,"command":108},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-access-recertification-with-saviynt",{"tool":110,"command":111},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-access-recertification-with-saviynt",{"tool":113,"command":114},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-access-recertification-with-saviynt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002FSKILL.md",true,[118,124,129,135,139,143,147,151,157],{"path":119,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":122,"sourceHtmlUrl":123},"assets\u002Ftemplate.md","ASSET","资产文件",1338,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002Fassets\u002Ftemplate.md",{"path":125,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002FLICENSE",{"path":130,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":133,"sourceHtmlUrl":134},"reference\u002Fchecklist-template.md","REFERENCE","参考文档",5151,"https:\u002F\u002Fgithub.com\u002Finernoro\u002Fprd_agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Facceptance-checklist\u002Freference\u002Fchecklist-template.md",{"path":136,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":137,"sourceHtmlUrl":138},"reference\u002Fexample-cds-cluster.md",9487,"https:\u002F\u002Fgithub.com\u002Finernoro\u002Fprd_agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Facceptance-checklist\u002Freference\u002Fexample-cds-cluster.md",{"path":140,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fapi-reference.md",1724,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002Freferences\u002Fapi-reference.md",{"path":144,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fstandards.md",1952,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002Freferences\u002Fstandards.md",{"path":148,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":149,"sourceHtmlUrl":150},"references\u002Fworkflows.md",4034,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002Freferences\u002Fworkflows.md",{"path":152,"resourceType":153,"resourceTypeDesc":154,"sizeBytes":155,"sourceHtmlUrl":156},"scripts\u002Fagent.py","SCRIPT","脚本",6879,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002Fscripts\u002Fagent.py",{"path":158,"resourceType":153,"resourceTypeDesc":154,"sizeBytes":159,"sourceHtmlUrl":160},"scripts\u002Fprocess.py",8668,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-access-recertification-with-saviynt\u002Fscripts\u002Fprocess.py",[162,187,211,237,263,290],{"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":49},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[170,171,172,173,174,48,175,47,46,176,177,178,179,180,181,182,183,184,185,186],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":49},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[193],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[195,183,196,197,174,198,48,46,199,200,201,202,203,204,205,206,207,208,209,210],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":221,"publishedAt":49},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[217,220],{"categoryNo":218,"categoryName":219,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[205,222,223,224,225,48,226,227,199,43,228,229,230,231,232,36,233,234,235,236],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":49},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[243],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,48,248,249,250,251,252,253,254,255,256,257,258,259,202,260,261,262],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":264,"name":265,"nameZh":6,"description":266,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":267,"categories":268,"keywords":270,"publishedAt":49},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[269],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[271,272,273,48,274,275,276,277,278,279,280,281,282,283,284,285,286,287,288,289],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":291,"name":292,"nameZh":6,"description":293,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":294,"categories":295,"keywords":297,"publishedAt":49},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[296],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,298,48,299,300,301,42,302,303,304,305,36,306,233,307,308,309,310,311,312],"triaging security incident","siem","file","ioc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]