Back to catalog
Static reviewDevelopment

Skill dossier

implementing-zero-standing-privilege-with-cyberark

Source declaration

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.

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

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.

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 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. 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-zero-standing-privilege-with-cyberark/SKILL.md:L99]
  • Step 1: Integrate Cloud Providers [Source statement; provisional, not tested. Evidence: skills/implementing-zero-standing-privilege-with-cyberark/SKILL.md:L101]
  • Step 2: Define Access Policies [Source statement; provisional, not tested. Evidence: skills/implementing-zero-standing-privilege-with-cyberark/SKILL.md:L139]
  • Step 3: Configure Session Monitoring [Source statement; provisional, not tested. Evidence: skills/implementing-zero-standing-privilege-with-cyberark/SKILL.md:L179]
  • Step 4: Implement Approval Workflows [Source statement; provisional, not tested. Evidence: skills/implementing-zero-standing-privilege-with-cyberark/SKILL.md:L191]
  • Step 5: Migrate from Standing Privileges [Source statement; provisional, not tested. Evidence: skills/implementing-zero-standing-privilege-with-cyberark/SKILL.md:L200]

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-zero-standing-privilege-with-cyberark/SKILL.md:L1-L27]

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
42.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-zero-standing-privilege-with-cyberark/assets/template.mdReference1.2 KB
skills/implementing-zero-standing-privilege-with-cyberark/LICENSEOther11 KB
skills/implementing-zero-standing-privilege-with-cyberark/references/api-reference.mdReference1.7 KB
skills/implementing-zero-standing-privilege-with-cyberark/references/standards.mdReference1.6 KB
skills/implementing-zero-standing-privilege-with-cyberark/references/workflows.mdReference3.6 KB
skills/implementing-zero-standing-privilege-with-cyberark/scripts/agent.pyScript7.1 KB
skills/implementing-zero-standing-privilege-with-cyberark/scripts/process.pyScript6.9 KB
skills/implementing-zero-standing-privilege-with-cyberark/SKILL.mdInstruction9.3 KB

SKILL.md frontmatter

{
  "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"
  ]
}

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

    Core Concepts

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

  4. 04
    Action

    Workflow

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

  5. 05
    Action

    Step 1: Integrate Cloud Providers

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  6. 06
    Action

    Create a CyberArk integration role in AWS IAM

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

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

    Configure cross-account trust policy allowing CyberArk to assume roles

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  2. 08
    Action

    Create IAM policies that define maximum allowed entitlements

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  3. 09
    Action

    Register AWS accounts in CyberArk SCA

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  4. 10
    Action

    Register CyberArk as an enterprise application in Microsoft Entra ID

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  5. 11
    Action

    Grant CyberArk application permissions: Directory.ReadWrite.All, RoleManagement.ReadWrite.Directory

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  6. 12
    Action

    Create custom Azure roles with scoped permissions

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  7. 13
    Action

    Register Azure subscriptions in CyberArk SCA

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  8. 14
    Action

    Create a service account for CyberArk in GCP

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  9. 15
    Action

    Grant IAM Admin and Service Account Admin roles

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  10. 16
    Action

    Configure workload identity federation for cross-cloud access

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  11. 17
    Action

    Register GCP projects in CyberArk SCA

    Source-described action candidate under “Step 1: Integrate Cloud Providers”; not verified execution.

  12. 18
    Action

    Step 2: Define Access Policies

    Source-described action candidate under “Step 2: Define Access Policies”; not verified execution.

  13. 19
    Action

    Create policies that map job functions to cloud entitlements:

    Source-described action candidate under “Step 2: Define Access Policies”; not verified execution.

  14. 20
    Action

    Step 3: Configure Session Monitoring

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  15. 21
    Action

    Enable session recording for all ZSP sessions

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  16. 22
    Action

    Configure keystroke logging for SSH/RDP sessions

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  17. 23
    Action

    Set up real-time alerts for suspicious activities:

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  18. 24
    Action

    Attempts to escalate privileges during session

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  19. 25
    Action

    Access to resources outside policy scope

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  20. 26
    Action

    Session duration exceeding 2x the normal pattern

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  21. 27
    Action

    Forward session metadata to SIEM

    Source-described action candidate under “Step 3: Configure Session Monitoring”; not verified execution.

  22. 28
    Action

    Step 4: Implement Approval Workflows

    Source-described action candidate under “Step 4: Implement Approval Workflows”; not verified execution.

  23. 29
    Action

    ServiceNow: CyberArk SCA connector creates ServiceNow tickets for approval

    Source-described action candidate under “Step 4: Implement Approval Workflows”; not verified execution.

  24. 30
    Action

    Slack/Teams: ChatOps bot for quick approvals within messaging platforms

    Source-described action candidate under “Step 4: Implement Approval Workflows”; not verified execution.

  25. 31
    Action

    Jira: Integration for development-related access requests

    Source-described action candidate under “Step 4: Implement Approval Workflows”; not verified execution.

  26. 32
    Action

    Auto-Approval: Configure rules for low-risk, previously approved requests

    Source-described action candidate under “Step 4: Implement Approval Workflows”; not verified execution.

  27. 33
    Action

    Step 5: Migrate from Standing Privileges

    Source-described action candidate under “Step 5: Migrate from Standing Privileges”; not verified execution.

  28. 34
    Action

    Validation Checklist

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

  29. 35
    Action

    References

    Source-described action candidate under “References”; 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.

Items warrant review

18 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 useNot observed
Medium

Network access is mentioned

14 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 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

4 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 4 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-zero-standing-privilege-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-zero-standing-privilege-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-zero-standing-privilege-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.