-
Couldn't load subscription status.
- Fork 505
[cisco_ftd] Add support for Security Group Tag and Endpoint Group fields #15652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[cisco_ftd] Add support for Security Group Tag and Endpoint Group fields #15652
Conversation
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
log |
892.06 | 524.93 | -367.13 (-41.16%) | 💔 |
To see the full report comment with /test benchmark fullreport
| @@ -0,0 +1,3 @@ | |||
| 2025-09-01T12:00:00Z firepower : %FTD-6-430003: EventPriority: Low, DeviceUUID: d697c8ca-9fe4-43e6-aeb5-33e277e5ffea, InstanceID: 11, FirstPacketSecond: 2025-09-01T12:35:00Z, ConnectionID: 39416, AccessControlRuleAction: Trust, SrcIP: 10.0.100.30, DstIP: 10.0.1.20, SrcPort: 56799, DstPort: 53, Protocol: udp, IngressInterface: inside, EgressInterface: outside, SourceSecurityGroup: SGT_TEST_GROUP, SourceSecurityGroupTag: 2003, SourceSecurityGroupType: Session Directory, DestinationIP_DynamicAttribute: APIC_EPG_TEST_GROUP, IngressVRF: Global, EgressVRF: Global, Endpoint Profile: Workstation:Microsoft-Workstation:Windows11-Workstation, ACPolicy: ACP-Access, AccessControlRuleName: Test-Rule-1, Prefilter Policy: Default Prefilter Policy, User: testuser, Client: DNS, ApplicationProtocol: DNS, ConnectionDuration: 0, InitiatorPackets: 1, ResponderPackets: 1, InitiatorBytes: 31, ResponderBytes: 238, NAPPolicy: Balanced Security and Connectivity | |||
| 2025-09-01T14:00:00Z firepower : %FTD-6-430002: EventPriority: Low, DeviceUUID: d697c8ca-9fe4-43e6-aeb5-33e277e5ffea, InstanceID: 4, FirstPacketSecond: 2025-09-01T14:00:03Z, ConnectionID: 36584, AccessControlRuleAction: Block, SrcIP: 10.0.100.30, DstIP: 10.0.1.20, SrcPort: 56799, DstPort: 22, Protocol: tcp, IngressInterface: inside, EgressInterface: outside, SourceSecurityGroup: 2005, SourceSecurityGroupTag: 2005, DestinationSecurityGroup: 9, DestinationSecurityGroupTag: 9, SourceSecurityGroupType: Session Directory, DestinationSecurityGroupType: SXP, IngressVRF: Global, EgressVRF: Global, Endpoint Profile: Invalid ID, ACPolicy: ACP-Management, AccessControlRuleName: Default Deny, Prefilter Policy: Management Prefilter Policy, InitiatorPackets: 1, ResponderPackets: 0, InitiatorBytes: 70, ResponderBytes: 0, NAPPolicy: Balanced Security and Connectivity | |||
|
|
|||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can remove this empty log line
packages/cisco_ftd/changelog.yml
Outdated
| @@ -1,4 +1,9 @@ | |||
| # newer versions go on top | |||
| - version: "3.10.3" | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be 3.11.0 since we are adding support for new types in this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
implemented
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
- Bump version to 3.11.0 (enhancement requires minor version bump) - Update changelog link to PR elastic#15652 - Remove pr.md file (not needed in integration packages) - Remove empty lines from test-sgt.log - Anonymize test DeviceUUID values Addresses review comments from @P1llus and @bhapas
0d61098 to
3833710
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix the manifest entry with the new version for CI to go green.. Else LGTM
💔 Build Failed
Failed CI StepsHistory
|
Summary
This PR adds support for parsing 6 Security Group Tag (SGT) and Endpoint Group (EPG) fields from Cisco FTD connection event syslog messages (message IDs 430002 and 430003).
Related Issue
Fixes #15204
Problem
The Cisco FTD integration was not parsing SGT/EGT-related fields from connection event messages. These fields were present in the
event.originalfield but were not being extracted into structured, queryable fields, making it difficult to search and analyze security group information in Elastic.Solution
Added parsing support for the following 6 fields:
SourceSecurityGroupcisco.ftd.security_event.source_security_groupSourceSecurityGroupTagcisco.ftd.security_event.source_security_group_tagSourceSecurityGroupTypecisco.ftd.security_event.source_security_group_typeDestinationIP_DynamicAttributecisco.ftd.security_event.destination_ip_dynamic_attributeDestinationSecurityGroupcisco.ftd.security_event.destination_security_groupDestinationSecurityGroupTagcisco.ftd.security_event.destination_security_group_tagChanges Made
1. Ingest Pipeline (default.yml)
security_event_listarray to ensure fields are placed incisco.ftd.security_eventgroup (consistent with other connection event fields)["430002", "430003"]2. Field Definitions (fields.yml)
cisco.ftd.security_eventgroupkeywordto support both string and numeric values3. Testing
"SGT_TEST_GROUP") and numeric values (e.g.,"2005")Implementation Notes
Fields are placed in
cisco.ftd.security_eventrather than the legacycisco.ftd.securityfield for consistency and maintainability.All new fields use
keywordtype to handle both string and numeric values.Testing Performed
References
Checklist