WorkloadIdentities Object
Properties
The account, subscription or project the object belongs to. An object with no account cannot be attributed to an environment, so this is always present for objects that live inside an account.
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.
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 identifier for the workload identity.
Role, managed identity, service principal or service account.
rolemanaged_identityservice_principalservice_accountother
The identity name as the provider names it.
The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.
Which cloud this object was read from.
awsazuregcp
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.
Provider references for the permission definitions attached to this identity.
When the identity was created.
Federated access configuration, as objects carrying issuer, subject and audience. AWS has no federated-credential resource: these are assembled from the OIDC provider URL (stored without its https:// scheme, so both sides are normalised before joining), the provider ClientIDList cross-checked against the :aud condition key, and the :sub condition key. Where the ClientIDList and the trust policy disagree, the trust policy is what actually gates the assume.
Whether the machine identity holds long-lived keys -- a finding on its own. Structurally false for AWS IAM roles, which have no long-term credentials: that is a fact about the provider, not a data gap.
Whether a subject condition is present on each federated trust. Modelled as its own state rather than an empty subject list, because a role trusting an OIDC provider with NO subject condition can be assumed by any subject from that issuer -- for a GitHub Actions provider, any repository on GitHub. The finding is a missing key, which an empty list would hide.
Whether the identity can be assumed by a bare wildcard principal with no condition -- wide open. Derived.
How many inline permission documents are attached directly.
How many long-lived keys the identity holds. Always 0 for AWS IAM roles.
When the identity was last used. On AWS the tracking window is bounded at roughly 400 days, so absent does NOT mean unused and is reported as unknown rather than as dormant.
Where the identity was last used, where the provider exposes it.
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.
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.
The raw trust or assume-role policy document, so the consumer can re-derive external trust independently of Truto's parsing.
Every external account, tenant, domain or federated issuer permitted to assume this identity. Each entry is an object carrying the principal reference, its kind (account, service, federated, canonical_user) and whether a scoping condition is present. On AWS this is parsed out of the trust policy rather than supplied by an API: any account id that is neither the scanned account nor a member of the same organisation is an external trust.
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'.