Initial commit - 611 cybersecurity skills across all subdomains

This commit is contained in:
mukul975
2026-02-25 10:47:44 +01:00
commit 22a7ab1462
1765 changed files with 280648 additions and 0 deletions
@@ -0,0 +1,46 @@
# Role Mining for RBAC Optimization - Standards Reference
## RBAC Standards
### ANSI/INCITS 359-2012 - Core RBAC
- Defines User, Role, Permission, Session abstractions
- Role assignment: users are assigned to roles
- Permission assignment: permissions are assigned to roles
- Role hierarchy: senior roles inherit junior role permissions
- Separation of Duty constraints (static and dynamic)
### NIST RBAC Model (SP 800-162)
- Core RBAC: Basic user-role and role-permission mappings
- Hierarchical RBAC: Role inheritance relationships
- Constrained RBAC: Static and dynamic separation of duties
- Symmetric RBAC: Combined user-centric and permission-centric views
## Identity Governance Standards
### ISO 27001:2022 - A.5.15 Access Control
- Access control policy based on business and security requirements
- Roles determined by job function
- Regular review of access rights
- Formal authorization for privilege changes
### NIST SP 800-53 Rev 5
- AC-2: Account Management
- AC-3: Access Enforcement
- AC-5: Separation of Duties
- AC-6: Least Privilege
- AC-16: Security and Privacy Attributes
- AC-24: Access Control Decisions
## Role Mining Research
### Key Algorithms
- **RoleMiner (Vaidya et al., 2007)**: Iterative role mining minimizing WSC
- **CompleteMiner / FastMiner (Vaidya et al., 2006)**: Complete vs. approximate algorithms
- **ORCA (Schlegelmilch & Steffens, 2005)**: Clustering-based approach
- **Graph Optimization (Lu et al., 2008)**: Graph-based role mining
### Quality Metrics
- Weighted Structural Complexity: min(|UA| + |PA| + |Roles|)
- Boolean Matrix Decomposition error
- Jaccard similarity between mined and original access
- Role coverage percentage
@@ -0,0 +1,82 @@
# Role Mining for RBAC Optimization - Workflows
## End-to-End Role Mining Workflow
```
Phase 1: DATA COLLECTION (Week 1-2)
├── Export user-permission data from all identity sources
│ ├── Active Directory group memberships
│ ├── Cloud IAM role assignments
│ ├── Application-level permissions
│ └── Database access grants
├── Collect HR data (job titles, departments, cost centers)
├── Normalize data into User-Permission Assignment (UPA) matrix
└── Clean data: remove disabled accounts, system accounts
Phase 2: ANALYSIS (Week 3-4)
├── Run clustering algorithms (hierarchical, k-means)
├── Run Formal Concept Analysis for exact role candidates
├── Compare results using WSC and coverage metrics
├── Identify optimal number of roles via silhouette analysis
└── Map candidate roles to organizational structure
Phase 3: VALIDATION (Week 5-6)
├── Present candidate roles to business unit managers
├── Validate each role against job descriptions
├── Identify and resolve outlier permissions
├── Define role hierarchy (inheritance relationships)
└── Agree on role names and descriptions
Phase 4: IMPLEMENTATION (Week 7-8)
├── Create roles in identity governance platform
├── Assign users to validated roles
├── Remove individual permission assignments
├── Test access for sample users in each role
└── Document role definitions and approval chain
Phase 5: GOVERNANCE (Ongoing)
├── Monitor for permission drift
├── Quarterly role effectiveness review
├── Re-run mining annually to detect new patterns
└── Track role count and WSC metrics over time
```
## Data Normalization Workflow
```
Raw Data Sources
├── AD: user → group → permissions
│ Normalize to: user_id, permission_id
├── AWS: user/role → policy → actions
│ Normalize to: user_id, permission_id
├── Azure: user → role → permissions
│ Normalize to: user_id, permission_id
└── Applications: user → app_role → features
Normalize to: user_id, permission_id
Merge all sources → Deduplicate → Create UPA matrix
```
## Role Consolidation Workflow
```
Mining produces N candidate roles
├── Remove roles with < 3 users (outliers)
├── Merge roles with > 90% Jaccard similarity
├── Identify hierarchical relationships:
│ └── If Role A permissions ⊂ Role B permissions
│ → Role A is junior to Role B
├── Check for SoD violations:
│ └── Does any role combine conflicting permissions?
│ → Split into separate roles if needed
└── Final role set with hierarchy and constraints
```