06-reference/research

iam usage before tightening service identities

2026-11-19·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
permissionsiamharness-safetysilent-failurepre-enforcement

Yes, all three clouds document "check usage before you tighten" for service identities - but only Google's replays real access against the proposed rule, and each one has a window or coverage hole a scheduled job can fall through

The question

Verbatim: "Does any major IAM vendor document a "check what was actually used before you tighten" workflow that covers non-interactive service identities, not just human users?"

Open follow-up #1 of [[2026-11-06-correct-rule-wrong-default-permission-detection]], which named AWS IAM last-accessed data, IAM Access Analyzer unused-access findings, GCP Policy Simulator and the Azure/Entra equivalents as candidates but had spent its caps and labeled all of them unverified. This is the verification pass.

What we already know (from the vault)

What the web says

Three vendor pages were fetched and read on 2026-11-19 (AWS, Google, Microsoft). Claims marked search-level come from search-result summaries of vendor doc pages that were not themselves fetched.

Candidate Covers service identities? Lookback Pre-enforcement or post-hoc Verification
AWS IAM last accessed information Yes: roles, by name Service level "at least 400 days"; action level from a per-service start date Evidence to read before a change; does not test a proposed policy Fetched
AWS IAM Access Analyzer unused access Yes: unused roles and unused permissions; service-linked roles excluded Configurable tracking period, 1 to 365 days Continuous findings; does not test a proposed policy Search-level
GCP Policy Simulator Principal-agnostic by mechanism (replays access logs); the overview page does not enumerate principal types 90 days True pre-enforcement: replays real access attempts against the proposed policy Fetched
GCP IAM recommender / service account insights Yes: docs use a service account as the worked example 90 days max; 30 or 60 selectable for project-level Recommendation from past usage Search-level
Entra Conditional Access for workload identities, report-only Partly: single-tenant service principals only; managed identities excluded None backward; observes sign-ins after the policy is saved Pre-enforcement, forward-looking staging Fetched

Convergences and contradictions

Synthesis for RDCO

The answer is yes, with a ranking. The four named candidates are all real and all cover non-human identities to some degree. Ranked by how close each is to a pre-enforcement control for the correct-rule-wrong-default failure: (1) GCP Policy Simulator, the only one that takes a proposed rule and replays actual recorded access against it; (2) AWS last-accessed data and Access Analyzer unused access, which document "review usage before you change permissions" explicitly and cover roles, but report evidence rather than testing a specific change; (3) Entra report-only for workload identities, which is forward staging for a narrow policy type and excludes managed identities and multitenant apps. Confidence is high on the fetched rows (AWS last-accessed, Policy Simulator, Entra) and medium on the two search-level rows.

The useful correction to RDCO's thinking is that staging comes in two designs and RDCO only wrote down the slow one. The parent brief's control (3) says: before a permission change, hold it for one full period of the longest-period affected job, then check mtimes. That is forward observation, the Entra design, and it is why a change touching a monthly job "cannot be judged for a month." Google's design is the alternative: do not wait, replay. Take the proposed rule and run it against the last N days of what the workloads actually did. For RDCO this is an inference, not something any vendor documents for agent harnesses, but it is the transferable part: the raw material for a replay is a record of each cron run's tool calls and paths, and the lookback has to be at least as long as the longest job period. Google picked 90 days; RDCO's longest standing periods are monthly (finance-pulse, acquisition-rescan), so roughly 35 to 45 days of retained run records would cover every current slug. Whether the cron runner retains enough per-run detail to replay against is not something this brief checked.

Every vendor documents the holes, and the holes line up with RDCO's failure. AWS: no data-plane actions at action level, so the tool knows a role used a service but not that it wrote. RDCO's freeze was a write failure with reads intact. AWS again: denied attempts count as usage, so a job already failing still looks "in use" - worth knowing as a trap in any homegrown replay that counts attempts rather than successes. Google: anything outside the window is silently absent and the tool "fails to report a loss of access." Entra: the identity types most used for unattended automation in Azure (managed identities) are outside the policy entirely. The pattern is that these tools are strongest on interactive, frequent, control-plane access and weakest on infrequent, scheduled, data-plane access, which is the profile of a nightly or monthly agent job. So the industry's best pre-enforcement control is real but would not have been sufficient alone, and the parent brief's post-hoc freshness manifest stays necessary rather than becoming redundant.

For the phData-facing side, this is a clean, citable three-cloud comparison for any client conversation about putting agents into production under least privilege: the tooling to right-size a service identity exists on all three clouds, it is usage-window-bound, and an agent that runs monthly or does mostly data-plane work is where it under-reports. That is a defensible, vendor-sourced caution rather than an opinion.

Why this is in the vault

It closes follow-up #1 of [[2026-11-06-correct-rule-wrong-default-permission-detection]] by converting four named-but-unverified candidates into verified or search-level rows, and it adds the backward-replay staging design as an alternative to the hold-for-one-period step that brief specified for RDCO's own permission changes.

Open follow-ups

Related

Sources

Web, primary, fetched 2026-11-19:

Web, search-summary level only, NOT fetched:

Vault: