mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-07 03:00:19 +03:00
Initial commit - 611 cybersecurity skills across all subdomains
This commit is contained in:
+31
@@ -0,0 +1,31 @@
|
||||
# Standards and References - Privileged Access Management with CyberArk
|
||||
|
||||
## NIST Standards
|
||||
- **NIST SP 800-53 Rev 5**: Security and Privacy Controls
|
||||
- AC-2: Account Management
|
||||
- AC-5: Separation of Duties
|
||||
- AC-6: Least Privilege
|
||||
- AC-6(7): Review of User Privileges (Privileged Accounts)
|
||||
- AU-14: Session Audit
|
||||
- IA-5: Authenticator Management
|
||||
- **NIST SP 800-171**: Protecting CUI - 3.1.5 Least Privilege, 3.1.7 Privileged Functions
|
||||
- **NIST SP 800-63B**: Digital Identity Guidelines - Authentication
|
||||
- **NIST Cybersecurity Framework**: PR.AC (Identity Management, Authentication, Access Control)
|
||||
|
||||
## CyberArk Documentation
|
||||
- **CyberArk NIST 800-53 Rev 5 Whitepaper**: https://www.cyberark.com/resources/white-papers/nist-sp-800-53-revision-5-implementing-essential-security-controls-with-cyberark-solutions
|
||||
- **CyberArk Privilege Cloud**: SaaS PAM platform
|
||||
- **CyberArk Conjur**: Application secrets management
|
||||
- **CyberArk EPM**: Endpoint privilege management
|
||||
|
||||
## Industry Standards
|
||||
- **CIS Controls v8**: Control 5 - Account Management, Control 6 - Access Control Management
|
||||
- **MITRE ATT&CK**: T1078 (Valid Accounts), T1003 (OS Credential Dumping)
|
||||
- **PCI DSS 4.0**: Requirement 7 (Restrict Access), Requirement 8 (Identify and Authenticate)
|
||||
- **SOX**: Section 404 - Internal controls for privileged access
|
||||
- **ISO 27001**: A.9 Access Control
|
||||
|
||||
## Compliance Frameworks
|
||||
- **FISMA**: Federal compliance requiring NIST 800-53 controls
|
||||
- **HIPAA**: Access controls for PHI systems
|
||||
- **GDPR**: Article 32 - Security of processing
|
||||
+74
@@ -0,0 +1,74 @@
|
||||
# Privileged Access Management Workflows
|
||||
|
||||
## Workflow 1: Privileged Credential Checkout and Use
|
||||
|
||||
```
|
||||
User -> PVWA -> Request Credential -> Dual Control Approval -> Vault Release -> PSM Session -> Target System
|
||||
```
|
||||
|
||||
### Steps:
|
||||
1. User authenticates to PVWA with MFA
|
||||
2. User requests access to privileged account
|
||||
3. If dual control enabled, request routed to approver
|
||||
4. Approver reviews and approves/denies request
|
||||
5. Vault releases credential through PSM
|
||||
6. User connects to target via PSM (never sees password)
|
||||
7. Session recorded (video, keystrokes, commands)
|
||||
8. On disconnect, credential checked back in
|
||||
9. If one-time password mode, CPM rotates credential immediately
|
||||
|
||||
## Workflow 2: Automated Credential Rotation
|
||||
|
||||
### Steps:
|
||||
1. CPM checks rotation schedule for each platform
|
||||
2. CPM connects to target system using reconciliation account
|
||||
3. CPM generates new password meeting complexity requirements
|
||||
4. CPM changes password on target system
|
||||
5. CPM updates password in vault
|
||||
6. CPM verifies new credential works on target
|
||||
7. If verification fails, CPM triggers reconciliation
|
||||
8. Rotation event logged to audit trail
|
||||
9. SIEM alert triggered on rotation failure
|
||||
|
||||
## Workflow 3: Privileged Account Discovery
|
||||
|
||||
### Steps:
|
||||
1. Configure account discovery scan targets (IP ranges, domains)
|
||||
2. Discovery scanner connects to targets using scanning credentials
|
||||
3. Scanner identifies privileged accounts:
|
||||
- Windows: Local admins, domain admins, service accounts
|
||||
- Linux: root, sudoers, service accounts
|
||||
- Database: DBA accounts, application accounts
|
||||
- Network: admin/enable accounts on switches/routers
|
||||
4. Discovered accounts compared against vault inventory
|
||||
5. Unmanaged accounts flagged for review
|
||||
6. Security team reviews and prioritizes onboarding
|
||||
7. Approved accounts onboarded to appropriate safes
|
||||
8. CPM begins credential rotation per platform policy
|
||||
|
||||
## Workflow 4: Break-Glass Emergency Access
|
||||
|
||||
### Steps:
|
||||
1. Normal vault access unavailable (outage, disaster)
|
||||
2. Authorized personnel retrieve break-glass media (sealed envelope, USB)
|
||||
3. Break-glass credentials used to access critical systems directly
|
||||
4. All actions taken with break-glass credentials manually documented
|
||||
5. When vault service restored, all break-glass credentials rotated immediately
|
||||
6. Break-glass media re-sealed with new credentials
|
||||
7. Incident report created documenting break-glass usage
|
||||
8. All actions performed during break-glass reviewed by security team
|
||||
|
||||
## Workflow 5: Incident Response - Compromised Privileged Account
|
||||
|
||||
### Steps:
|
||||
1. PTA detects anomalous privileged account behavior
|
||||
2. Alert generated with risk score and indicators
|
||||
3. Security analyst reviews alert in PVWA/SIEM
|
||||
4. If confirmed compromise:
|
||||
a. Immediately rotate compromised credential via CPM
|
||||
b. Terminate any active PSM sessions using that account
|
||||
c. Review session recordings for malicious activity
|
||||
d. Check for lateral movement using audit logs
|
||||
e. Assess blast radius of compromised privilege level
|
||||
5. Forensic analysis of session recordings
|
||||
6. Post-incident review and policy updates
|
||||
Reference in New Issue
Block a user