Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Cybersecurity & Risk 6 min read

Least privilege access control checklist for growing teams

A practical checklist for joiners, movers, leavers, admin rights, service accounts and access reviews, with the evidence to keep.

E
EncryptTechBD · 0 comments
Laptop with code on the screen
Photo: Marcin Milewski / StockSnap

Least privilege is the practice of giving every person, service and device only the access needed to do a defined job, for only as long as it is needed. It sounds obvious, but access is usually granted in a hurry and removed only when somebody remembers.

This checklist covers what matters in a typical Bangladeshi SME: shared admin accounts, several cloud systems, payment exports, a support inbox and a growing vendor list.

What least privilege actually requires

A permission is only correct when four things are right at the same time:

  • Identity: a named person or service, not a shared login.
  • Permission: the specific action on the specific resource, not the whole system.
  • Time: a start and an end, especially for projects, vendors and temporary cover.
  • Evidence: a record of who approved it and when it was last reviewed.

If one is missing, the control is decorative: a named account with permanent admin rights is not least privilege, and a shared account with an expiry is still shared.

Five rules before the checklist

  1. Default to no access. Access is requested, approved and recorded.
  2. One person, one account. Shared accounts are exceptions with an owner and an expiry date.
  3. Admin rights are separate from daily work and are time-bound wherever the tool allows it.
  4. Every permission has a business owner, not only a technical owner.
  5. Access is reviewed on a schedule and after every role change.

1. Inventory and ownership

  • List every system that holds money, customer records, student data, payroll or administrative control.
  • Record the business owner, technical owner and support route for each system.
  • Map roles to tasks. "Branch manager" is not a permission; "approve refunds up to the branch limit" is.
  • Find accounts that are not tied to a current employee, student or supplier record.

Owner: operations lead with IT. Evidence: system register, owner matrix and role catalogue.

2. Joiners

  • Use one access request containing the role, manager approval, start date and review date.
  • Create the account only after the person has signed the acceptable use policy.
  • Enrol multi-factor authentication before the first login, not after the first week.
  • Give the standard role first. Add extra permissions only with a written reason.

Owner: HR and IT. Evidence: approved request, policy acknowledgement and MFA status.

3. Movers

  • Trigger a review from the HR record or the manager, not from a chat message.
  • Compare the old and new role before changing anything, then remove access that is no longer needed.
  • Re-check admin rights, finance limits, export permissions and vendor portals.
  • Set a 30-day review for any access granted "for the transition".

Owner: hiring manager with IT. Evidence: before-and-after access list and approval.

4. Leavers

  • Disable the account on the last working day, or earlier if the exit is not amicable.
  • Revoke active sessions, refresh tokens and API keys, not only the password.
  • Recover laptops, phones, SIMs, hardware tokens and printed credential sheets.
  • Transfer mailbox, drive and application ownership to a named manager.

Owner: HR with IT and the line manager. Evidence: exit checklist, disable timestamp and token revocation record.

5. Privileged access

  • Give administrators a separate admin account that is not used for email or browsing.
  • Ban shared admin logins. If one exists, give it an owner, a vault and an expiry date.
  • Use just-in-time elevation for routine admin work, with a short session and a reason.
  • Require phishing-resistant authentication for admin accounts where the platform supports it.
  • Log admin activity, review it monthly and keep a break-glass procedure that is sealed, monitored and tested.

Owner: IT lead. Evidence: admin account list, elevation log and monthly review notes.

6. Application and data permissions

  • Define roles inside the application, not only at the network or hosting layer.
  • Check object-level access: a branch user should not see another branch's customers or orders.
  • Restrict bulk export, report downloads and "view all" screens to the people who need them.
  • Test with a real low-privilege account before go-live, not with the administrator account.

Owner: application owner. Evidence: role matrix and test results from a standard user account.

7. Service accounts and API keys

  • Record the purpose, owner, scope and expiry of every service account and key.
  • Disable interactive login for accounts that only run integrations.
  • Rotate credentials when a staff member leaves or a vendor contract ends.
  • Store secrets in a secret manager or vault, not in a spreadsheet, chat thread or source code.
  • Monitor usage and alert on new locations, unusual volumes or failed authentication spikes.

Owner: engineering or IT. Evidence: credential register, last rotation date and usage alert configuration.

8. Third parties

  • Create named accounts for vendor staff, never a shared vendor login.
  • Scope access to the support or maintenance task, with a start and end date.
  • Name an internal sponsor who approves and reviews the access.
  • Include offboarding and evidence obligations in the contract.

Owner: procurement or operations. Evidence: vendor access register, sponsor approval and offboarding clause.

Verification: test, do not assume

Run these samples every quarter and record the result:

  • Pick five recent leavers. Try to authenticate and check whether sessions or tokens remain active.
  • Pick five finance users. Confirm they cannot open administration screens or change payment details.
  • Review the twenty highest-risk permissions in each core system.
  • Check ten API keys for a named owner, scope and expiry date.
  • Attempt a customer data export using a support-level account.

Record the date, tester and result, and raise a ticket for every failure. An access review without a failed item is usually a review that did not look.

Common mistakes

  • Treating the role matrix as a one-time project instead of a living document.
  • Copying a colleague's permissions during onboarding.
  • Removing a password but leaving active sessions and API keys.
  • Leaving break-glass accounts unmonitored.
  • Reviewing access by reading a list instead of testing an account.

Metrics worth reporting

  • Number of privileged accounts per administrator.
  • Orphaned accounts as a share of total accounts.
  • Median time from exit to full revocation.
  • Percentage of systems with a completed quarterly review.
  • Standing admin rights replaced by time-bound elevation.

These numbers are more useful than a policy document because they show whether the process works when someone is busy, on leave or leaving.

A 90-day rollout

  1. Weeks 1-2: build the system register, owner matrix and role catalogue.
  2. Weeks 3-4: fix joiner and leaver handling, including token revocation.
  3. Weeks 5-6: separate admin accounts and remove shared admin logins.
  4. Weeks 7-8: register service accounts, API keys and vendor access.
  5. Weeks 9-10: run the verification samples and fix the failures.
  6. Weeks 11-12: set the quarterly review calendar and report the first metrics.

Where this fits

If you need help turning this checklist into an evidence-based review, start with Managed Technology & Cybersecurity. The pricing page explains scoping. For the wider risk picture, read what a cybersecurity risk assessment should cover.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes