List Object stores

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.

Where the store's data physically sits. A compliance answer in its own right.

The bucket or container name.

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 provider's own identifier for the store.

Whether access logging is on. On AWS an unlogged bucket returns an empty document rather than an error, read as false.

Whether an ACL grants access to a public group. Kept distinct from policy_grants_anyone because the two mechanisms fail independently.

Whether an ACL grants access to any authenticated account on the provider. Not anonymous -- requests must be signed -- but it means any account on earth, and it is kept distinguishable rather than folded into anonymous_access_allowed.

Whether the store is effectively reachable without credentials. Computed, not read: on AWS, BlockPublicAcls and BlockPublicPolicy are write-time guards that AWS documents as not affecting existing policies or ACLs, so only IgnorePublicAcls and RestrictPublicBuckets change effective read access. Computing exposure from the two block flags produces false clean results.

The per-flag effective block configuration after combining account-level and store-level settings, so the consumer can see which specific guard is missing rather than only the rolled-up boolean.

The provider's own algorithm string, verbatim.

Reference to the key, stored as the provider returned it -- which may be a key id, an ARN or an alias. Not canonicalised, because canonicalising needs a further key-service call that may be denied.

Who manages the encryption key. The real control on modern AWS is whether the key is customer-managed: default provider-side encryption is now applied to every bucket, so 'no default encryption' is an obsolete control.

Lifecycle rules as objects, carrying the provider's own rule id, status, prefix or filter and transition and expiry settings. An empty array means no rules are configured; null means they could not be read.

Minimum TLS version accepted. No bucket-level setting exists on AWS: the only mechanism is a per-action condition key inside the bucket policy, so a policy can require TLS 1.2 for writes and allow TLS 1.0 for reads and there is no honest bucket-wide scalar. Emitted as null with not_supported_by_provider rather than guessed.

Whether write-once retention is enabled on the store.

Whether the access POLICY grants access to anyone, reflecting the policy itself and not only an account-level toggle -- the two disagree often. Note that on AWS a cross-account role cannot read a bucket policy at all (405 regardless of IAM), so this falls back to the bucket policy status operation and any field that needs the policy body is marked permission_denied.

Whether public access is comprehensively blocked. On AWS this is true only when all four effective block-public-access flags are set, taking the most restrictive of the account-level and bucket-level configurations; a missing configuration counts as all-false, not as blocked.

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.

Whether any replication rule is configured and enabled.

Replication destinations as objects carrying the destination store reference, its region and the rule status. Load-bearing for the data residency check: a replica quietly created on another continent is a serious finding.

Whether the retention period itself cannot be shortened or removed. Not a real S3 field: the closest honest AWS mapping is a COMPLIANCE-mode default rule, which is a default for FUTURE objects rather than a statement about anything currently stored, and legal holds are per object version. Carried with that caveat in unreadable_fields.

Default retention period applied to objects, in days.

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

Whether object versioning is on. On AWS a never-enabled bucket returns an empty document with no status element at all, which is read as false rather than unknown.