[Cisco ISE] Pipeline failing for console logs

[qcorporation]

Proposed commit message

Implemented a TACACS accounting pipeline hardening fix for cisco_ise.log to prevent non-IP Remote-Address values (console, async, EEM) from causing ingest failures, while still mapping valid IP literals to destination.ip.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

• Closes [cisco.ise]: Pipeline failing for console logs #17972

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

Pinging @elastic/integration-experience (Team:Integration-Experience)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: efa5be8

History

• 💚 Build #40890 succeeded a0e4ce7
• 💚 Build #40794 succeeded d96f577
• 💚 Build #40759 succeeded ee1b632
• 💚 Build #40747 succeeded ed15fbc
• 💚 Build #40732 succeeded e935050

cc @qcorporation

[elastic-vault-github-plugin-prod]

Package cisco_ise - 1.32.3 containing this change is available at https://epr.elastic.co/package/cisco_ise/1.32.3/