PolicyComplianceStates 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.
The evaluation outcome. insufficient_data is kept distinct and never folded into compliant. Note one provider returns insufficient_data but will not accept it as a query filter, so it can only be observed in results.
compliantnon_compliantinsufficient_datanot_applicableunknown
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.
The rule or policy this state belongs to.
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.
The account, node or resource scope this state was evaluated for.
How many resources satisfy the rule.
Whether the counts are a provider-imposed ceiling rather than exact. Mapped through rather than dropped, because the cap bites on exactly the large rules that matter most and publishing a ceiling as a count is a wrong number.
When the rule was last evaluated. Read from a real provider evaluation timestamp -- Truto's own fetch time is NEVER substituted here, because that is precisely the staleness lie the brief warns about. The AWS compliance call carries no timestamp at all and is paired with a separate evaluation-status call.
The last evaluation that actually succeeded, as distinct from the last invocation.
How many resources violate the rule. See count_capped: the provider may return a ceiling rather than a true count.
The resources violating the rule. Opt-in, because on AWS the resource list cannot be aggregated and costs one paged call per rule per account per region.
The rule name as the provider names 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.
Whether non_compliant_resource_refs was actually gathered. False means an empty list reflects a collection choice, not a clean result.
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'.