Agent skill

Implementing Privileged Access Management With Cyberark

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation…

Apache-2.0Auto-check passedBackend & APIs

Install Implementing Privileged Access Management With Cyberark

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-privileged-access-management-with-cyberark -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-privileged-access-management-with-cyberark --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-privileged-access-management-with-cyberark .claude/skills/implementing-privileged-access-management-with-cyberark && rm -rf skills-src

Use ~/.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/

Facts

Skill name
implementing-privileged-access-management-with-cyberark
GitHub stars
34k
Token cost
~1.8k tokens
SKILL.md length
728 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation…

  • Works in 5 steps: Vault Architecture Design → Safe and Policy Configuration → Platform Configuration → …
  • Standing up CyberArk PAM
  • SKILL.md covers Overview, When to Use, Prerequisites and Objectives, plus 5 more sections
  • Runs Python scripts from its folder

What it does

Implementing Privileged Access Management With Cyberark is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements. Use when standing up CyberArk PAM, vaulting privileged credentials, or designing credential rotation policies.

Its SKILL.md is about 1.8k 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 Backend & APIs, covering Authorization and RBAC. 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

  • Standing up CyberArk PAM
  • Vaulting privileged credentials
  • Designing credential rotation policies

Example prompts

  • “/implementing-privileged-access-management-with-cyberark”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Vault Architecture Design
  2. Safe and Policy Configuration
  3. Platform Configuration
  4. Privileged Session Management
  5. Integration and Monitoring

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

    No URLs in SKILL.md.

    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 Privileged Access Management With Cyberark loads about 1.8k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 728 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

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). 728 words, ~1,842 tokens.

Download SKILL.mdSave it as .claude/skills/implementing-privileged-access-management-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-privileged-access-management-with-cyberark
description
Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements. Use when standing up CyberArk PAM, vaulting privileged credentials, or designing credential rotation policies.
domain
cybersecurity
subdomain
identity-access-management
tags
iam, identity, access-control, privileged-access, pam, cyberark
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, T1003
mitre_f3.version
1.1
mitre_f3.tactics
initial-access, positioning, resource-development

Implementing Privileged Access Management with CyberArk

Overview

Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure. This skill covers vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements.

When to Use

  • When deploying or configuring implementing privileged access management 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

  • Familiarity with identity access management concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Objectives

  • Design CyberArk vault architecture with high availability
  • Implement automated privileged credential discovery and onboarding
  • Configure credential rotation policies for different account types
  • Deploy Privileged Session Manager (PSM) for session isolation and recording
  • Integrate CyberArk with SIEM for privileged access monitoring
  • Implement just-in-time (JIT) privileged access workflows

Key Concepts

CyberArk Architecture Components
  1. Digital Vault: Encrypted credential storage with FIPS 140-2 validated encryption
  2. Central Policy Manager (CPM): Automated password rotation and verification
  3. Privileged Session Manager (PSM): Session isolation, recording, and keystroke logging
  4. Password Vault Web Access (PVWA): Web interface for credential management
  5. Privileged Threat Analytics (PTA): Behavioral analytics for privileged accounts
  6. Conjur Secrets Manager: Application identity and secrets management
Vault Security Model
  • Master Policy: Global security settings (dual control, exclusive access, one-time passwords)
  • Safes: Logical containers for credentials with granular permissions
  • Platforms: Configuration profiles defining rotation, verification, and reconciliation
  • Account Groups: Link accounts sharing rotation dependencies
Credential Lifecycle
  1. Discovery: Scan infrastructure for privileged accounts
  2. Onboarding: Import accounts into vault with platform assignment
  3. Rotation: Automated password changes per policy schedule
  4. Verification: Periodic validation that vaulted credentials work
  5. Reconciliation: Re-sync credentials when vault and target are out of sync
  6. Decommissioning: Remove accounts no longer needed

Workflow

Step 1: Vault Architecture Design
  1. Deploy primary vault server in secured network segment
  2. Configure vault high availability with DR vault
  3. Harden vault server OS (remove unnecessary services, disable RDP)
  4. Configure firewall rules (only port 1858 from authorized components)
  5. Set up vault backup with encryption
Step 2: Safe and Policy Configuration
  1. Create safe hierarchy aligned with business units
  2. Define safe members with least-privilege roles:
    • Safe Admins: manage safe membership
    • Credential Managers: add/modify accounts
    • Auditors: view audit logs only
    • Users: retrieve/use credentials
  3. Configure Master Policy settings:
    • Require dual control for credential retrieval
    • Enable exclusive access (one user per credential at a time)
    • Set one-time password mode for sensitive accounts
Show full SKILL.md (294 more words)Show less
Step 3: Platform Configuration
  • Windows Domain Admin: Rotate every 24 hours, verify every 4 hours
  • Linux Root: Rotate every 72 hours with SSH key rotation
  • Database Admin (Oracle, SQL Server): Rotate every 24 hours
  • Network Devices: Rotate every 7 days
  • Service Accounts: Rotate on schedule with dependency management
  • Cloud IAM Keys: Rotate every 90 days with dual-key strategy
Step 4: Privileged Session Management
  1. Deploy PSM servers behind load balancer
  2. Configure session recording (video, keystroke, command logs)
  3. Set up session isolation (users connect through PSM, never directly)
  4. Define connection components for RDP, SSH, databases, web apps
  5. Configure live session monitoring and termination capabilities
  6. Set session recording retention (minimum 1 year for compliance)
