List Network boundaries
/unified/cloud-infrastructure/network_boundaries
Query Parameters
Refer Specifying query parameters in Truto APIs
Show Truto-specific parameters
The ID of the integrated account to use for the request.
62f44730-dd91-461e-bd6a-aedd9e0ad79dThe format of the response.
unifiedreturns the response with unified mappings applied.rawreturns the unprocessed, raw response from the remote API.normalizedapplies the unified mappings and returns the data in a normalized format.streamreturns the response as a stream, which is ideal for transmitting large datasets, files, or binary data. Using streaming mode helps to efficiently handle large payloads or real-time data flows without requiring the entire data to be buffered in memory.debugreturns the final unified result alongside raw remote fetch information. The response is an envelope containingresult(identical to unified mode output) anddebug(withrequestUrl,requestOptions,data,responseHeaders, and for list operations:nextCursor,isLooping,isEmptyResult,resultCount). When the upstream body exceeds 1 MiB,datais replaced by{ truto_truncated: true, truto_max_bytes, truto_excerpt }.debugisnullfor static responses or whentruto_skip_api_call=true.
Defaults to unified.
unifiedunifiedrawnormalizedstreamdebug
By default the result attribute is an array of objects. This parameter allows you to specify a field in each result objects to use as key, which transforms the result array into an object with the array items keyed by the field. This is useful for when you want to use the result as a lookup table.
idIgnores the limit query parameter.
Excludes the remote_data attribute from the response.
Array of fields to exclude from the response.
truto_exclude_fields[]=id&truto_exclude_fields[]=nameQuery parameters to pass to the underlying API without any transformations. Refer this guide to see how to structure the query parameters.
remote_query[foo]=barResponse Body
Present only when truto_response_format=debug. Contains raw fetch details: requestUrl, requestOptions, data, responseHeaders, nextCursor, isLooping, isEmptyResult, resultCount. data is the parsed upstream body; when its JSON form exceeds 1 MiB it is replaced by { truto_truncated: true, truto_max_bytes, truto_excerpt }, where truto_excerpt is the leading bytes of that body. The same applies to a string requestOptions.body. null for static responses or when truto_skip_api_call=true.
The cursor to use for the next page of results. Pass this value as next_cursor in the query parameter in the next request to get the next page of results.
List of Network boundaries
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.
1 supported
The provider's own identifier for the network.
1 supported
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.
1 supported
Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.
1 supported
Whether this is the provider's automatically created default network. Default networks are commonly permissive and are assessed separately.
1 supported
The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.
1 supported
Which cloud this object was read from.
awsazuregcp
1 supported
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.
1 supported
Whether the network is regional or genuinely global.
regionalglobal
1 supported
Firewall rule sets attached at the boundary level.
1 supported
Whether a boundary-wide public-access block overrides the routing. A boundary can hold an internet gateway route and still be unreachable because of this setting, so it is read before has_route_to_internet is reported as a finding.
1 supported
The address ranges the network covers.
1 supported
How long the provider batches records before writing them. Carried under its honest name: it is a batching window, not a sampling fraction, and it is not substituted for flow_log_sampling_rate.
1 supported
What fraction of traffic is actually captured, where a provider samples. Matters as much as the enabled flag, since a very low rate is technically enabled and evidentially useless. AWS VPC Flow Logs have no sampling rate at all -- no field and no setting -- so on AWS this is null with not_supported_by_provider. Related honest caveat: AWS flow logs never capture DNS, instance metadata, DHCP or ARP traffic by design, and AWS documents non-deterministic record loss under capacity pressure.
1 supported
Whether traffic flow logging is on for this boundary. Flow logs attach at boundary, subnet or interface level and the provider returns them in one flat list keyed only by resource id, so matching on the subnet id alone gives false negatives for the very common single boundary-level flow log. Also gated on the log being ACTIVE and delivering successfully, since a flow log can exist and be silently failing delivery.
1 supported
Whether the boundary can reach the internet. Computed, and easy to get wrong: a subnet not explicitly associated with a route table is IMPLICITLY associated with the boundary's main table and the provider does not return the subnet id for implicit associations, so joining on explicit associations alone marks every default-configured subnet as having no internet route.
1 supported
What kind of internet path exists. A gateway giving inbound reachability is a different finding from an outbound-only NAT path, and the two are not collapsed.
noneinternet_gatewaynat_onlyipv6_egress_onlyunknown
1 supported
True where the provider's network has no location at all. When true, the envelope region carries the literal string 'global' rather than a guessed region.
1 supported
The network name.
1 supported
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.
1 supported
Raw data returned from the remote API call.
Subnets inside this boundary, as objects carrying subnet_ref, location, cidr, auto_assign_public_ip, flow_logs_enabled, attached_rule_set_refs and has_route_to_internet. Nested rather than a separate resource because a subnet is only meaningful inside its boundary.
1 supported
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.
1 supported
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'.
1 supported
truto unified cloud-infrastructure networkboundaries \
-a '<integrated_account_id>' \
-o jsonimport Truto from '@truto/truto-ts-sdk';
const truto = new Truto({
token: '<your_api_token>',
});
const result = await truto.unifiedApi.list(
'cloud-infrastructure',
'networkboundaries',
{ integrated_account_id: '<integrated_account_id>' }
);
console.log(result);import asyncio
from truto_python_sdk import TrutoApi
truto_api = TrutoApi(token="<your_api_token>")
async def main():
async for item in truto_api.unified_api.list(
"cloud-infrastructure",
"networkboundaries",
{"integrated_account_id": "<integrated_account_id>"}
):
print(item)
asyncio.run(main())curl -X GET 'https://api.truto.one/unified/cloud-infrastructure/network_boundaries?integrated_account_id=<integrated_account_id>' \
-H 'Authorization: Bearer <your_api_token>' \
-H 'Content-Type: application/json'const integratedAccountId = '<integrated_account_id>';
const response = await fetch(`https://api.truto.one/unified/cloud-infrastructure/network_boundaries?integrated_account_id=${integratedAccountId}`, {
method: 'GET',
headers: {
'Authorization': 'Bearer <your_api_token>',
'Content-Type': 'application/json',
},
});
const data = await response.json();
console.log(data);import requests
url = "https://api.truto.one/unified/cloud-infrastructure/network_boundaries"
headers = {
"Authorization": "Bearer <your_api_token>",
"Content-Type": "application/json",
}
params = {
"integrated_account_id": "<integrated_account_id>"
}
response = requests.get(url, headers=headers, params=params)
print(response.json())