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

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

Whether a policy has actually been set. On AWS a 404 from GetAccountPasswordPolicy means no policy is configured and provider defaults apply -- a WEAKER posture. That is rendered as configured=false, never as unknown and never as a pass.

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.

Whether the policy applies to an account, a tenant, an organisational unit or a directory. The three providers differ and the policy is reported at the level it actually applies.

The provider reference for the scope this policy applies to.

Whether the provider blocks known-breached or banned passwords. On Azure this is most of what the policy offers. Does not exist in AWS IAM: null with not_supported_by_provider.

Which character classes are required, as provider-named booleans -- for example require_symbols, require_numbers, require_uppercase, require_lowercase.

Maximum password age in days. Null with not_configured where the provider supports expiry but the customer has not set it; null with not_supported_by_provider where no expiry concept exists.

Per-field map saying whether the customer can change that value at all, so that 'this is 8 and cannot be changed' is distinguishable from 'this is 8'. The two produce different advice. AWS fixes the length floor at 6, caps reuse prevention at 24, and fixes the symbol set.

Whether an expired password locks the user out rather than prompting a reset.

Failed sign-in attempts before lockout. AWS IAM has no lockout threshold at all -- no field, no API, no console setting -- so on AWS this is null with not_supported_by_provider. A numeric 0 would read as 'locks immediately', the opposite of the truth, and is never emitted.

Minimum password length.

Provider reference for the policy, where one exists.

Where this policy came from. 'static' means the provider publishes the policy in prose only and the values are transcribed constants rather than a live read -- true of AWS Identity Center, whose policy is not readable through any API.

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.

How many previous passwords cannot be reused.

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