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.
The insurer's questionnaire asks for every administrator with privileged access, and your team is building that list by hand from directory exports. That is the situation to solve first, and it is a governance problem before it is a software problem. Identity access management software reduces risk only when a process already exists: define privileged access, name one owner, inventory the raw exports, and re-approve every privileged account each quarter. A console that sits on top of an undefined process will only automate the wrong answer.
What does the insurer's privileged-access question actually require?
Read the questionnaire line by line before anyone opens a directory export. The question about privileged access is usually asking three things: who holds administrative rights, why they hold them, and who checked that recently. Your carrier's form sets the exact wording and the evidence it expects, so the form is the specification. Do not guess at it from memory of last year's renewal.
The likely problem is not a missing product. It is a missing owner and a missing list. If the team is assembling the answer by hand, nobody has been formally responsible for the list, so nobody has been keeping it current. That is the finding to fix this week, because it shapes every step after it.
This week, do three things. Find the privileged-access section of the form and copy its exact questions into a working document. Ask your leadership who will sign the answer. Then pull a first set of raw directory exports, so you know how much work the inventory will be. Most of the time goes into reconciling accounts that nobody can explain, not into the export itself. Expect that, and budget for it.
Renewal season is when many carriers ask for this evidence, which is why this lands now. An insurer's question on privileged access is a governance question. A vendor dashboard does not answer it on its own, because a dashboard shows what the system is configured to do, not whether anyone decided it should.
What must be governed before buying identity software?
Three things have to exist before any console is configured. They are a written definition of privileged access for your environment, one accountable owner who decides who may approve privileged grants, and a written approval rule. A product inherits whatever it is configured against, so these come first.
Start with the definition. Privileged access is more than the directory administrator group. It includes cloud tenant administrators and server local administrators. Backup and firewall administrators belong on it too, and so does anyone who can manage the tools that manage identities. If someone can change who gets access, they hold privileged access, whatever their title says. Write the list down in one place and get it agreed by IT leadership.
Next, name the owner before the purchase, not after. That person decides who can approve privileged grants, and the answer should be written before anyone touches a configuration screen. The owner does not need to be an identity specialist. They need the authority to say no and the time to review the list. A mid-market team without identity staff can still hold this role by making it one named person's responsibility, backed by a monthly check on admin membership.
Total 360 Security's Enterprise Security Risk Management program includes identity control among the domains it runs, so the owner question is one the firm helps answer as part of a managed program rather than a one-time configuration project. With or without outside help, write the definition and name the owner on paper first.
Define privileged access in your environment
Write a short definition that lists each system where administrative rights live. Go through the directory, the cloud tenant and each server class, then check the backup system. The firewall and any management console come next. Add a line for anything that can manage identities. Keep it to one page. If a system is missing from the definition, it is missing from the inventory, so review the list with the people who run each system.
Name one owner, even without identity staff
The owner signs off on privileged grants and owns the quarterly review. Give the role a backup name too, so the process survives a holiday or a resignation. Put both names in the governance document with their authority stated plainly. An owner who has no authority to refuse a request is only a formality.
The governance layer described here is what an ESRM engagement sets up, and you can read how that approach is structured at Enterprise Security Risk Management. Either way, write the definition and name the owner before you touch the tool.
How should privileged accounts be inventoried?
Build the inventory from raw exports, not from group names. Group names describe intent; membership describes reality. A group called "Server Admins" can contain people who left two years ago, and a service account can hold rights that appear in no group you were looking at.
- Export membership from every place admin rights live. Pull the members of directory admin groups and of each server's local administrators. Add cloud tenant roles and SaaS admin roles as separate exports. Save each export with the date it was taken.
- Make every member a line item. Put each account on its own row, even when the same person appears in several systems. Duplicates show you the true reach of one person.
- Give each entry three fields. A named human, or a named owner for a non-human account; the reason the account holds the right; and the date that reason was last justified. A row without a justification shows an auditor that nobody is reviewing it.
- Mark each entry's status. Active, expired, under review, or removed. Anything with no owner or no justification goes to review, not into the approved column.
- Include third-party and vendor administrator accounts. Local exposure shows why. Star-Telegram reporting on Fort Worth and Crowley ISD describes exposure that arrived through a third-party software provider, and the lesson for any organization is that exposure can come through a vendor's system rather than its own. Vendor administrator accounts that reach your environment belong on the list.
Pull raw exports, not group names
Group membership reports are the fastest source, but check them against the systems themselves. Where a system has no reliable export, record that as a gap and assign someone to close it. An honest list with stated gaps is more credible than a tidy one that hides them.
Service accounts and API keys count
When a service account or API key holds administrative rights, it is privileged. These are the entries most inventories miss, because they often have no named owner, no documented purpose and no record of last use. Give each one an owner, a purpose and a last-used date, and if you cannot find an owner, that is a finding to report, not a reason to leave it off.
Who approves access changes, and how is each one recorded?
Separate three roles on every elevation: the requester, the approver and the person who implements the change. The approver must be someone other than the requester. For a two-person IT team, that can mean the owner approves and the second technician implements, and the person who asked does neither.
- Open a ticket for every elevation. The ticket states who is requesting, what rights, on which system, and why.
- The owner approves or refuses in the ticket. The approval is recorded before any change is made.
- A second person implements the change. The implementer records the ticket reference in the change itself.
- Set an expiry date by default. Temporary rights expire automatically or on a stated date. A grant with no end date is a grant nobody will remember to remove.
- Re-check at expiry. If the right is still needed, it goes through the same approval again.
This pattern rests on two principles auditors test against: least privilege and separation of duties. Least privilege means people hold only the rights their job needs. Separation of duties means the person who asks for a right cannot also approve and grant it. The ticket is the record that proves both.
How do you prove deprovisioning actually happened?
Deprovisioning fails most often at two moments: when someone leaves, and when someone changes role and keeps old rights. Those are the moments to check. The evidence is the disable timestamp for the account, the group removals, and the ticket that triggered them. Check those records against the HR list of leavers and movers, not against memory.
Ask HR for the leaver and mover list each month, and compare it to the privileged inventory. Any name that left or changed role and still holds an admin right is an exception. Record it, fix it, and note the date.
When a departed admin account is still active
If you find a departed employee's privileged account still active, or admin credentials shared among several people, treat it as a security event rather than a clean-up task. Check the logs for any use after the departure date before you change anything, so you do not destroy the evidence you need. Involve your incident response contact early. Disable the account once that is done, rotate any shared credentials, and document each step with its time. Plainly stated: the account should have been removed on the day the person left, and the record should show when it was.
What should the quarterly review keep as evidence?
Each quarter, every privileged account is re-approved or removed by its owner. The review is not finished until the evidence is saved. Keep the dated export, the reviewer's name and sign-off, the decisions made, and the exceptions with remediation dates. An auditor or insurer will sample from that record, so it has to exist in a form you can hand over.
Argue for honesty over polish. An honest list with a short exceptions section and dated fixes holds up under sampling far better than a perfect list you cannot back up. When the first sampled account turns out to have no owner, a clean-looking list collapses. A list that already names its exceptions does not.
Automation helps only on clean data. Identity governance tools automate reviews and approvals, but if the inventory is not complete, a tool imports the mess and makes it look official. Finish the manual inventory first, then decide whether a tool is worth the cost.
What to retain each quarter
- The dated export of privileged membership from every system in scope
- The owner's review decisions, with the reviewer's name and sign-off date
- Removals, with the ticket that caused each one
- Exceptions, each with a named owner and a remediation date
- The leaver and mover reconciliation against HR's list
Break-glass accounts get tested too
Document each break-glass account, control its credentials, and test it on a schedule. Teams that skip this discover during an incident that the account is locked or the password is unknown. A quarterly test that logs in, confirms access and records the result is a short task that prevents a serious failure.
What should you do before the renewal deadline?
This month, make three decisions. Name the program owner in writing. Schedule a leadership review of privileged access against the insurer's form, so the people who sign the renewal know what the answer is. Then book a 30-minute risk discussion to scope identity governance before the renewal date. Doing this now gives the team time to build the inventory rather than assemble it under deadline.
CISA's Critical Infrastructure Security and Resilience Month began on November 2, 2026, which is a natural point to put identity and recovery dependencies on the leadership agenda. The review is worth doing whether or not your company is critical infrastructure, because the questions it forces are the same ones an insurer asks.
You can book the 30-minute risk discussion at the consultation page, or call 817-677-0515. Bring the insurer's privileged-access questions and your current directory exports, and the discussion will start from what you actually have.
Frequently asked questions
Do service accounts and API keys count as privileged accounts?
Yes, when they hold administrative rights over a directory, cloud tenant, server or management tool. Give each non-human account a named owner, a documented purpose and a record of last use. These are the entries most inventories miss, so check them deliberately.
How often should privileged access be reviewed?
Each privileged account should be re-approved or removed by its owner every quarter. Between reviews, run a short monthly check on admin group membership. Keep the dated export, the reviewer's name, the sign-off and the exceptions with remediation dates.
What is the difference between identity governance and identity management?
Identity management creates, changes and removes accounts and access. Identity governance decides who should hold which access, who approved it, and whether it was reviewed. Software can automate both, but governance needs an owner and a record even without a tool.
Can a small IT team run identity governance without dedicated staff?
Yes. Assign one named program owner, run a monthly check on admin membership, and keep a versioned, access-controlled register. A well-controlled spreadsheet is more useful than an identity suite that nobody owns.
What evidence does a cyber insurer want for privileged access?
The form your carrier sends sets what it asks for, so read it first. In general it looks for the current list of privileged accounts with owners and reasons, approval and expiry records, deprovisioning evidence, and a dated quarterly review that discloses exceptions honestly.
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
7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article6 min read
IoT Security Solutions: How to Inventory and Segment Devices
Connected cameras and building controllers need an inventory, network separation, unique credentials and a named responder. This is the order to work in and who owns each step.
Read article