INC-2026-03-16: Investigation

Investigation

Identify Affected Devices

# List all Strongline devices and their current identity groups
netapi ise -f json endpoints | jq -r '.[] | select(.description // "" | test("strongline"; "i")) | [.mac, .identityGroup, .description] | @tsv' | column -t

# Or search by endpoint profile if assigned
netapi ise -f json endpoints | jq -r '.[] | select(.profileId // "" | test("strongline"; "i")) | [.mac, .identityGroup] | @tsv'

Verify Expected Identity Group

# List all identity groups to find the correct one
netapi ise -f json identity-groups | jq -r '.[] | [.name, .id] | @tsv' | column -t

# Search for Strongline-related group
netapi ise -f json identity-groups | jq '.[] | select(.name | test("strongline"; "i"))'

Check Current VLAN Authorization Rules

# View authorization policies (may need GUI for full context)
netapi ise policy-sets

# Check if identity group is referenced in authorization rules
# GUI: Policy > Policy Sets > [Policy Set] > Authorization Policy

Root Cause Analysis

To be completed after remediation

  • Why were 8 devices not included in the original CSV import?

  • Is there a process gap for new Strongline gateway deployments?

  • Should there be automated identity group assignment based on MAC OUI or profile?