Cloud Identity: Who Gets Access and How to Remove It
Cloud identity decides who can sign in to your cloud systems and what they can reach. This guide covers removing orphaned accounts, expiring contractor access and reviewing privileged accounts.
Cloud identity controls who can sign in to your cloud systems and what they can access. Keeping it under control takes an accountable executive and a removal rule tied to business events, not just an annual review. Most security firms advise on this gap, but Total 360 Security runs the program day to day.
A former project manager still listed as an administrator is a governance failure, not a reason to buy another tool. Start by identifying who owns each account and why it still exists.
What Counts as an Orphaned Account in a Cloud Environment?
An orphaned account has no current business reason to exist. It might belong to a former employee, a contractor whose engagement ended, or a retired application. Ask who requested the account and what purpose it serves today. If nobody can answer, treat it as orphaned until its purpose is confirmed.
Who Should Own Cloud Identity Governance?
Stale accounts persist when nobody is responsible for noticing them. HR usually hears about departures, and IT usually handles access requests, but neither one owns the decision. One executive must own the decision about who can reach your finance and operations data, usually the CFO or operations head in a mid-market organization.
That responsibility extends beyond IT. Losing access to a building system or a critical vendor portal can interrupt operations. If no internal executive can hold the security leadership role, our virtual CISO services provide cybersecurity program ownership. We operate security programs and report directly to the board; your managed provider can carry out the approved technical changes.
Write the Removal Rule Before You Touch the List
Write down which business event changes access, who reports it, and when IT must act. Have HR and the admin team approve the rule. For a termination, specify when HR must notify the administrator and when access must stop, rather than leaving either decision to a ticket queue.
Treat disabling and deleting as two separate decisions. Blocking sign-in generally preserves the account and its associated records; deleting it can start a platform-specific retention clock. Leadership and HR should approve retention windows for each account class, with legal requirements considered.
Disable at the trigger
Block access when the agreed business event occurs, not at the next quarterly review. Confirm the block and address active sessions where the platform requires it. Record who acted and when, so a closed ticket is not your only evidence.
Delete after the retention window
Delete only after the approved retention window ends and dependencies are resolved. Check mailbox and file ownership before removal, including any legal hold. A shorter account list is not a reason to destroy records your organization still needs.
How Do You Handle Contractor Accounts With No End Date?
Every contractor or vendor account should have an expiry date matched to the statement of work. Make that date mandatory on the request form before cleaning up existing accounts. Otherwise, the same gap keeps producing accounts with indefinite access.
- Start by exporting every external account. Include the creation date and last sign-in for each one.
- Match each to a contract. Verify the written end date. Ongoing activity does not prove the engagement is still authorized.
- Give each account an expiry date. Match it to the approved contract term. Disable expired access unless an authorized extension is documented.
- Make sure each account has a sponsor. Require the internal manager to justify continued access by a stated deadline.
- Update the request form so it asks for both. Reject requests that lack an end date or a named internal sponsor.
For active contractors, check scope as well as dates. Access to one project folder should not become access to every customer file.
How Do You Run a First Access Review?
Start with an export, not a software purchase. The time required depends on your account inventory and how quickly sponsors answer. Set a deadline that allows dependency checks rather than promising a one-week cleanup before you know what is connected.
Export and match each account to a sponsor
Export every user with its last sign-in date and the groups it belongs to. Assign a sponsor who can explain the business need. Record a keep-or-remove decision for each account, then resolve unsponsored accounts under the removal rule.
Last sign-in is a clue, not a verdict. A quiet account might support seasonal work or emergency access. Check its purpose before blocking it.
Check dependencies before you disable
Identify applications and scheduled jobs that authenticate with the account. Ask IT whether previous removals interrupted workflows. For legitimate service dependencies, schedule changes outside busy operating periods and prepare a rollback; do not use scheduling convenience to delay an urgent security response.
How Do You Review Privileged and Service Accounts Without Breaking Workflows?
Administrative access can change the environment. Service access can keep it running. Review these separately from ordinary employee accounts because their consequences and removal procedures differ.
Privileged accounts
Use a reviewer other than the administrator who manages the accounts. Require a second approver for privileged grants and named individual logins so actions can be attributed. Keep emergency break-glass access separate from daily accounts, and test it.
Service accounts
HR cannot offboard an identity that never appeared in its records. Maintain a separate service-account inventory naming each account’s owner and how its credential gets rotated. Before removing an account tied to a retired application, verify that no active integration still uses it.
What Evidence Should the Review Leave Behind?
A completed review needs a record of decisions, not just a cleaner directory. Store that record where the next program owner can find it after staff changes.
| Field | What to record | Why it matters |
|---|---|---|
| Account | Identifier and account type | Defines what was reviewed |
| Reviewer | Reviewer’s name; independent of the administrator for privileged accounts | Records accountability |
| Sponsor | Person confirming the business need | Identifies the business owner |
| Decision | Keep, change or remove | Records the outcome |
| Reason | Business justification for the decision | Explains why access remains or ends |
| Action and date | Completed change, date and person responsible | Distinguishes approval from execution |
| Exception and expiry | Approved exception and end date | Prevents indefinite exceptions |
Auditors and insurers can request evidence of access controls. This file supports your answers, but check the actual questionnaire rather than assuming every insurer requires identical fields.
How Often Should Cloud Access Be Reviewed?
Use quarterly reviews for privileged and external accounts as a working baseline. Review ordinary users at least twice a year. These are operating recommendations, not a substitute for stricter contractual or regulatory requirements.
| Review type | Scope | Frequency |
|---|---|---|
| Higher-risk review | Privileged and external accounts; service-account inventory and dependencies | Quarterly baseline, adjusted to risk |
| Standard review | Ordinary user accounts | At least twice a year |
| Event-driven check | Accounts affected by departure, role change or contract end | At each trigger |
For Texas organizations, late November is a practical checkpoint before holiday absences and year-end audit work. Confirm who can approve access changes while executives are away. Include escalation authority in winter disruption planning so an unavailable approver does not stall containment.
What Do You Do With an Account You Cannot Explain?
An unexplained administrative account or suspicious sign-in warrants a possible-incident response, not routine deletion. Preserve logs and contact your incident response lead before removing evidence. Your Incident Response Plan should identify who authorizes containment while the investigation establishes what happened.
Frequently asked questions
How often should we review who has access to our cloud systems?
Use quarterly reviews for privileged and external accounts, with ordinary-user reviews at least twice a year. Also check access at every departure, role change and contract end. Follow stricter requirements where your contracts or regulations impose them.
What is the difference between disabling an account and deleting it?
Disabling blocks sign-in while generally retaining the account and associated data. Deletion removes the identity and can trigger data removal under the platform’s retention rules. Confirm those rules and resolve ownership or legal holds before deleting.
Can our managed IT provider own the access review?
Your provider can coordinate exports and implement approved changes. An accountable executive should own the business decisions, and privileged access needs a reviewer other than its administrator. Put those responsibilities in writing so a completed technical task does not stand in for business approval.
How does an access review help with a cyber-insurance renewal or a vendor security assessment?
A dated review file documents who checked access and whether approved changes happened. It supports questionnaire answers without forcing your team to reconstruct decisions under deadline. It does not replace the specific evidence an insurer or customer requests.
If your organization lacks a security program owner, book a 30-minute Risk Discussion to define the leadership role and review scope, or call 817-677-0515.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
6 min read
Key Man Risk in Security: Who Decides When the Leader Is Away
Key man risk is more than a finance term. Learn which security decisions only one leader can make, and how to hand them to a tested backup before leave starts.
Read article7 min read
SB 553 Workplace Violence Plans: What California Employers Need
SB 553 requires California employers to run a written workplace violence prevention plan, train staff and keep a violent incident log. This guide covers what the plan must include, who is exempt and which records to keep.
Read article10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article