-
Notifications
You must be signed in to change notification settings - Fork 519
Closed
Labels
Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Security Service Integrations team [elastic/security-service-integrations]Team:Sit-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Crest developers on the Security Integrations team [elastic/sit-crest-contractors]enhancementNew feature or requestNew feature or request
Description
Description
-
When looking at the Netskope integration configuration options, it's unclear that the three object storage options map to Netskope's Log Streaming mode, and that TCP input maps to Log Shipper.
We should edit the TCP input title to "Collect logs from Netskope using Log Shipper", and the 3 object storage titles to "Collect logs from Netskope using Log Streaming via {vendor}"
This would ensure consistency across the two products and prevent user confusion during setup.
- Log Shipper is now considered legacy by Netskope. There are no known plans to deprecate it, but Log Streaming is now the preferred approach. Therefore, we should:
a. Re-order the options in the UI so that Log Streaming options appears first in the list
b. Indicate Log Shipper is legacy, ie "Collect Netskope logs via Log Shipper (Legacy)"
Metadata
Metadata
Assignees
Labels
Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Security Service Integrations team [elastic/security-service-integrations]Team:Sit-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Crest developers on the Security Integrations team [elastic/sit-crest-contractors]enhancementNew feature or requestNew feature or request