Step 5: Integration and Monitoring
  1. Forward CyberArk audit logs to SIEM (CEF/Syslog format)
  2. Configure PTA for behavioral analytics:
    • Detect credential theft indicators
    • Alert on suspicious privileged session activity
    • Monitor unmanaged privileged account usage
  3. Integrate with ticketing system for access request workflows
  4. Set up alerts for failed rotation, verification failures, policy violations

Security Controls

ControlNIST 800-53Description
Privileged AccessAC-6(7)Privileged account controls
Credential ManagementIA-5Automated credential rotation
Session RecordingAU-14Session audit capability
Access EnforcementAC-3Vault-enforced access policies
Separation of DutiesAC-5Dual control for sensitive operations

Common Pitfalls

  • Not configuring reconciliation accounts leading to lockouts after rotation
  • Setting rotation schedules too aggressive for service accounts with dependencies
  • Failing to test PSM connection components before production deployment
  • Not establishing break-glass procedures for vault unavailability
  • Overlooking network device credential management

Verification

  • Vault accessible only from authorized components
  • Credential rotation succeeds for all onboarded accounts
  • PSM sessions recorded and searchable
  • Dual control enforced for sensitive credential checkout
  • SIEM receives CyberArk audit events
  • Break-glass procedure tested and documented
  • DR vault failover tested successfully

© 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-privileged-access-management-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 Privileged Access Management 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.

Implementing Privileged Access Management With Cyberark compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implementing Privileged Access Management With Cyberark this skillmukul975/Anthropic-Cybersecurity-Skills34k—~1.8kAutomated safety check: PassApache-2.0
Lokalise Security Basicsjeremylongshore/tons-of-skills-marketplace2.8k—~2.4kAutomated safety check: NotesMIT
Cb Security HardeningBlkLeg/CircuitBreaker201—~2.1kAutomated safety check: PassMIT
Supercheck Feature Implementationsupercheck-io/supercheck215—~1.1kAutomated safety check: PassAGPL-3.0
Audit Reconccashwell/evm-cortex131—~1.5kAutomated safety check: PassMIT
Sec Checkwaynesutton/markdown-site627—~753Automated safety check: PassMIT

Similar skills

  • Lokalise Security Basics

    jeremylongshore/tons-of-skills-marketplace

    Apply Lokalise security best practices for API tokens and access control.

    2.8k GitHub stars~2.4k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Cb Security Hardening

    BlkLeg/CircuitBreaker

    Enforces Circuit Breaker security hardening conventions across backend, frontend, Docker, and nginx.

    201 GitHub stars~2.1k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed
  • Supercheck Feature Implementation

    supercheck-io/supercheck

    Implement a new or changed Supercheck feature end to end across schema, auth/RBAC, services, routes/actions, UI, queues/workers, CLI/recorder, tests, docs, and deployment contracts.

    215 GitHub stars~1.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Audit Recon

    ccashwell/evm-cortex

    A skill your agent uses when performing initial audit reconnaissance.

    131 GitHub stars~1.5k tokensUpdated 10 days ago
    Backend & APIsAuto-check passed
  • Sec Check

    waynesutton/markdown-site

    Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code.

    627 GitHub stars~753 tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed
  • Security Threat Model

    majiayu000/spellbook

    Threat-model product features, APIs, data flows, secrets, permissions, supply-chain changes, auth boundaries, and risky code paths before or during implementation.

    287 GitHub stars~561 tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign 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.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • 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.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • 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.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • 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.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • 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.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • 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.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Implementing Privileged Access Management With Cyberark

What does Implementing Privileged Access Management With Cyberark do?

Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation…. Implementing Privileged Access Management With Cyberark is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements.

When should I use Implementing Privileged Access Management With Cyberark?

Implementing Privileged Access Management With Cyberark fits situations like: standing up CyberArk PAM; vaulting privileged credentials; designing credential rotation policies.

How do I install Implementing Privileged Access Management With Cyberark in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-privileged-access-management-with-cyberark -a claude-code`. Or copy the skill folder (skills/implementing-privileged-access-management-with-cyberark in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-privileged-access-management-with-cyberark in your project. Claude Code loads it when a task matches its description.

How do I install Implementing Privileged Access Management With Cyberark in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-privileged-access-management-with-cyberark -a codex`. Or copy the skill folder (skills/implementing-privileged-access-management-with-cyberark in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-privileged-access-management-with-cyberark in your project. Codex loads it when a task matches its description.

Can I use Implementing Privileged Access Management 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-privileged-access-management-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-privileged-access-management-with-cyberark, .gemini/skills/implementing-privileged-access-management-with-cyberark, .github/skills/implementing-privileged-access-management-with-cyberark and .opencode/skills/implementing-privileged-access-management-with-cyberark in your project.

What does Implementing Privileged Access Management With Cyberark need to run?

Going by SKILL.md and its folder, Implementing Privileged Access Management With Cyberark needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Implementing Privileged Access Management With Cyberark access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Implementing Privileged Access Management 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 Privileged Access Management With Cyberark use?

Implementing Privileged Access Management 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 Privileged Access Management With Cyberark use?

About 1.8k tokens (SKILL.md is roughly 7.4k 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 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Implementing Privileged Access Management With Cyberark?

Skills that share tags, products or a category with Implementing Privileged Access Management With Cyberark: Lokalise Security Basics (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Cb Security Hardening (BlkLeg/CircuitBreaker, 201 stars), Supercheck Feature Implementation (supercheck-io/supercheck, 215 stars) and Audit Recon (ccashwell/evm-cortex, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implementing Privileged Access Management With Cyberark?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 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.