HumanIdentities 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.

Whether the identity can currently sign in. Real and readable for Identity Center (UserStatus). For AWS IAM users no such field exists -- it is synthesized from 'no login profile and no active access keys' and flagged as derived.

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 identity.

Which identity store this row came from. Load-bearing on AWS, where IAM users and Identity Center users share no identifiers and answer different subsets of this resource's fields.

Whether this is a person, a service account or an external guest. Guests are counted differently against every standard.

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.

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 administrative roles or policies behind is_admin, as provider references.

When the identity was created.

The person's display name. Does not exist for AWS IAM users, which carry only a user name and a path; null there with a not_supported_by_provider entry.

Email address or user principal name -- the join key against the customer's staff directory. AWS IAM users have no email attribute anywhere in the API, so on that path this is null unless the customer happens to carry it as a tag.

Group references for this identity. Evidence that access is granted by role rather than one user at a time.

Whether the identity has interactive sign-in, as distinct from programmatic-only. On AWS this is the 404 from GetLoginProfile read as an answer rather than an error. An IAM-only concept: null on the Identity Center path.

Whether the identity holds long-lived credentials. An IAM-only concept on AWS; null on the Identity Center path.

Whether this identity holds administrative privilege. No provider exposes an admin flag; this is entirely inference from attached permissions and is flagged as derived.

Last interactive sign-in. Console sign-in only on AWS, recorded at five-minute granularity, with a documented multi-week gap in 2018 and no tracking before 2014-10-20. Not available through any API for AWS Identity Center. A programmatic-only user reports null forever and must never be surfaced as 'never signed in'.

Number of MFA devices registered to this identity.

The registered method types, because some standards now distinguish phishing-resistant methods. On AWS, ListMFADevices returns no device type: the type is inferred from the serial number shape and FIDO cannot be cleanly separated from TOTP, so entries are marked derived.

Whether THIS user has MFA registered. Per user, never per account -- 'the account has MFA enabled' is not an answer to 'does every user have MFA'. Not available at all for AWS Identity Center: no public API exposes it, and it is emitted as null with not_supported_by_provider rather than guessed.

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.

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'.