
π©οΈ CloudCSF β Day 22
Control #21: Ghost Access β Offboarding Failure That Leads to Breaches
βYou revoked their email. But did you revoke their AWS, GitHub, Zoom, and 10 other apps?β
π Whatβs the Problem?
Most organizations assume user offboarding is complete once:
- HR revokes email
- IT disables workstation logins
But in reality:
- Departed users often retain access to Cloud, SaaS, DevOps tools, and APIs
- 44% of organizations admit ex-employees had active access for more than a week
- 1 in 3 breaches involved former or rogue insider accounts
π§ Real-World Incidents
| Company | Breach Cause |
|---|---|
| Ex-employee used admin panel to sabotage internal systems | |
| Capital One | Former AWS employee exploited overly-permissive roles |
| Shopify | Insider misused vendor login credentials |
π¨ Top Missed Offboarding Items
- β GitHub/GitLab account not revoked
- β Cloud accounts (AWS, Azure, GCP) still active
- β Slack/Zoom/CRM access not terminated
- β SSO/IdP not de-provisioned across all apps
- β API keys & secrets owned by former devs still valid
- β Shared mailbox or Google Drive not locked
π CloudCSF Offboarding Control Framework
- Centralized User Directory
- Use Azure AD / Okta / JumpCloud
- Automate app access provisioning & deprovisioning
- Offboarding Workflow Integration
- Tie offboarding to HRMS like SAP, Workday, Zoho People
- Trigger checklist-based access revocation
- Cloud Account Aggregation Audit
- Periodically review accounts in AWS IAM, GCP IAM, Azure AD
- Detect accounts not linked to HR records
- API Credential Cleanup
- Scan and revoke lingering tokens tied to ex-users
- Rotate service account credentials if needed
- SaaS Access & Admin Role Cleanup
- Remove admin rights from Zoom, M365, Notion, CRM tools
- Use SSPM / CASB to monitor all accounts post-termination
- Retention & Archival Policy
- Ensure former user’s data is archived, encrypted, or deleted per policy
π§° Tools You Can Use
- π§© Offboarding Automation: Okta Workflows, BetterCloud, Torii
- π Cloud IAM Audit: AWS IAM Access Analyzer, Azure Entitlement Mgmt
- π οΈ CASB/SSPM: DoControl, AppOmni, Netskope
- β DevOps Access Scanning: GitHub Token Audit, GitLeaks
π§ͺ Maturity Model
| Maturity Level | Characteristics |
|---|---|
| π« Level 0 | Manual offboarding, no audit |
| β οΈ Level 1 | Ad-hoc deactivation, inconsistent logs |
| π Level 2 | Semi-automated, checklist-based revocation |
| π§ Level 3 | Centralized directory & SSO enforcement |
| 𧬠Level 4 | Continuous validation, auto-revocation, alerts |
π Free Download
π Departed User Cloud Access Tracker β Excel/PDF
A 2-in-1 template to track offboarding across cloud, SaaS, DevOps, and user identity sources.
π Tomorrow’s Post:
Day 23 β Control #22: Cloud Workloads with Public IPs β When Internal Becomes Internet-Facing
Employee Offboarding Checklist, Cloud Access Audit, Former Employee Data Breach, SaaS Offboarding Workflow, Cloud Identity Governance, Ghost Access Risk, Deprovisioning Cloud Accounts, IAM Security Best Practices, API Token Cleanup, Cloud Account Termination Audit