Why we count hops, not settings

Engineer walking two colleagues through a magenta path on a wall graph

A list of 12,406 grants tells you little. Every line looks like every other line, and none of them says what it connects to.

We built Wardline around a shorter question: how many steps does it take to get from here to something that matters? That number is a hop count, and people understand it without a glossary.

What a hop is

A hop is one move an identity can make on its own. Each one is a real permission that already exists in your account.

  • A user or a build job assuming a role.
  • A role trusting another account.
  • A role reading a key that opens something else.
  • A key or role reading a data store.

Three hops to customer records is a sentence a whole team can act on.

Why it changes the order

A severe setting on a test bucket with nothing in it can wait. A dull setting three hops from customer records cannot. Rank by what a path reaches, and most of the argument about what comes first goes away.

About the author

Mara co-founded Wardline after six years of answering the same audit question by hand. She still reads the first map of most new customers. Fictional author, demo content.

Related cloud notes