Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› How should security teams build a credible manual…
Cyber Security

How should security teams build a credible manual cost baseline before automating repeatable identity or access work?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 2, 2026 Domain: Cyber Security

Start with touch time, not elapsed time, for repeatable tickets. Multiply mean time to resolve by the fully burdened hourly rate and monthly ticket volume, using a trailing 12 month average to smooth spikes. That produces a defensible baseline for manual effort. The point is to quantify current spend on routine work before asking for automation budget.

How to size the manual effort you are trying to remove

The useful baseline is the cost of doing the same work by hand under normal operating conditions, not the cost of occasional escalations or exceptions. For repeatable identity and access tasks, that means measuring the human touch time per ticket, then multiplying it by the monthly volume and a fully burdened hourly rate. A trailing 12 month average is usually the cleanest way to avoid a distorted estimate.

Keep the unit of measure consistent. If one request takes 12 minutes of analyst effort but sits in a queue for two days, the queue time is operationally important, yet it is not the labour cost you are trying to baseline. The baseline should describe the routine cost of execution, so that later automation savings can be compared against a credible manual benchmark.

For teams managing identity operations, the same logic applies whether the work is access provisioning, entitlement changes, recertification follow-up, or common joiner-mover-leaver tasks. A credible baseline should be built from the work category that is genuinely repeatable, not from the hardest cases that require investigation or approval routing.

Which inputs make the baseline defensible

Three inputs matter most: average handling time, a realistic labour rate, and stable ticket volume. Average handling time should include the analyst actions that consume effort, such as reviewing the request, validating context, updating the system, and documenting the outcome. The labour rate should reflect the true cost to the organisation, not just salary. Monthly ticket volume should come from a period long enough to smooth seasonal peaks and one-off change events.

IAM and IGA Basics is a useful reference when the work being measured spans access requests, provisioning, entitlement reviews, and lifecycle governance. That matters because baseline errors often come from mixing different access operations into one bucket, which hides where the time is actually spent.

Where the work sits in cloud identity platforms or managed identities, the same cost logic still holds: measure the human effort around the request, approval, exception handling, and closure, not the background system processing. That separation keeps the baseline anchored in labour consumption rather than tool activity.

Security Budget and Investment Planning Guide supports the budgeting side of the argument, because a manual baseline becomes the starting point for spend allocation, investment prioritisation, and later return-on-investment discussion. The more clearly you can show current operating cost, the easier it is to defend automation as cost reallocation rather than speculative spending.

Where teams go wrong when estimating automation savings

Many teams overstate the baseline by using elapsed time, by counting rework twice, or by assuming every ticket is identical. That produces a number that looks large but does not survive scrutiny. The better approach is to separate steady-state repeatable work from exception handling, and to document any assumptions that affect the result.

Configuration Drift and Baseline Enforcement Guide is relevant because baselines only remain credible when the underlying process is stable enough to measure. If the workflow changes every month, the savings model becomes a moving target and the case for automation is harder to defend.

It also helps to exclude benefits that automation may create later, such as fewer errors, faster compliance evidence, or better user experience, unless you can measure them separately. Those are real advantages, but they should not be baked into the manual cost baseline itself. The baseline should answer one question only: what does this repeatable work cost today?

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareRepeatable identity work is easier to baseline when the process is standardised and stable.
Recommendation — Standardise the workflow before estimating automation savings so the manual baseline stays comparable over time.
NIST CSF 2.0GV.OC-01 — Organizational ContextA cost baseline supports investment decisions by defining the current operating context and work volume.
Recommendation — Define the current-state identity workload before asking for automation funding.
ISO/IEC 27001:2022A.5.9 — Inventory of information and other associated assetsIdentity and access work is easier to cost when the underlying service, request and entitlement inventory is known.
Recommendation — Inventory the repeatable identity work items you intend to measure before building the cost baseline.

Practitioner Guidance

What to verify: Verify that your sample includes only repeatable tickets with comparable handling steps. If the queue contains exceptions, approvals, or investigation-heavy cases, isolate them before calculating the average.

Decision rule: If the process can be described as a standard, repeatable workflow with consistent analyst touch time, use it in the baseline. If the work varies materially by case, split it into separate cost buckets before you automate anything.

What to measure: Measure touch time, ticket count, and fully burdened labour cost together. A baseline that omits any one of those three inputs is usually too weak to support a funding request.

Practitioner takeaway: The most credible automation business case starts with a conservative manual cost baseline, because overestimated savings are easier to challenge than a well-evidenced current-state effort model.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org