VulnerabilityFindings 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.
The resource carrying the vulnerability.
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 provider's own identifier for the finding.
When the vulnerability was first detected. Starts the remediation clock that several standards measure against, so a finding without it cannot be assessed and this is required rather than optional.
Whether a fix exists. Distinguishes 'the customer has not patched' from 'there is nothing to patch to', which produce different advice.
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.
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 provider's own type string for the affected resource.
Severity as the provider labelled it, verbatim.
Whether the finding is still open.
activesuppressedclosedunknown
The provider's own vulnerability identifier, verbatim. Kept separate from cve_id, because not every finding has a CVE.
The CVE identifier, where the vulnerability has one.
The CVSS base score.
Exploit prediction score, where the provider supplies one.
Whether a known exploit exists, where the provider reports it.
Where the vulnerable package was found on the resource, where the scanner reports it.
The version that resolves the vulnerability.
When the vulnerability was most recently seen.
The vulnerable package.
The installed version of the vulnerable package.
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.
The provider's remediation guidance.
Raw data returned from the remote API call.
Which scanning product produced this finding.
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 provider's own title for the vulnerability.
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'.