Перейти к содержимому
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
mukul975/implementing-zero-standing-privilege-with-cyberarkLinux, облака и контейнеры

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, Entitlements, Approvals). Use when designing or implementing zero standing privilege / just-in-time p⁩

v1.03 установки+3 за 7 дней36,3 тыс. ЗвездыApache-2.0синхронизировано 12 часов назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/implementing-zero-standing-privilege-with-cyberark

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
Ju0jEqfK63…IpyUpyAg==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакетb3163e64…623aee3f
b3163e648b28…f2b8623aee3f8 файлов · ⁦13.5 KB⁩
ПроверкаСредний3 замечания
  • Исполняемый скрипт в составе навыкаscripts/agent.py
  • Исполняемый скрипт в составе навыкаscripts/process.py
  • Ссылки на внешние домены
Вся проверка
Источникgithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-zero-standing-privilege-with-cyberark@54a7988

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.

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

text
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 remain

CyberArk 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:

  1. Create a CyberArk integration role in AWS IAM
  2. Configure cross-account trust policy allowing CyberArk to assume roles
  3. Create IAM policies that define maximum allowed entitlements
  4. Register AWS accounts in CyberArk SCA
json
{
    "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:

  1. Register CyberArk as an enterprise application in Microsoft Entra ID
  2. Grant CyberArk application permissions: Directory.ReadWrite.All, RoleManagement.ReadWrite.Directory
  3. Create custom Azure roles with scoped permissions
  4. Register Azure subscriptions in CyberArk SCA

GCP Integration:

  1. Create a service account for CyberArk in GCP
  2. Grant IAM Admin and Service Account Admin roles
  3. Configure workload identity federation for cross-cloud access
  4. Register GCP projects in CyberArk SCA

Step 2: Define Access Policies

Create policies that map job functions to cloud entitlements:

yaml
# 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:

  1. Enable session recording for all ZSP sessions
  2. Configure keystroke logging for SSH/RDP sessions
  3. 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
  4. 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

text
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 leadership

Validation 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

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыДаДа
Выполняет команды shellДаДа
Ходит в сетьДаДа
Использует коннекторыДаДа
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

  1. СредняяФайл · Исполняемый скрипт в составе навыкаscripts/agent.py
  2. СредняяФайл · Исполняемый скрипт в составе навыкаscripts/process.py
  3. ИнфоСсылка · Ссылки на внешние домены

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v1.013 нояб. 2026 г.54a7988b3163e64Подписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login