Removal requested
Disable the scheduling account.
Independent consulting · Henry Rheault
I help teams examine their controls, assemble evidence, and work through the gaps.
Take a closer lookAccess review Worked example
Two records. A few hours apart.
Follow what each one tells us.
IT has been asked to remove access to the scheduling system.
Disable the scheduling account.
The ticket gives me a starting point. I still need the account history.
“This tells me when IT received the request. I’d look for a separate record of the change.”
The application records the account being disabled later that day.
Disable the scheduling account.
The account history records the change.
“I can compare the two timestamps. To assess the timing, I’d also check when access was meant to end.”
I’d take these questions back to the people who own the process.
Compare the approved departure time and the organization’s access-removal policy with the system record.
With HR & the control ownerCheck the application’s session and token behavior, and look for any access that required a separate action.
With the application ownerReconcile the offboarding list with the person’s assigned accounts. Record gaps, owners, and the next check.
With IT & the reviewer“I’d keep the finding open until the evidence supports a conclusion within the agreed scope.”
Illustrative records for one account. Both timestamps use UTC.
A first review
I start with one control, a release path, or a small set of AWS resources. We agree what to examine, who owns it, and which decision the review needs to support.
What I checked, where it came from, and what it establishes.
Gaps tied to named resources and the agreed scope.
Prioritized fixes, someone responsible, and a way to check again.
Workflow handoffs Illustrative scenario
Operations imports the week’s orders. Finance uses the total for billing. A manager uses the export for staffing.
Only the original operator knows that an amendment replaces the first row. Here’s what that handoff note changes.
| Order | Entry | Units |
|---|---|---|
| 4817 | Original | 12 |
| 4817 | Amendment | 9 |
I walk through one real cycle with its owner, trace the corrections and downstream users, then ask a backup to run it from the notes. We reconcile both outputs against an agreed baseline.
You receive a dependency map, named owners and backups, a tested runbook, and an ordered list of changes. I record every step that still needed the original owner.
The same rehearsal can support succession or operational preparation for a sale. I document what the next operator can run, where access is managed, and who owns the unfinished work.
About Henry
I work in cloud security and software delivery. I’ve spoken at Aaron’s, taught CCSP for Simplilearn, and wrote and presented a Blackhack talk on Git, DevSecOps, and infrastructure as code.
My credentials include CISA, CISSP, CCSP, and PMP.
Start a conversation
In general terms, tell me what changed, who relies on it, and when you need an answer.