Reading a trust policy in five minutes

Two engineers at a row of dark monitors showing network graphs, one pointing at a screen

Permissions say what a role can do. A trust policy says who can become that role, and it gets read far less often.

You can learn to read one in five minutes. Only a few lines matter, and the rest is punctuation.

Four things to look for

  1. The principal: who is allowed in, and is it a whole account?
  2. Any wildcard, anywhere in that line.
  3. The conditions, or the lack of them.
  4. Whether an external ID is required for a vendor.

Trusting a whole account means trusting everyone that account ever lets in.

Start with your vendors

Roles that outside companies can assume are the best place to begin. Read each one, confirm you still use the vendor, and remove the ones you do not. Ours is on that list too, and you can delete it in one step.

About the author

Hana leads identity research at Wardline and collects trust policies the way other people collect stamps. Fictional author, demo content.

Related cloud notes