Skip to content
CIEM Tools

A CIEM requirements checklist: 15 requirements, each with a test you can run in a trial and the criterion it maps to

A CIEM buyer's checklist of 15 requirements, each with the reason it matters, a test to run during a trial and the one of the seven index criteria it maps to. The criteria and weights, fixed before scoring, are removal 25, safety 20, class of risk 15, drift 15, coverage 10, native controls 10 and audit 5.

See the ranking ยท All guides

Fifteen requirements and the test for each

Run each test on a non-production account with realistic roles. The last column uses the seven criteria of the method, so a result can be carried into the scoring sheet in the CIEM RFP template.

RequirementWhyHow to test in a trialCriterion
Ends in a removal, not only a findingThe product that only reports leaves the work to your teamPick 10 unused grants from the product's own report and ask it to remove them; time the whole pathRemoves access, not only reports it
Names what it will change before it changes itRemoving a permission in production can break a workloadRequest a change and ask for the list of identities and actions affected before approvalSafe to enforce
Simulates against your real policiesA simulation on sample data proves nothing about your accountSubmit a change you know would break something; confirm the tool flags itSafe to enforce
Rollback or restore pathA block with no way back pushes engineers to bypass the controlRemove access, then restore it; record the minutes taken and the stepsSafe to enforce
One change covers a class of pathsPermission-by-permission clean-up never finishesAsk for a single boundary or guardrail that blocks a risk across all accounts; count the paths it removesOne change, a class of risk
Applies at organization levelAccount-by-account policy leaves new accounts openCreate a new test account and see whether the control applies on day oneOne change, a class of risk
Checks changes before productionAccess removed today can be granted again tomorrowSubmit an infrastructure-as-code change that adds a broad grant; confirm it is flaggedStays fixed
Exceptions handled in your own toolsExceptions in a separate queue get lostRequest an exception from your ticketing or chat tool; confirm it reaches the productStays fixed
Proof that a fix heldAn audit asks for evidence over months, not a screenshotAsk for a report of one fixed finding and its state 30 days laterStays fixed
Covers identity, network and AI workloads togetherExcess is often reachable only through a network pathPick a workload with an AI service role; confirm it appears with its network exposureIdentity, network and AI access together
Machine identities includedService accounts and workload roles outnumber peopleAsk for the count of non-human identities in a sample account and check it against your own listIdentity, network and AI access together
Uses the cloud's own policy typesNothing new in the request path means nothing new to failAsk which native mechanism enforces each change (service control policy, role, deny policy) and read one of them in your consoleUses the cloud's own controls
No proxy or broker in the request pathA broker is an outage riskDisable the product's connection during the trial; confirm access still worksUses the cloud's own controls
Mapped controls and continuous evidenceAudits ask for the control, the date and the ownerExport evidence for one named framework and check it against your auditor's listEvidence for auditors
Entitlement count with a stated unitCounts differ by unit (policy, role, assignment)Ask for the unit and the total on one sample account; compare with your own countIdentity, network and AI access together

How the requirements map to the weights

Removal carries 25 of 100, safe enforcement 20, one change for a class of risk 15, staying fixed 15, identity, network and AI coverage 10, native controls 10 and evidence for auditors 5. The weights were fixed on 10 Nov 2026 before any vendor was scored. Six of the 15 requirements above map to the top three criteria, which is where most of the weight lies. Per-criterion scores for all 14 platforms are in the criteria comparison.

If your own priorities differ, change the weights before you open any vendor response, not after. The situation pages such as AWS-heavy organizations show how published weights change the order.

What a trial cannot show

A two-week trial shows whether a product finds excess and whether its removal works on the accounts you gave it. It rarely shows behavior at several hundred accounts, how often the vendor's connector breaks after a cloud API change, or the support response at month nine. Ask for two references of similar size and ask each what broke.

Ask for pricing early. The CIEM pricing page lists which vendors publish a price and which ask for a quote, as read on 16 Nov 2026. Where the answer is a quote, ask for the unit before the number.

Sources

  1. Wiz Academy, how to choose a CIEM vendor, read 16 Nov 2026
  2. Microsoft Learn, CIEM in Defender for Cloud, read 16 Nov 2026
  3. AWS documentation, IAM Access Analyzer, read 16 Nov 2026
  4. Google Cloud, IAM role recommendations overview, read 16 Nov 2026

Last reviewed 16 Nov 2026.