InfraServiceCategoryDetailsResponse

InfraServiceCategoryDetailsResponse
Infrastructure Service Category Details Response

Comprehensive information for the specified infrastructure service category, including per-service security policy paths, flow count statistics, and leaked workload data. Use this response to assess the current protection state of a category before deciding which rules to create via POST /intelligence/monitoring/infra/proposed-rules, POST /intelligence/monitoring/infra/ids-proposed-rules, or POST /intelligence/monitoring/infra/publish-config.

JSON Example 
{
    "infra_service_category": {
        "display_name": "DHCP",
        "_create_user": "system",
        "_create_time": 1781024535030,
        "_last_modified_user": "system",
        "_last_modified_time": 1781024535030,
        "_revision": 0,
        "id": "23745f49-fbb0-44ad-9d92-410f6370f36d",
        "site_ids": [],
        "nsx_service_paths": [],
        "infra_groups": [
            {
                "id": "84019131-36a0-4d7d-838f-8ba441cc3f23",
                "display_name": "SSP_Infra_DHCP_Group",
                "path": "/infra/domains/default/groups/d12503fa-5abf-38cc-8f30-c434e5f3785f",
                "nsx_realization_id": "2ad736b6-f24f-4a7c-a4a1-98e91eb0a2b5",
                "exists": true
            }
        ],
        "last_publish_job_status": {
            "job_id": "de075cb7-872f-4a32-927c-18de94389542",
            "status": "COMPLETED",
            "service_id": "",
            "service_category_id": "23745f49-fbb0-44ad-9d92-410f6370f36d",
            "created_time": 1781041197659,
            "updated_time": 1781041199556,
            "completed_time": 1781041199556,
            "results": [
                {
                    "action_type": "HIERARCHY_IDS_RULE_CREATE",
                    "action_status": "SUCCESS",
                    "action_index": 0,
                    "status_message": "IDS rule publish completed successfully"
                }
            ]
        },
        "aggregated_port_protocols": [],
        "is_custom": false
    },
    "detected_new_servers": 1,
    "flows_for_new_servers": 3,
    "all_unique_flows": 18,
    "flows_for_leaked_workloads": 6
}
MonitoringTimeParameters
time_selection
Optional

The resolved time window used for the analysis.

InfraServiceCategory
infra_service_category
Optional

Infrastructure service category resource representing a standard infrastructure service category (e.g., DNS, AD, LDAP)

integer
detected_new_servers
Optional

Count of servers newly discovered communicating with this category during the time_selection window that are not yet members of a published infrastructure asset group. A non-zero value indicates ungrouped workloads that may need to be added to a group via POST /intelligence/monitoring/infra/publish-config with action type GROUP_PUBLISH.

integer
flows_for_new_servers
Optional

Count of unique traffic flows involving newly detected, ungrouped servers across all services in this category during the time_selection window. Use this to gauge the risk surface of unprotected workloads - a high value suggests significant unprotected traffic.

integer
all_unique_flows
Optional

Total count of unique traffic flows for all services in this category during the time_selection window, across both grouped and ungrouped servers. Use to assess overall traffic volume for the category.

integer
flows_for_leaked_workloads
Optional

Approximate count of unique traffic flows where the workload side of the flow has an UNCOVERED infrastructure classification (not protected by a published infrastructure rule for this category). The workload is on the opposite side of the flow from the infra service endpoint: for server-side services it is the flow source; for client-side services it is the flow destination. Broadcast services are excluded from this aggregate.

Important: A null value means one of the following conditions applies:

  • site_id was not specified on the request, OR
  • This category has no published infrastructure rules (no traffic, lockdown, or IDS rules). In these cases the API does not run leak aggregation. Do not interpret null as zero leaks.
Returned By