Policies Overview
Policies in IdentityCenter define the rules and constraints that govern identity management in your organization. They automate compliance checks, enforce security standards, and ensure consistent governance across all connected systems.
What are Policies?
Policies are configurable rules that:
- Detect violations of security and compliance requirements
- Alert administrators to potential issues
- Enforce governance standards automatically
- Report on compliance status for auditors
Policy Types
Compliance Policies
Ensure adherence to regulatory frameworks:
| Framework |
Example Policies |
| SOX |
Segregation of duties, access review completion |
| HIPAA |
PHI access controls, minimum necessary access |
| GDPR |
Data access limitations, consent tracking |
| PCI-DSS |
Cardholder data access, unique user IDs |
| ISO 27001 |
Access control, account management |
Security Policies
Protect against security risks:
| Policy |
Purpose |
| Privileged Access |
Monitor and control admin access |
| Orphaned Accounts |
Detect accounts without owners |
| Stale Accounts |
Find inactive accounts |
| Password Age |
Identify accounts with old passwords |
| Failed Logins |
Track authentication failures |
Governance Policies
Enforce organizational standards:
| Policy |
Purpose |
| Naming Standards |
Ensure consistent account naming |
| Required Attributes |
Verify accounts have necessary data |
| Manager Assignment |
All accounts must have a manager |
| Department Structure |
Valid department assignments |
Policy Architecture
┌─────────────────────────────────────────────────────────────┐
│ Policy Engine │
├─────────────────────────────────────────────────────────────┤
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Evaluator │ │ Scheduler │ │ Reporter │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ Policy Rules │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Conditions │ Actions │ Exceptions │ Severity │ │
│ └──────────────────────────────────────────────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ Violation Store │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Active Violations │ History │ Remediation Log │ │
│ └──────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
Policy Components
Conditions
Define when a policy violation occurs:
IF [Condition] THEN [Violation]
Examples:
- IF account.lastLogin > 90 days THEN "Stale Account"
- IF account.manager IS NULL THEN "Missing Manager"
- IF user IN group("Domain Admins") AND user IN group("Finance") THEN "SoD Violation"
Severity Levels
| Level |
Description |
Response Time |
| Critical |
Immediate security risk |
Hours |
| High |
Significant compliance issue |
1-2 days |
| Medium |
Moderate risk |
1 week |
| Low |
Minor issue |
1 month |
| Info |
Awareness only |
As needed |
Actions
What happens when a violation is detected:
| Action |
Description |
| Log |
Record the violation |
| Alert |
Send notification |
| Ticket |
Create support ticket |
| Disable |
Disable the account |
| Flag |
Mark for review |
Exceptions
Exclude specific cases from policy enforcement:
| Exception Type |
Example |
| User |
CEO account exempt from password policy |
| Group |
Service accounts exempt from login tracking |
| Time |
Ignore during maintenance windows |
| Attribute |
Accounts with specific flag are exempt |
Built-in Policies
IdentityCenter includes these pre-configured policies:
Account Lifecycle
| Policy |
Description |
Default Severity |
| Orphaned Account |
Account has no manager |
Medium |
| Stale Account |
No login in 90 days |
Medium |
| Disabled with Access |
Disabled but still has permissions |
High |
| Terminated Employee |
Account active after termination |
Critical |
Access Control
| Policy |
Description |
Default Severity |
| Privileged Account |
Admin access detected |
Info |
| Excessive Permissions |
Too many group memberships |
Medium |
| Cross-Domain Access |
Access spans multiple domains |
Low |
| Service Account Login |
Interactive login by service account |
High |
Segregation of Duties
| Policy |
Description |
Default Severity |
| Finance + IT Access |
Both financial and IT admin |
High |
| Create + Approve |
Can create and approve own requests |
High |
| Admin + User |
Both admin and standard user roles |
Medium |
Data Protection
| Policy |
Description |
Default Severity |
| Sensitive Data Access |
Access to classified data |
Info |
| External Sharing |
Data shared outside organization |
Medium |
| Bulk Export |
Large data exports |
High |
Policy Evaluation
Evaluation Triggers
| Trigger |
Description |
| Scheduled |
Run at configured intervals |
| On Change |
Evaluate when identity changes |
| On Demand |
Manual evaluation |
| Real-time |
Continuous monitoring |
Evaluation Scope
| Scope |
Description |
| All Identities |
Evaluate every identity |
| Changed Only |
Only recently modified |
| Specific Groups |
Target specific populations |
| Sampled |
Random sampling for large environments |
Violation Management
Violation Lifecycle
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ New │ → │ Active │ → │Remediated│ → │ Closed │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
│
▼
┌──────────┐
│ Excepted │
└──────────┘
Managing Violations
| Action |
Description |
| Acknowledge |
Mark as seen |
| Assign |
Assign to owner |
| Remediate |
Fix the issue |
| Exception |
Create exception |
| Defer |
Postpone resolution |
Compliance Reporting
Standard Reports
| Report |
Contents |
| Policy Summary |
Overall compliance status |
| Violation Trends |
Historical violation data |
| Open Violations |
Current active violations |
| Remediation Status |
Progress on fixes |
| Exception Register |
All active exceptions |
Compliance Dashboards
- Overall compliance score
- Violations by severity
- Violations by policy
- Trend over time
- Top violating accounts
Best Practices
Policy Design
- Start with Frameworks - Use compliance requirements as your guide
- Be Specific - Clear conditions reduce false positives
- Set Realistic Severity - Not everything is critical
- Document Rationale - Explain why each policy exists
Exception Management
- Require Justification - Document why exceptions are needed
- Set Expiration - Exceptions should be temporary
- Review Regularly - Audit exception list quarterly
- Limit Scope - Make exceptions as narrow as possible
Continuous Improvement
- Monitor False Positives - Tune policies that generate noise
- Track Trends - Identify systemic issues
- Update for Changes - Adjust when requirements change
- Benchmark - Compare to industry standards
Next Steps