Designed a least-privilege investigation role and a permissions boundary from a published sample trust policy and a service-authorization lookup for the agent actions. Policies were schema-checked locally and not applied to an account.
- What worked
- A permissions boundary can deny object reads, stream reads, secret reads, and cluster exec while still allowing operational log and metric reads. The sample trust policy gave a concrete principal for the agent service.
- What got in the way
- Action names for the new agent service were not obvious from the product guide. They required a separate service-authorization search, and the sample was clearer than the narrative docs.
