Cloud Misconfig Auditor
criptogus/agent-evolve-network
Audits AWS, GCP and Azure environments (and matching IaC) for excessive permissions, public exposure, weak encryption defaults and missing logging.
Agent skill
Implementing Zero Standing Privilege With Cyberark
Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time…
Install Implementing Zero Standing Privilege With Cyberark
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-standing-privilege-with-cyberark --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-zero-standing-privilege-with-cyberark .claude/skills/implementing-zero-standing-privilege-with-cyberark && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "implementing-zero-standing-privilege-with-cyberark" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark into .claude/skills/implementing-zero-standing-privilege-with-cyberark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-zero-standing-privilege-with-cyberark", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberarkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-standing-privilege-with-cyberark --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/implementing-zero-standing-privilege-with-cyberark .agents/skills/implementing-zero-standing-privilege-with-cyberark && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implementing-zero-standing-privilege-with-cyberark" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark into .agents/skills/implementing-zero-standing-privilege-with-cyberark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-zero-standing-privilege-with-cyberark", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-standing-privilege-with-cyberark --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/implementing-zero-standing-privilege-with-cyberark .cursor/skills/implementing-zero-standing-privilege-with-cyberark && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "implementing-zero-standing-privilege-with-cyberark" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark into .cursor/skills/implementing-zero-standing-privilege-with-cyberark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-zero-standing-privilege-with-cyberark", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git --path skills/implementing-zero-standing-privilege-with-cyberark--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-standing-privilege-with-cyberark --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/implementing-zero-standing-privilege-with-cyberark .gemini/skills/implementing-zero-standing-privilege-with-cyberark && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "implementing-zero-standing-privilege-with-cyberark" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark into .gemini/skills/implementing-zero-standing-privilege-with-cyberark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-zero-standing-privilege-with-cyberark", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-standing-privilege-with-cyberarkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/implementing-zero-standing-privilege-with-cyberark .github/skills/implementing-zero-standing-privilege-with-cyberark && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "implementing-zero-standing-privilege-with-cyberark" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark into .github/skills/implementing-zero-standing-privilege-with-cyberark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-zero-standing-privilege-with-cyberark", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-standing-privilege-with-cyberark --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/implementing-zero-standing-privilege-with-cyberark .opencode/skills/implementing-zero-standing-privilege-with-cyberark && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "implementing-zero-standing-privilege-with-cyberark" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark into .opencode/skills/implementing-zero-standing-privilege-with-cyberark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-zero-standing-privilege-with-cyberark", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
implementing-zero-standing-privilege-with-cyberark- GitHub stars
- 34k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 588 words
- Files
- 8 (incl. scripts, references, assets)
- Skills in repo
- 644
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time…
- Works in 5 steps: Integrate Cloud Providers → Define Access Policies → Configure Session Monitoring → …
- Implementing zero standing privilege / just-in-time privileged access models with CyberArk
- SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 3 more sections
- Runs Python scripts from its folder
What it does
Implementing Zero Standing Privilege With Cyberark is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time, Entitlements, Approvals). Use when designing or implementing zero standing privilege / just-in-time privileged access models with CyberArk, or when replacing persistent cloud admin roles with time-bound, approval-gated sessions.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).
It sits in DevOps & Cloud. It works with Amazon Web Services, Google Cloud and Microsoft Azure. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
- Implementing zero standing privilege / just-in-time privileged access models with CyberArk
- Replacing persistent cloud admin roles with time-bound
- Approval-gated sessions
Example prompts
- “/implementing-zero-standing-privilege-with-cyberark”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.cyberark.comcyberark.comaws.amazon.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Implementing Zero Standing Privilege With Cyberark loads about 2.3k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 588 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 588 words, ~2,314 tokens.
Download SKILL.mdSave it as
.claude/skills/implementing-zero-standing-privilege-with-cyberark/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- implementing-zero-standing-privilege-with-cyberark
- description
- Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time, Entitlements, Approvals). Use when designing or implementing zero standing privilege / just-in-time privileged access models with CyberArk, or when replacing persistent cloud admin roles with time-bound, approval-gated sessions.
- domain
- cybersecurity
- subdomain
- identity-access-management
- tags
- cyberark, zero-standing-privilege, jit-access, pam, cloud-security, least-privilege
- version
- 1.0
- author
- mahipal
- license
- Apache-2.0
- nist_csf
- PR.AA-01, PR.AA-02, PR.AA-05, PR.AA-06
- mitre_attack
- T1078, T1110, T1556, T1098, T1078.004
Implementing Zero Standing Privilege with CyberArk
Overview
Zero 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.
When to Use
- When deploying or configuring implementing zero standing privilege with cyberark capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- CyberArk Identity Security Platform (Privilege Cloud or self-hosted)
- CyberArk Secure Cloud Access (SCA) license
- Cloud provider accounts (AWS, Azure, GCP) with admin access for integration
- ITSM integration (ServiceNow, Jira) for approval workflows
- CyberArk Vault configured with safe management
Core Concepts
TEA Framework (Time, Entitlements, Approvals)
| Component | Description | Configuration |
|---|---|---|
| Time | Duration of the privileged session | Min 15 minutes, max 8 hours, default 1 hour |
| Entitlements | Permissions granted during the session | Dynamically scoped IAM roles/policies |
| Approvals | Authorization workflow before access | Auto-approve, manager approval, or multi-level |
ZSP Architecture
User requests access via CyberArk
│
├── CyberArk evaluates request against policies:
│ ├── Is user eligible for this access?
│ ├── Does the request comply with TEA policies?
│ └── Is approval required?
│
├── [If approval needed] → Route to approver (ITSM/ChatOps)
│
├── Upon approval:
│ ├── CyberArk creates ephemeral IAM role in target cloud
│ ├── Scopes permissions to minimum required entitlements
│ ├── Sets session TTL (time-bound)
│ └── Provisions temporary credentials
│
├── User accesses cloud resources via session
│ ├── All actions logged and recorded
│ └── Session monitored for policy violations
│
└── Session expires:
├── Ephemeral role deleted
├── Temporary credentials revoked
└── Zero standing privileges remainCyberArk Components
| Component | Role |
|---|---|
| Identity Security Platform | Central management and policy engine |
| Privilege Cloud Vault | Stores privileged credentials and keys |
| Secure Cloud Access | Creates/destroys ephemeral cloud roles |
| Endpoint Privilege Manager | Controls local admin and app elevation |
| Privileged Session Manager | Records and monitors privileged sessions |
Workflow
Step 1: Integrate Cloud Providers
AWS Integration:
- Create a CyberArk integration role in AWS IAM
- Configure cross-account trust policy allowing CyberArk to assume roles
- Create IAM policies that define maximum allowed entitlements
- Register AWS accounts in CyberArk SCA
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::CYBERARK_ACCOUNT:role/CyberArkSCARole"
},
"Action": "sts:AssumeRole",
"Condition": {
"StringEquals": {
"sts:ExternalId": "cyberark-external-id"
}
}
}]
}Azure Integration:
- Register CyberArk as an enterprise application in Microsoft Entra ID
- Grant CyberArk application permissions: Directory.ReadWrite.All, RoleManagement.ReadWrite.Directory
- Create custom Azure roles with scoped permissions
- Register Azure subscriptions in CyberArk SCA
GCP Integration:
- Create a service account for CyberArk in GCP
- Grant IAM Admin and Service Account Admin roles
- Configure workload identity federation for cross-cloud access
- Register GCP projects in CyberArk SCA
Show full SKILL.md (221 more words)Show less
Step 2: Define Access Policies
Create policies that map job functions to cloud entitlements:
# CyberArk SCA Policy Example
policy_name: "developer-aws-read-access"
description: "Read-only access to AWS production for developers"
target_cloud: "aws"
target_accounts: ["123456789012", "987654321098"]
time_policy:
max_duration: "4h"
default_duration: "1h"
business_hours_only: true
timezone: "America/New_York"
entitlement_policy:
aws_managed_policies:
- "arn:aws:iam::aws:policy/ReadOnlyAccess"
deny_actions:
- "iam:*"
- "organizations:*"
- "sts:*"
resource_restrictions:
- "arn:aws:s3:::production-*"
approval_policy:
approval_required: true
approvers:
- type: "manager"
- type: "group"
group: "cloud-security-team"
auto_approve_conditions:
- previous_approved_same_policy: true
within_days: 7
escalation_timeout: "2h"
escalation_approver: "cloud-security-lead"Step 3: Configure Session Monitoring
Set up privileged session recording and real-time monitoring:
- Enable session recording for all ZSP sessions
- Configure keystroke logging for SSH/RDP sessions
- Set up real-time alerts for suspicious activities:
- Attempts to escalate privileges during session
- Access to resources outside policy scope
- Session duration exceeding 2x the normal pattern
- Forward session metadata to SIEM
Step 4: Implement Approval Workflows
Integrate with ITSM tools for access request and approval:
- ServiceNow: CyberArk SCA connector creates ServiceNow tickets for approval
- Slack/Teams: ChatOps bot for quick approvals within messaging platforms
- Jira: Integration for development-related access requests
- Auto-Approval: Configure rules for low-risk, previously approved requests
Step 5: Migrate from Standing Privileges
Phase 1: DISCOVERY (Weeks 1-2)
├── Inventory all standing privileged roles across cloud accounts
├── Map users to their standing role assignments
├── Analyze CloudTrail/activity logs for actual permission usage
└── Identify roles that can be converted to JIT
Phase 2: POLICY CREATION (Weeks 3-4)
├── Create ZSP policies based on actual usage analysis
├── Define TEA parameters for each policy
├── Configure approval workflows
└── Test policies with pilot users
Phase 3: MIGRATION (Weeks 5-8)
├── Assign ZSP policies to pilot group
├── Remove standing privileges from pilot users
├── Monitor for access issues and adjust policies
├── Expand to additional teams incrementally
└── Remove all standing privileges organization-wide
Phase 4: GOVERNANCE (Ongoing)
├── Monthly review of ZSP policy effectiveness
├── Quarterly entitlement optimization
├── Monitor for policy drift or standing privilege re-creation
└── Report ZSP metrics to security leadershipValidation Checklist
- Cloud providers integrated with CyberArk SCA
- TEA policies defined for all privileged access scenarios
- Approval workflows configured and tested
- Session recording and monitoring enabled
- All standing privileged roles identified for migration
- Pilot group successfully using ZSP without standing privileges
- Break-glass procedure defined for emergency access
- SIEM integration receiving session and access logs
- Auto-approval rules configured for low-risk, repeat access
- Organization-wide migration plan approved and scheduled
- KPI tracking: reduction in standing privilege assignments
References
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts, references, assets) in skills/implementing-zero-standing-privilege-with-cyberark of mukul975/Anthropic-Cybersecurity-Skills.
- SKILL.md
- LICENSE
- assets/template.md
- references/api-reference.md
- references/standards.md
- references/workflows.md
- scripts/agent.py
- scripts/process.py
Open the folder on GitHubat commit 54a7988
Compare with similar skills
Implementing Zero Standing Privilege With Cyberark next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Implementing Zero Standing Privilege With Cyberark this skillmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Cloud Misconfig Auditorcriptogus/agent-evolve-network | 288 | — | ~965 | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Operate Cloud Posture Toolchaincyberful/cyberful | 135 | — | ~907 | Automated safety check: Pass | AGPL-3.0 | |
| Cloud Cost Optimizationwshobson/agents | 40k | 14 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Terravision Cloud Diagramspatrickchugh/terravision | 1.6k | — | ~5.6k | Automated safety check: Notes | AGPL-3.0-only | |
| Thesvgglincker/thesvg | 2.8k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Operate Cloud Posture Toolchain
cyberful/cyberful
Operate Prowler, Cloudsplaining, cloud CLIs, policy documents, and resource evidence for advanced AWS, Azure, GCP, and Kubernetes-adjacent posture assessment.
Cloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
Terravision Cloud Diagrams
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
Thesvg
glincker/thesvg
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.
Terrashark
LukasNiessen/terrashark
Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps.
More from mukul975/Anthropic-Cybersecurity-Skills
All 644 skills in this repoCampaign Attribution Evidence Analysis
mukul975/Anthropic-Cybersecurity-Skills
Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.
Go Malware Analysis in Ghidra
mukul975/Anthropic-Cybersecurity-Skills
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
LNK and Jump List Forensics
mukul975/Anthropic-Cybersecurity-Skills
Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.
Malware Persistence Analysis with Autoruns
mukul975/Anthropic-Cybersecurity-Skills
Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.
NTFS MFT Deleted File Recovery
mukul975/Anthropic-Cybersecurity-Skills
Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.
Network Covert Channel Analysis
mukul975/Anthropic-Cybersecurity-Skills
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Related
Categories
Questions about Implementing Zero Standing Privilege With Cyberark
What does Implementing Zero Standing Privilege With Cyberark do?
Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time…. Implementing Zero Standing Privilege With Cyberark is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time, Entitlements, Approvals).
When should I use Implementing Zero Standing Privilege With Cyberark?
Implementing Zero Standing Privilege With Cyberark fits situations like: implementing zero standing privilege / just-in-time privileged access models with CyberArk; replacing persistent cloud admin roles with time-bound; approval-gated sessions.
How do I install Implementing Zero Standing Privilege With Cyberark in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a claude-code`. Or copy the skill folder (skills/implementing-zero-standing-privilege-with-cyberark in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-zero-standing-privilege-with-cyberark in your project. Claude Code loads it when a task matches its description.
How do I install Implementing Zero Standing Privilege With Cyberark in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a codex`. Or copy the skill folder (skills/implementing-zero-standing-privilege-with-cyberark in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-zero-standing-privilege-with-cyberark in your project. Codex loads it when a task matches its description.
Can I use Implementing Zero Standing Privilege With Cyberark in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-standing-privilege-with-cyberark -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-zero-standing-privilege-with-cyberark, .gemini/skills/implementing-zero-standing-privilege-with-cyberark, .github/skills/implementing-zero-standing-privilege-with-cyberark and .opencode/skills/implementing-zero-standing-privilege-with-cyberark in your project.
What does Implementing Zero Standing Privilege With Cyberark need to run?
Going by SKILL.md and its folder, Implementing Zero Standing Privilege With Cyberark needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Implementing Zero Standing Privilege With Cyberark access the network?
SKILL.md names 3 domains. As links in the text: docs.cyberark.com, cyberark.com and aws.amazon.com. This is read from the text; nothing was executed.
Is Implementing Zero Standing Privilege With Cyberark safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Implementing Zero Standing Privilege With Cyberark use?
Implementing Zero Standing Privilege With Cyberark is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Implementing Zero Standing Privilege With Cyberark use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Implementing Zero Standing Privilege With Cyberark?
Skills that share tags, products or a category with Implementing Zero Standing Privilege With Cyberark: Cloud Misconfig Auditor (criptogus/agent-evolve-network, 288 stars), Operate Cloud Posture Toolchain (cyberful/cyberful, 135 stars), Cloud Cost Optimization (wshobson/agents, 40k stars) and Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementing Zero Standing Privilege With Cyberark?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 33,993 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.
Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.