Manage Traffic Flows Using REST API
You can use the following properties to manage traffic flows using the REST API.
Note
You should ignore and not use any extra properties that are not described in this document, such as tbi
, tbo
, dbi
, and dbo
.
Property | Description | Type | Required | Possible Values |
---|---|---|---|---|
| The version of the flow summary schema. | Integer | Yes | 4 |
| Indicates the time (RFC3339) when the first flow in the summary was created, represented in UTC. Format: | String | Yes | |
| Sample duration for the flows in the summary. Default is approximately 600 seconds (10 minutes), depending on the VEN's ability to report traffic and PCE's current load. | Integer | Yes | |
| Direction of the first packet: in or out (I, O). | String | Yes | I, O |
| Source IP of the flows. | String | Yes | |
| Destination IP of the flows. | String | Yes | |
| Protocol number (0-255). | Integer | Yes | Minimum=0 Maximum=255 |
| The ICMP message type associated with the first flow in the summary. This value exists only if protocol is ICMP (1). NoteThis information is included in blocked flows for VEN versions lower than 19.1.0. It is included in all flows for VEN version 19.1.0 and later. Example: 3 for “Destination Unreachable.” | Integer | No | Minimum=0 Maximum=255 |
| The ICMP message code (subtype) associated with the first flow in the summary. This value exists only if protocol is ICMP (1). NoteThis information is included in blocked flows for VEN versions lower than 19.1.0. It is included in all flows for VEN version 19.1.0 and later. Example: 1 for “Destination host unreachable.” | Integer | No | Minimum=0 Maximum=255 |
| Destination port. This value exists only if protocol is not TCP (6) or UDP (17). | Integer | Yes | Minimum=0 Maximum=65535 |
| Policy decision value, which indicates if the flow was allowed, potentially blocked (but allowed), blocked, or unknown. Possible values:
NotePolicy decision is “unknown” in the following cases:
| Integer | Yes | Minimum=0 Maximum=3 |
| Count of the number of flows in the flow summary. | Integer | Yes | |
| Session state for the traffic flows in the flow summaries. Possible values:
| String | No | A, C, T, S, N |
| The program name is associated with the first flow of the summary. It is supported on inbound flows for Linux and Windows VEN and on outbound flows for only Windows VEN. NoteThis information might not be available on short-lived processes, which are Linux-specific. Currently, flows are aggregated, so this value might represent only the first process detected across all aggregated flows. If network communication is done by an OS component (or a driver), no process is associated with it. | String | No | |
| The username is associated with the first flow of the summary. It is supported on inbound flows for Linux and Windows VEN and on outbound flows for only Linux VEN. On Windows, it can include the username of the user account that initiated the connection. NoteThis information might not be available on short-lived processes. | String | No | |
| Service name associated with the first flow in the summary. It is supported only on inbound flows on Windows VEN. | String | No | |
| Hostname of the source workload that reported the flow. | String | No | |
| HREF of the source workload that reported the flow. | String | No | |
| Labels applied to the source workload. NoteThe | Object | No | |
| Hostname of the destination workload that reported the flow. | String | No | |
| HREF of the destination workload that reported the flow. | String | No | |
| Labels applied to the destination workload. NoteThe | Object | No | |
dst_vulns | Information about the vulnerabilities on the destination of the traffic flow with the specific port and protocol. Note
| Object | No | |
| Fully qualified domain name | String | No |
The following table describes the sub-properties for the dst_vulns
property:
Sub-property | Description | Type | Required |
---|---|---|---|
| The total number of existing vulnerabilities on the destination port and protocol. | Integer | No |
| The maximum of all the scores for the vulnerabilities on the destination port and protocol. | Number | No |
| The list of CVE-IDs associated with the vulnerabilities that have the maximum score. Up to 100 displayed . | Array | No |