implementing-privileged-access-management-with-cyberark
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- implementing-privileged-access-management-with-cyberark
- tags
- [ "iam", "identity", "access-control", "privileged-access", "pam", "cyberark" ]
- author
- mahipal
- domain
- cybersecurity
- license
- Apache-2.0
- version
- 1.0
- mitre_f3
- { "tactics": [ "initial-access", "positioning", "resource-development" ], "version": "1.1", "techniques": [ { "id": "T1586", "name": "Compromise Accounts", "source": "attack", "tactic": "resource-development" }, { "id": "T1110", "name": "Brute Force", "source": "attack", "tactic": "initial-access" }, { "id": "F1033", "name": "Insider Access Abuse", "source": "f3", "tactic": "initial-access" }, { "id": "F1005.002", "name": "Account Manipulation: Add Authorized User", "source": "f3", "tactic": "positioning" }, { "id": "F1006.002", "name": "Account Takeover: Exposed Login Credential", "source": "f3", "tactic": "initial-access" } ] }
- nist_csf
- [ "PR.AA-01", "PR.AA-02", "PR.AA-05", "PR.AA-06" ]
- subdomain
- identity-access-management
- 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.
- mitre_attack
- [ "T1078", "T1110", "T1556", "T1098", "T1003" ]
02 资源文件 7
- 资产文件assets/template.md2.5 KB
- 许可证LICENSE11.0 KB
- 参考文档references/api-reference.md4.5 KB
- 参考文档references/standards.md1.5 KB
- 参考文档references/workflows.md3.0 KB
- 脚本scripts/agent.py9.6 KB
- 脚本scripts/process.py16.5 KB
03 SKILL.md 正文
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
- Digital Vault: Encrypted credential storage with FIPS 140-2 validated encryption
- Central Policy Manager (CPM): Automated password rotation and verification
- Privileged Session Manager (PSM): Session isolation, recording, and keystroke logging
- Password Vault Web Access (PVWA): Web interface for credential management
- Privileged Threat Analytics (PTA): Behavioral analytics for privileged accounts
- 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
- Discovery: Scan infrastructure for privileged accounts
- Onboarding: Import accounts into vault with platform assignment
- Rotation: Automated password changes per policy schedule
- Verification: Periodic validation that vaulted credentials work
- Reconciliation: Re-sync credentials when vault and target are out of sync
- Decommissioning: Remove accounts no longer needed
Workflow
Step 1: Vault Architecture Design
- Deploy primary vault server in secured network segment
- Configure vault high availability with DR vault
- Harden vault server OS (remove unnecessary services, disable RDP)
- Configure firewall rules (only port 1858 from authorized components)
- Set up vault backup with encryption
Step 2: Safe and Policy Configuration
- Create safe hierarchy aligned with business units
- 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
- 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
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
- Deploy PSM servers behind load balancer
- Configure session recording (video, keystroke, command logs)
- Set up session isolation (users connect through PSM, never directly)
- Define connection components for RDP, SSH, databases, web apps
- Configure live session monitoring and termination capabilities
- Set session recording retention (minimum 1 year for compliance)
Step 5: Integration and Monitoring
- Forward CyberArk audit logs to SIEM (CEF/Syslog format)
- Configure PTA for behavioral analytics:
- Detect credential theft indicators
- Alert on suspicious privileged session activity
- Monitor unmanaged privileged account usage
- Integrate with ticketing system for access request workflows
- Set up alerts for failed rotation, verification failures, policy violations
Security Controls
| Control | NIST 800-53 | Description |
|---|---|---|
| Privileged Access | AC-6(7) | Privileged account controls |
| Credential Management | IA-5 | Automated credential rotation |
| Session Recording | AU-14 | Session audit capability |
| Access Enforcement | AC-3 | Vault-enforced access policies |
| Separation of Duties | AC-5 | Dual 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
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.
grants
NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.