[New Integration] Blue Coat ProxySG

[mjwolf]

Integration release checklist

This checklist is intended for integrations maintainers to ensure consistency when creating or updating a Package, Module or Dataset for an Integration.

All changes

• [ ] Change follows the contributing guidelines
• [ ] Supported versions of the monitoring target are documented
• [ ] Supported operating systems are documented (if applicable)
• [ ] Integration or System tests exist
• [ ] Documentation exists, useful guidelines to follow
• [ ] Fields follow ECS and naming conventions
• [ ] At least a manual test with ES / Kibana / Agent has been performed.
• [ ] Required Kibana version set to:

Notes

Supported log formats are described here.

The log field definitions are here.

[mjwolf]

Hi @jamiehynds, just an update on this. I'm still working on developing this integration. I have a ProxySG system running, and generating some admin messages, but so far I haven't been able to get it working completely properly as a functional proxy.

With the sample logs you've provided and the admin logs I can generate, I should be able to do most of the work to finish developing the integration. But I would like to get my ProxySG system fully working, so I can do some end-to-end testing before this is released.

Do you know anyone who could help me get ProxySG fully running and proxying data?

[jamiehynds]

Thanks for the update @mjwolf. Not sure who could help get the virtual appliance fully running - @LucaWintergerst maybe?

[LucaWintergerst]

I won't be of much help I'm afraid. I haven't done any work with virtual appliances in the past. If you provide more info or logs of what's not working as expected I'm happy to give it a try, but maybe someone can think of others that have more experience in this space?

[elasticmachine]

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)