[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HMF8B3E2JPKWSMA5YWCCG1":3,"skill-same:01M6HMF8B3E2JPKWSMA5YWCCG1":117},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6HMF8B3E2JPKWSMA5YWCCG1","implementing-zero-standing-privilege-with-cyberark",null,"Deploy CyberArk Secure Cloud Access to eliminate standing privileges in hybrid and multi-cloud environments using just-in-time access with time, entitlement, and approval controls.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"implementing","with","ZeRO","implementing zero standing privilege with cyberark","cyberark","PAM","environments","time","access","jit-access","zero-standing-privilege","security","just-in-time","t1098","t1078","least-privilege","cloud-security","secure","identity","cybersecurity","2026-11-10 10:12:30",false,"---\nname: implementing-zero-standing-privilege-with-cyberark\ndescription: Deploy CyberArk Secure Cloud Access to eliminate standing privileges in hybrid and multi-cloud environments using just-in-time access with time, entitlement, and approval controls.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- cyberark\n- zero-standing-privilege\n- jit-access\n- pam\n- cloud-security\n- least-privilege\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- T1078.004\ncategory: implementing-zero-standing-privilege-with-cyberark\n---\n# Implementing Zero Standing Privilege with CyberArk\n\n## Overview\n\nZero Standing Privileges (ZSP) is a security model where no user or identity retains persistent privileged access. Instead, elevated access is provisioned dynamically on a just-in-time (JIT) basis and automatically revoked after use. CyberArk implements ZSP through its Secure Cloud Access (SCA) module, which creates ephemeral, scoped roles in cloud environments (AWS, Azure, GCP) that exist only for the duration of a session. The TEA framework -- Time, Entitlements, and Approvals -- governs every privileged access session.\n\n\n## When to Use\n\n- When deploying or configuring implementing zero standing privilege with cyberark capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- CyberArk Identity Security Platform (Privilege Cloud or self-hosted)\n- CyberArk Secure Cloud Access (SCA) license\n- Cloud provider accounts (AWS, Azure, GCP) with admin access for integration\n- ITSM integration (ServiceNow, Jira) for approval workflows\n- CyberArk Vault configured with safe management\n\n## Core Concepts\n\n### TEA Framework (Time, Entitlements, Approvals)\n\n| Component | Description | Configuration |\n|-----------|-------------|---------------|\n| **Time** | Duration of the privileged session | Min 15 minutes, max 8 hours, default 1 hour |\n| **Entitlements** | Permissions granted during the session | Dynamically scoped IAM roles\u002Fpolicies |\n| **Approvals** | Authorization workflow before access | Auto-approve, manager approval, or multi-level |\n\n### ZSP Architecture\n\n```\nUser requests access via CyberArk\n        │\n        ├── CyberArk evaluates request against policies:\n        │   ├── Is user eligible for this access?\n        │   ├── Does the request comply with TEA policies?\n        │   └── Is approval required?\n        │\n        ├── [If approval needed] → Route to approver (ITSM\u002FChatOps)\n        │\n        ├── Upon approval:\n        │   ├── CyberArk creates ephemeral IAM role in target cloud\n        │   ├── Scopes permissions to minimum required entitlements\n        │   ├── Sets session TTL (time-bound)\n        │   └── Provisions temporary credentials\n        │\n        ├── User accesses cloud resources via session\n        │   ├── All actions logged and recorded\n        │   └── Session monitored for policy violations\n        │\n        └── Session expires:\n            ├── Ephemeral role deleted\n            ├── Temporary credentials revoked\n            └── Zero standing privileges remain\n```\n\n### CyberArk Components\n\n| Component | Role |\n|-----------|------|\n| Identity Security Platform | Central management and policy engine |\n| Privilege Cloud Vault | Stores privileged credentials and keys |\n| Secure Cloud Access | Creates\u002Fdestroys ephemeral cloud roles |\n| Endpoint Privilege Manager | Controls local admin and app elevation |\n| Privileged Session Manager | Records and monitors privileged sessions |\n\n## Workflow\n\n### Step 1: Integrate Cloud Providers\n\n**AWS Integration:**\n1. Create a CyberArk integration role in AWS IAM\n2. Configure cross-account trust policy allowing CyberArk to assume roles\n3. Create IAM policies that define maximum allowed entitlements\n4. Register AWS accounts in CyberArk SCA\n\n```json\n{\n    \"Version\": \"2012-10-17\",\n    \"Statement\": [{\n        \"Effect\": \"Allow\",\n        \"Principal\": {\n            \"AWS\": \"arn:aws:iam::CYBERARK_ACCOUNT:role\u002FCyberArkSCARole\"\n        },\n        \"Action\": \"sts:AssumeRole\",\n        \"Condition\": {\n            \"StringEquals\": {\n                \"sts:ExternalId\": \"cyberark-external-id\"\n            }\n        }\n    }]\n}\n```\n\n**Azure Integration:**\n1. Register CyberArk as an enterprise application in Microsoft Entra ID\n2. Grant CyberArk application permissions: Directory.ReadWrite.All, RoleManagement.ReadWrite.Directory\n3. Create custom Azure roles with scoped permissions\n4. Register Azure subscriptions in CyberArk SCA\n\n**GCP Integration:**\n1. Create a service account for CyberArk in GCP\n2. Grant IAM Admin and Service Account Admin roles\n3. Configure workload identity federation for cross-cloud access\n4. Register GCP projects in CyberArk SCA\n\n### Step 2: Define Access Policies\n\nCreate policies that map job functions to cloud entitlements:\n\n```yaml\n# CyberArk SCA Policy Example\npolicy_name: \"developer-aws-read-access\"\ndescription: \"Read-only access to AWS production for developers\"\ntarget_cloud: \"aws\"\ntarget_accounts: [\"123456789012\", \"987654321098\"]\n\ntime_policy:\n  max_duration: \"4h\"\n  default_duration: \"1h\"\n  business_hours_only: true\n  timezone: \"America\u002FNew_York\"\n\nentitlement_policy:\n  aws_managed_policies:\n    - \"arn:aws:iam::aws:policy\u002FReadOnlyAccess\"\n  deny_actions:\n    - \"iam:*\"\n    - \"organizations:*\"\n    - \"sts:*\"\n  resource_restrictions:\n    - \"arn:aws:s3:::production-*\"\n\napproval_policy:\n  approval_required: true\n  approvers:\n    - type: \"manager\"\n    - type: \"group\"\n      group: \"cloud-security-team\"\n  auto_approve_conditions:\n    - previous_approved_same_policy: true\n      within_days: 7\n  escalation_timeout: \"2h\"\n  escalation_approver: \"cloud-security-lead\"\n```\n\n### Step 3: Configure Session Monitoring\n\nSet up privileged session recording and real-time monitoring:\n\n1. Enable session recording for all ZSP sessions\n2. Configure keystroke logging for SSH\u002FRDP sessions\n3. Set up real-time alerts for suspicious activities:\n   - Attempts to escalate privileges during session\n   - Access to resources outside policy scope\n   - Session duration exceeding 2x the normal pattern\n4. Forward session metadata to SIEM\n\n### Step 4: Implement Approval Workflows\n\nIntegrate with ITSM tools for access request and approval:\n\n- **ServiceNow**: CyberArk SCA connector creates ServiceNow tickets for approval\n- **Slack\u002FTeams**: ChatOps bot for quick approvals within messaging platforms\n- **Jira**: Integration for development-related access requests\n- **Auto-Approval**: Configure rules for low-risk, previously approved requests\n\n### Step 5: Migrate from Standing Privileges\n\n```\nPhase 1: DISCOVERY (Weeks 1-2)\n    ├── Inventory all standing privileged roles across cloud accounts\n    ├── Map users to their standing role assignments\n    ├── Analyze CloudTrail\u002Factivity logs for actual permission usage\n    └── Identify roles that can be converted to JIT\n\nPhase 2: POLICY CREATION (Weeks 3-4)\n    ├── Create ZSP policies based on actual usage analysis\n    ├── Define TEA parameters for each policy\n    ├── Configure approval workflows\n    └── Test policies with pilot users\n\nPhase 3: MIGRATION (Weeks 5-8)\n    ├── Assign ZSP policies to pilot group\n    ├── Remove standing privileges from pilot users\n    ├── Monitor for access issues and adjust policies\n    ├── Expand to additional teams incrementally\n    └── Remove all standing privileges organization-wide\n\nPhase 4: GOVERNANCE (Ongoing)\n    ├── Monthly review of ZSP policy effectiveness\n    ├── Quarterly entitlement optimization\n    ├── Monitor for policy drift or standing privilege re-creation\n    └── Report ZSP metrics to security leadership\n```\n\n## Validation Checklist\n\n- [ ] Cloud providers integrated with CyberArk SCA\n- [ ] TEA policies defined for all privileged access scenarios\n- [ ] Approval workflows configured and tested\n- [ ] Session recording and monitoring enabled\n- [ ] All standing privileged roles identified for migration\n- [ ] Pilot group successfully using ZSP without standing privileges\n- [ ] Break-glass procedure defined for emergency access\n- [ ] SIEM integration receiving session and access logs\n- [ ] Auto-approval rules configured for low-risk, repeat access\n- [ ] Organization-wide migration plan approved and scheduled\n- [ ] KPI tracking: reduction in standing privilege assignments\n\n## References\n\n- [CyberArk Zero Standing Privileges](https:\u002F\u002Fwww.cyberark.com\u002Fwhat-is\u002Fzero-standing-privileges\u002F)\n- [CyberArk ZSP Implementation with AWS](https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fapn\u002Fhow-to-implement-zero-standing-privileges-with-cyberark-for-securing-access-to-the-aws-console\u002F)\n- [CyberArk Blueprint - Zero Standing Privilege](https:\u002F\u002Fdocs.cyberark.com\u002Fcyberark-blueprint\u002Flatest\u002Fen\u002Fcontent\u002Fzero-standing-privilege.htm)\n- [CyberArk Secure Cloud Access Documentation](https:\u002F\u002Fdocs.cyberark.com\u002Fispss-access\u002Flatest\u002Fen\u002Fcontent\u002Fgetstarted\u002Facc-frst-page.htm)\n","# Implementing Zero Standing Privilege with CyberArk\n\n## Overview\n\nZero Standing Privileges (ZSP) is a security model where no user or identity retains persistent privileged access. Instead, elevated access is provisioned dynamically on a just-in-time (JIT) basis and automatically revoked after use. CyberArk implements ZSP through its Secure Cloud Access (SCA) module, which creates ephemeral, scoped roles in cloud environments (AWS, Azure, GCP) that exist only for the duration of a session. The TEA framework -- Time, Entitlements, and Approvals -- governs every privileged access session.\n\n\n## When to Use\n\n- When deploying or configuring implementing zero standing privilege with cyberark capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- CyberArk Identity Security Platform (Privilege Cloud or self-hosted)\n- CyberArk Secure Cloud Access (SCA) license\n- Cloud provider accounts (AWS, Azure, GCP) with admin access for integration\n- ITSM integration (ServiceNow, Jira) for approval workflows\n- CyberArk Vault configured with safe management\n\n## Core Concepts\n\n### TEA Framework (Time, Entitlements, Approvals)\n\n| Component | Description | Configuration |\n|-----------|-------------|---------------|\n| **Time** | Duration of the privileged session | Min 15 minutes, max 8 hours, default 1 hour |\n| **Entitlements** | Permissions granted during the session | Dynamically scoped IAM roles\u002Fpolicies |\n| **Approvals** | Authorization workflow before access | Auto-approve, manager approval, or multi-level |\n\n### ZSP Architecture\n\n```\nUser requests access via CyberArk\n        │\n        ├── CyberArk evaluates request against policies:\n        │   ├── Is user eligible for this access?\n        │   ├── Does the request comply with TEA policies?\n        │   └── Is approval required?\n        │\n        ├── [If approval needed] → Route to approver (ITSM\u002FChatOps)\n        │\n        ├── Upon approval:\n        │   ├── CyberArk creates ephemeral IAM role in target cloud\n        │   ├── Scopes permissions to minimum required entitlements\n        │   ├── Sets session TTL (time-bound)\n        │   └── Provisions temporary credentials\n        │\n        ├── User accesses cloud resources via session\n        │   ├── All actions logged and recorded\n        │   └── Session monitored for policy violations\n        │\n        └── Session expires:\n            ├── Ephemeral role deleted\n            ├── Temporary credentials revoked\n            └── Zero standing privileges remain\n```\n\n### CyberArk Components\n\n| Component | Role |\n|-----------|------|\n| Identity Security Platform | Central management and policy engine |\n| Privilege Cloud Vault | Stores privileged credentials and keys |\n| Secure Cloud Access | Creates\u002Fdestroys ephemeral cloud roles |\n| Endpoint Privilege Manager | Controls local admin and app elevation |\n| Privileged Session Manager | Records and monitors privileged sessions |\n\n## Workflow\n\n### Step 1: Integrate Cloud Providers\n\n**AWS Integration:**\n1. Create a CyberArk integration role in AWS IAM\n2. Configure cross-account trust policy allowing CyberArk to assume roles\n3. Create IAM policies that define maximum allowed entitlements\n4. Register AWS accounts in CyberArk SCA\n\n```json\n{\n    \"Version\": \"2012-10-17\",\n    \"Statement\": [{\n        \"Effect\": \"Allow\",\n        \"Principal\": {\n            \"AWS\": \"arn:aws:iam::CYBERARK_ACCOUNT:role\u002FCyberArkSCARole\"\n        },\n        \"Action\": \"sts:AssumeRole\",\n        \"Condition\": {\n            \"StringEquals\": {\n                \"sts:ExternalId\": \"cyberark-external-id\"\n            }\n        }\n    }]\n}\n```\n\n**Azure Integration:**\n1. Register CyberArk as an enterprise application in Microsoft Entra ID\n2. Grant CyberArk application permissions: Directory.ReadWrite.All, RoleManagement.ReadWrite.Directory\n3. Create custom Azure roles with scoped permissions\n4. Register Azure subscriptions in CyberArk SCA\n\n**GCP Integration:**\n1. Create a service account for CyberArk in GCP\n2. Grant IAM Admin and Service Account Admin roles\n3. Configure workload identity federation for cross-cloud access\n4. Register GCP projects in CyberArk SCA\n\n### Step 2: Define Access Policies\n\nCreate policies that map job functions to cloud entitlements:\n\n```yaml\n# CyberArk SCA Policy Example\npolicy_name: \"developer-aws-read-access\"\ndescription: \"Read-only access to AWS production for developers\"\ntarget_cloud: \"aws\"\ntarget_accounts: [\"123456789012\", \"987654321098\"]\n\ntime_policy:\n  max_duration: \"4h\"\n  default_duration: \"1h\"\n  business_hours_only: true\n  timezone: \"America\u002FNew_York\"\n\nentitlement_policy:\n  aws_managed_policies:\n    - \"arn:aws:iam::aws:policy\u002FReadOnlyAccess\"\n  deny_actions:\n    - \"iam:*\"\n    - \"organizations:*\"\n    - \"sts:*\"\n  resource_restrictions:\n    - \"arn:aws:s3:::production-*\"\n\napproval_policy:\n  approval_required: true\n  approvers:\n    - type: \"manager\"\n    - type: \"group\"\n      group: \"cloud-security-team\"\n  auto_approve_conditions:\n    - previous_approved_same_policy: true\n      within_days: 7\n  escalation_timeout: \"2h\"\n  escalation_approver: \"cloud-security-lead\"\n```\n\n### Step 3: Configure Session Monitoring\n\nSet up privileged session recording and real-time monitoring:\n\n1. Enable session recording for all ZSP sessions\n2. Configure keystroke logging for SSH\u002FRDP sessions\n3. Set up real-time alerts for suspicious activities:\n   - Attempts to escalate privileges during session\n   - Access to resources outside policy scope\n   - Session duration exceeding 2x the normal pattern\n4. Forward session metadata to SIEM\n\n### Step 4: Implement Approval Workflows\n\nIntegrate with ITSM tools for access request and approval:\n\n- **ServiceNow**: CyberArk SCA connector creates ServiceNow tickets for approval\n- **Slack\u002FTeams**: ChatOps bot for quick approvals within messaging platforms\n- **Jira**: Integration for development-related access requests\n- **Auto-Approval**: Configure rules for low-risk, previously approved requests\n\n### Step 5: Migrate from Standing Privileges\n\n```\nPhase 1: DISCOVERY (Weeks 1-2)\n    ├── Inventory all standing privileged roles across cloud accounts\n    ├── Map users to their standing role assignments\n    ├── Analyze CloudTrail\u002Factivity logs for actual permission usage\n    └── Identify roles that can be converted to JIT\n\nPhase 2: POLICY CREATION (Weeks 3-4)\n    ├── Create ZSP policies based on actual usage analysis\n    ├── Define TEA parameters for each policy\n    ├── Configure approval workflows\n    └── Test policies with pilot users\n\nPhase 3: MIGRATION (Weeks 5-8)\n    ├── Assign ZSP policies to pilot group\n    ├── Remove standing privileges from pilot users\n    ├── Monitor for access issues and adjust policies\n    ├── Expand to additional teams incrementally\n    └── Remove all standing privileges organization-wide\n\nPhase 4: GOVERNANCE (Ongoing)\n    ├── Monthly review of ZSP policy effectiveness\n    ├── Quarterly entitlement optimization\n    ├── Monitor for policy drift or standing privilege re-creation\n    └── Report ZSP metrics to security leadership\n```\n\n## Validation Checklist\n\n- [ ] Cloud providers integrated with CyberArk SCA\n- [ ] TEA policies defined for all privileged access scenarios\n- [ ] Approval workflows configured and tested\n- [ ] Session recording and monitoring enabled\n- [ ] All standing privileged roles identified for migration\n- [ ] Pilot group successfully using ZSP without standing privileges\n- [ ] Break-glass procedure defined for emergency access\n- [ ] SIEM integration receiving session and access logs\n- [ ] Auto-approval rules configured for low-risk, repeat access\n- [ ] Organization-wide migration plan approved and scheduled\n- [ ] KPI tracking: reduction in standing privilege assignments\n\n## References\n\n- [CyberArk Zero Standing Privileges](https:\u002F\u002Fwww.cyberark.com\u002Fwhat-is\u002Fzero-standing-privileges\u002F)\n- [CyberArk ZSP Implementation with AWS](https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fapn\u002Fhow-to-implement-zero-standing-privileges-with-cyberark-for-securing-access-to-the-aws-console\u002F)\n- [CyberArk Blueprint - Zero Standing Privilege](https:\u002F\u002Fdocs.cyberark.com\u002Fcyberark-blueprint\u002Flatest\u002Fen\u002Fcontent\u002Fzero-standing-privilege.htm)\n- [CyberArk Secure Cloud Access Documentation](https:\u002F\u002Fdocs.cyberark.com\u002Fispss-access\u002Flatest\u002Fen\u002Fcontent\u002Fgetstarted\u002Facc-frst-page.htm)\n",{"name":5,"tags":44,"author":46,"domain":38,"license":15,"version":47,"category":5,"nist_csf":48,"subdomain":53,"description":7,"mitre_attack":54},[23,29,28,45,35,34],"pam","mahipal","1.0",[49,50,51,52],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[55,56,57,58,59],"T1078","T1110","T1556","T1098","T1078.004","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fimplementing-zero-standing-privilege-with-cyberark",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill implementing-zero-standing-privilege-with-cyberark",{"tool":74,"command":75},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill implementing-zero-standing-privilege-with-cyberark",{"tool":77,"command":78},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill implementing-zero-standing-privilege-with-cyberark","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002FSKILL.md",true,[82,88,93,99,103,107,113],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Ftemplate.md","ASSET","资产文件",1254,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002Fassets\u002Ftemplate.md",{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002FLICENSE",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fapi-reference.md","REFERENCE","参考文档",1705,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002Freferences\u002Fapi-reference.md",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fstandards.md",1675,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002Freferences\u002Fstandards.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fworkflows.md",3705,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002Freferences\u002Fworkflows.md",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fagent.py","SCRIPT","脚本",7235,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002Fscripts\u002Fagent.py",{"path":114,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fprocess.py",7038,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-zero-standing-privilege-with-cyberark\u002Fscripts\u002Fprocess.py",[118,148,173,195,211,232],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[130,131,132,133,134,135,38,136,137,138,139,140,141,33,142,143,144,145,146,147],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[155,156,157,158,20,38,159,160,161,162,163,164,165,166,167,168,169,170,171,172],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"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":179,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[30,180,145,38,181,182,183,33,142,184,185,186,187,188,189,190,191,192,193,194],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[30,202,203,180,145,20,38,204,182,139,205,206,33,142,207,185,168,208,209,210],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"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":217,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[30,218,219,220,221,222,38,223,224,225,182,226,33,227,228,229,188,230,145,231],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","cm","de",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[239,240,241,242,38,243,244,245,246,247,248,227,249,250,230,251,231,252,253,254],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]