AccessGrants Object

When Truto actually read this object from the provider, in UTC ISO 8601 with the offset present. Not when the request was made and not a provider timestamp. Drives consumer staleness rules.

Stable reference for this grant. On AWS there is no single list operation for grants -- it is a join across principals and their attached and inline policies -- so this is composed from the principal and the attachment.

Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.

The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.

Who holds the grant.

What kind of principal holds it.

Which cloud this object was read from.

The provider's own unbroken identifier, passed through verbatim -- a full ARN, resource id or self-link. Never truncated, prefixed or normalised. This is the customer-facing key used to find the object in the console.

The name of what was granted, as the provider names it.

The provider reference for the role, policy or permission set granted.

The provider reference for the exact thing the grant applies to.

How far the grant reaches. A grant at organisation level is a much bigger deal than the same role on a single resource, and this distinction is commonly flattened away by unified models.

Whether the privilege is permanent or activated on request with an expiry. Time-limited privilege is materially better evidence and is credited separately.

When the grant expires. AWS has no expiry on IAM attachments or Identity Center assignments -- both are permanent until detached -- so on AWS this is null with not_supported_by_provider. Session duration bounds a credential, not a grant, and is deliberately not mapped here.

Whether the grant permits every action on every resource. Derived from the permission document, including the NotAction case: an Allow with NotAction is one of the broadest grants expressible and is not missed.

Whether this grant confers administrative privilege. Derived by parsing the permission document, and flagged as derived.

When this grant was last formally reviewed. AWS has no access-review or attestation concept at all; last_used_at is offered separately rather than substituted, because last-used is not a review.

When the granted access was last exercised. Offered as its own field, not as a stand-in for last_reviewed_at.

Where the object is. A compliance answer in its own right, not metadata. The literal string 'global' is emitted for genuinely global resources (for example IAM, or a GCP VPC network) rather than guessing a region. Never invented: where the provider does not return a location and none can be derived, the collector's queried region is used and that substitution is recorded in unreadable_fields.

Raw data returned from the remote API call.

The provider reference for the scope node.

Key-value pairs exactly as the customer set them: no case folding, no key or value normalisation, no merging of separate provider concepts. Present on every object because tags are the primary input for environment classification. An empty object means the object carries no tags; tags that could not be read are recorded in unreadable_fields instead.

Per-object list of the fields that could not be read, and why -- the brief section 8.4 answer, chosen over per-field sentinel values. Each entry is an object with 'field' (the property name on this resource), 'reason' (a reason code) and an optional human-readable 'detail'. Reason codes: not_supported_by_provider, not_configured, permission_denied, not_collected, collection_error, partially_collected. An empty array means every property on this object was read successfully. A property absent from this array and null in the payload means the provider genuinely returned no value, which is different from 'we could not look'.