InlineInfraServiceCategorySummary1

InlineInfraServiceCategorySummary1
InlineInfraServiceCategorySummary1
JSON Example
{
    "detected_new_servers": 0,
    "total_services": 0,
    "leaked_assets_workload_count": 0,
    "excluded_servers_count": 0,
    "rules_status": "string"
}
integer
detected_new_servers
Required  

Count of servers newly observed communicating with this category during the time_selection window that are not yet members of a published infrastructure asset group. Use POST /intelligence/monitoring/infra/service-categories/{service-category-id}/discovered-servers to see the individual servers.

integer
total_services
Required  

Total number of port/protocol service entries in this category.

integer
leaked_assets_workload_count
Optional

Approximate count of distinct workload assets with UNCOVERED infrastructure flow classification for flows matching this category's server-side and client-side port/protocols in the time window. A flow is considered UNCOVERED if it is not protected by infrastructure firewall rules published via SSP infra security segmentation planning or infrastructure monitoring.

null or omitted when:

  • This category has no published infrastructure rules (traffic, lockdown, and IDS counts are all zero). When no rules are published, the API does not query leak counts. Do not interpret a missing value as confirmation of zero leaks.
integer
excluded_servers_count
Optional

Count of servers that have been manually suppressed from discovery via POST /intelligence/monitoring/infra/service-categories/{service-category-id}/exclusions for this service category at the requested site. Use GET /intelligence/monitoring/infra/service-categories/{service-category-id}/exclusions to see which specific servers are excluded.

rules_status
Required   Read-Only  

High-level indicator of published rule coverage for this category. NO_RULES if no rules are published but some are required. SOME_MISSING_RULES if at least one rule is published but expected traffic, lockdown, or IDS counts are not fully met. ALL_RULES_PUBLISHED when published counts meet expected totals.

Enumeration: NO_RULES, SOME_MISSING_RULES, ALL_RULES_PUBLISHED