Gujarat has a dense mix of manufacturers, chemical and textile companies, trading houses and a growing software scene, and almost all of them share one quiet security weakness: the link between the people list and the access list. Somebody leaves, a contractor finishes, a supervisor changes plants, and the badge, the ERP login and the shared mailbox carry on as if nothing happened. This checklist helps you audit that link in an afternoon. It draws on the PeopleOps discipline, in which the hiring, moving and leaving of staff are handled as controlled events.
Before you begin: what you are testing
The Ops Atlas, whose PeopleOps reference page underlies this checklist, splits responsibility in a helpful way. The people function owns the trigger and the data: the hire date, the move, the end date. The identity or IT team owns the accounts. The Atlas says the gap between the two must be measured, and that is precisely what this audit does. You will need three exports: the current staff list, the list of active accounts for your main systems, and the list of physical access cards or keys.
Part A: the lists agree
- Match every active account to a current worker. Any account without a matching person is an orphan. Record each one with the system name and the last sign-in date.
- Match every leaver of the last ninety days to a closed account. A person recorded as gone in the staff list but live elsewhere is the finding the Atlas wants to turn into an alert rather than a line in a report.
- Check the join key. If your tools match people by email address, note it. The Atlas advises a permanent worker identifier, since addresses change after a marriage or a rehire and break the link.
- Count duplicates. The same person under two numbers or two spellings is a sign that the record is not trusted.
Part B: timing
- For each leaver, compare the last working time with the time the first account closed. The Atlas gives an example policy of one hour and a sample goal that all but one leaver in a hundred meet it. Your own limit may differ; what matters is that you have a written one.
- List any leaver who exceeded it, and by how much. The sheet’s sample audit found two of four leavers within the limit, with one account that never closed and another that stayed open for twenty-six hours.
- Check whether departures are entered ahead of time with an effective moment. A future-dated entry lets access end exactly when the person walks out.
- Find out how the systems learn about a departure. If they pull a file overnight, the delay is built in. The Atlas lists scheduled pulls and fragile file transfers among the usual weaknesses.
Part C: movers
- List everyone who changed plant, department or role in the last six months.
- For each, confirm that a review of access happened. The Atlas cites the personnel-security controls published by NIST, which expect a review on transfer, and calls movers the forgotten event.
- Count how many hold access that their current job cannot justify. This number is usually uncomfortable and always useful.
Part D: the awkward cases
- Rehires. Was the old account switched back on with its previous rights? The Atlas wants the person’s identity brought back clean, without any earlier entitlements.
- No-shows. If accounts were created in advance, are there any for people who never started?
- Leave periods. Is anyone on extended leave whose separation was processed while they were away, leaving a gap?
- Contractors. Does the staff list even include them? The sheet notes that contractor accounts are a common orphan source when the arrangement runs through procurement.
- Outside the single sign-in. Shared passwords, test accounts, scripts and bots that nobody owns.
Part E: physical and equipment
- Match cards and keys to current workers.
- Check that equipment returned by leavers is logged. The Atlas cites a documented case in which laptops are expected back within a few weeks, which shows that this is a tracked step and not an afterthought.
- Confirm that gate and plant-floor access is closed on the last day, not at the next payroll run.
A worked pass through one department
Take a packaging unit with eighty people. Pull the staff list, the plant ERP user list and the card register. Suppose the ERP shows ninety-one active users. Eleven extra accounts is the first headline. Sorting them, you might find four leavers, three contractors who finished a project, two shared accounts for the weighbridge and two test logins left by a consultant. Each category has its own fix: close, close with a contractor tab in the staff list, assign an owner or rotate the password, and delete. The exercise takes ninety minutes and produces a short, factual list that any manager can act on.
Note that none of the findings required a clever tool. They needed three exports and a willingness to compare them, which is exactly the habit the Atlas keeps returning to.
Scoring your audit
Keep it simple. Give each part one of three marks: clean, minor findings or major findings. Then choose the top three findings by risk, give every item an accountable name and a due date, then repeat the audit a month on. A lengthy write-up is not the aim. The Atlas favours daily reconciliation over periodic documents, so use the afternoon exercise to design a small automated check that runs every morning.
What not to conclude
An audit like this is an operational control, not a legal conclusion. Its legal tables carry dates and are marked for periodic re-checking, and the Atlas is careful to say they are not counsel. It also separates analytics from surveillance, so keep the focus on accounts and processes, not on watching individuals. Finally, remember its candid note that PeopleOps is largely HR renamed; the benefit comes from the controls, not the label.
Reading for the next step
If you want to build the automation that makes this check continuous, the site’s guide to growing a career in DevOps one step at a time is a decent starting point for the skills involved. And if the audit leads to a work trip, the visitor article on sketching out a maiden trip across Gujarat offers a useful template for doing a task in a sensible order.
Run the checklist once, fix the top three items, and schedule it again. This article is general information, not legal or employment advice.