Back to catalog
Static reviewDevelopment

Skill dossier

implementing-privileged-access-management-with-cyberark

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L111]
  • Step 1: Vault Architecture Design [Source statement; provisional, not tested. Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L113]
  • Step 2: Safe and Policy Configuration [Source statement; provisional, not tested. Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L120]
  • Step 3: Platform Configuration [Source statement; provisional, not tested. Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L132]
  • Step 4: Privileged Session Management [Source statement; provisional, not tested. Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L140]
  • Step 5: Integration and Monitoring [Source statement; provisional, not tested. Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L148]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L1-L58]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
55.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-privileged-access-management-with-cyberark/assets/template.mdReference2.5 KB
skills/implementing-privileged-access-management-with-cyberark/LICENSEOther11 KB
skills/implementing-privileged-access-management-with-cyberark/references/api-reference.mdReference4.5 KB
skills/implementing-privileged-access-management-with-cyberark/references/standards.mdReference1.5 KB
skills/implementing-privileged-access-management-with-cyberark/references/workflows.mdReference3 KB
skills/implementing-privileged-access-management-with-cyberark/scripts/agent.pyScript9.6 KB
skills/implementing-privileged-access-management-with-cyberark/scripts/process.pyScript16.5 KB
skills/implementing-privileged-access-management-with-cyberark/SKILL.mdInstruction7.2 KB

SKILL.md frontmatter

{
  "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",
    "tactics": [
      "initial-access",
      "positioning",
      "resource-development"
    ],
    "techniques": [
      {
        "id": "T1586",
        "name": "Compromise Accounts",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1110",
        "name": "Brute Force",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1033",
        "name": "Insider Access Abuse",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1005.002",
        "name": "Account Manipulation: Add Authorized User",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  5. 05
    Action

    Digital Vault: Encrypted credential storage with FIPS 140-2 validated encryption

    Source-described action candidate under “CyberArk Architecture Components”; not verified execution.

  6. 06
    Action

    Central Policy Manager (CPM): Automated password rotation and verification

    Source-described action candidate under “CyberArk Architecture Components”; not verified execution.

Inspect all extracted workflow candidates (59 candidate steps)
  1. 07
    Action

    Privileged Session Manager (PSM): Session isolation, recording, and keystroke logging

    Source-described action candidate under “CyberArk Architecture Components”; not verified execution.

  2. 08
    Action

    Password Vault Web Access (PVWA): Web interface for credential management

    Source-described action candidate under “CyberArk Architecture Components”; not verified execution.

  3. 09
    Action

    Privileged Threat Analytics (PTA): Behavioral analytics for privileged accounts

    Source-described action candidate under “CyberArk Architecture Components”; not verified execution.

  4. 10
    Action

    Conjur Secrets Manager: Application identity and secrets management

    Source-described action candidate under “CyberArk Architecture Components”; not verified execution.

  5. 11
    Action

    Discovery: Scan infrastructure for privileged accounts

    Source-described action candidate under “Credential Lifecycle”; not verified execution.

  6. 12
    Input

    Onboarding: Import accounts into vault with platform assignment

    Source-described input candidate under “Credential Lifecycle”; not verified execution.

  7. 13
    Action

    Rotation: Automated password changes per policy schedule

    Source-described action candidate under “Credential Lifecycle”; not verified execution.

  8. 14
    Action

    Verification: Periodic validation that vaulted credentials work

    Source-described action candidate under “Credential Lifecycle”; not verified execution.

  9. 15
    Action

    Reconciliation: Re-sync credentials when vault and target are out of sync

    Source-described action candidate under “Credential Lifecycle”; not verified execution.

  10. 16
    Action

    Decommissioning: Remove accounts no longer needed

    Source-described action candidate under “Credential Lifecycle”; not verified execution.

  11. 17
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  12. 18
    Action

    Step 1: Vault Architecture Design

    Source-described action candidate under “Step 1: Vault Architecture Design”; not verified execution.

  13. 19
    Action

    Deploy primary vault server in secured network segment

    Source-described action candidate under “Step 1: Vault Architecture Design”; not verified execution.

  14. 20
    Action

    Configure vault high availability with DR vault

    Source-described action candidate under “Step 1: Vault Architecture Design”; not verified execution.

  15. 21
    Action

    Harden vault server OS (remove unnecessary services, disable RDP)

    Source-described action candidate under “Step 1: Vault Architecture Design”; not verified execution.

  16. 22
    Action

    Configure firewall rules (only port 1858 from authorized components)

    Source-described action candidate under “Step 1: Vault Architecture Design”; not verified execution.

  17. 23
    Action

    Set up vault backup with encryption

    Source-described action candidate under “Step 1: Vault Architecture Design”; not verified execution.

  18. 24
    Action

    Step 2: Safe and Policy Configuration

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  19. 25
    Action

    Create safe hierarchy aligned with business units

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  20. 26
    Action

    Define safe members with least-privilege roles:

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  21. 27
    Action

    Safe Admins: manage safe membership

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  22. 28
    Action

    Credential Managers: add/modify accounts

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  23. 29
    Action

    Auditors: view audit logs only

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  24. 30
    Action

    Users: retrieve/use credentials

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  25. 31
    Action

    Configure Master Policy settings:

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  26. 32
    Action

    Require dual control for credential retrieval

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  27. 33
    Action

    Enable exclusive access (one user per credential at a time)

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  28. 34
    Action

    Set one-time password mode for sensitive accounts

    Source-described action candidate under “Step 2: Safe and Policy Configuration”; not verified execution.

  29. 35
    Action

    Step 3: Platform Configuration

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  30. 36
    Action

    Windows Domain Admin: Rotate every 24 hours, verify every 4 hours

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  31. 37
    Action

    Linux Root: Rotate every 72 hours with SSH key rotation

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  32. 38
    Action

    Database Admin (Oracle, SQL Server): Rotate every 24 hours

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  33. 39
    Action

    Network Devices: Rotate every 7 days

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  34. 40
    Action

    Service Accounts: Rotate on schedule with dependency management

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  35. 41
    Action

    Cloud IAM Keys: Rotate every 90 days with dual-key strategy

    Source-described action candidate under “Step 3: Platform Configuration”; not verified execution.

  36. 42
    Action

    Step 4: Privileged Session Management

    Source-described action candidate under “Step 4: Privileged Session Management”; not verified execution.

  37. 43
    Input

    Deploy PSM servers behind load balancer

    Source-described input candidate under “Step 4: Privileged Session Management”; not verified execution.

  38. 44
    Action

    Configure session recording (video, keystroke, command logs)

    Source-described action candidate under “Step 4: Privileged Session Management”; not verified execution.

  39. 45
    Action

    Set up session isolation (users connect through PSM, never directly)

    Source-described action candidate under “Step 4: Privileged Session Management”; not verified execution.

  40. 46
    Action

    Define connection components for RDP, SSH, databases, web apps

    Source-described action candidate under “Step 4: Privileged Session Management”; not verified execution.

  41. 47
    Action

    Configure live session monitoring and termination capabilities

    Source-described action candidate under “Step 4: Privileged Session Management”; not verified execution.

  42. 48
    Action

    Set session recording retention (minimum 1 year for compliance)

    Source-described action candidate under “Step 4: Privileged Session Management”; not verified execution.

  43. 49
    Action

    Step 5: Integration and Monitoring

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  44. 50
    Action

    Forward CyberArk audit logs to SIEM (CEF/Syslog format)

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  45. 51
    Action

    Configure PTA for behavioral analytics:

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  46. 52
    Action

    Detect credential theft indicators

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  47. 53
    Action

    Alert on suspicious privileged session activity

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  48. 54
    Action

    Monitor unmanaged privileged account usage

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  49. 55
    Action

    Integrate with ticketing system for access request workflows

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  50. 56
    Action

    Set up alerts for failed rotation, verification failures, policy violations

    Source-described action candidate under “Step 5: Integration and Monitoring”; not verified execution.

  51. 57
    Action

    Security Controls

    Source-described action candidate under “Security Controls”; not verified execution.

  52. 58
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  53. 59
    Action

    Verification

    Source-described action candidate under “Verification”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

34 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

17 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 17 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

16 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-privileged-access-management-with-cyberark/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/implementing-privileged-access-management-with-cyberark/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-privileged-access-management-with-cyberark
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.