You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to support network.direction setting in our rsa2elk modules, we can leverage the new add_network_direction processor in any of our modules that use "perimeter"-based network models (i.e. firewalls, etc.). Currently however, all rsa2elk modules have the same module configuration. Since certain modules, such as AV modules, are "host"-based, we should have a way of making each module have the ability to leverage distinct configuration.
This issue is to track adding support for distinct configuration in the generated modules and also leveraging the new procssor for network.direction enrichment in the "perimeter"-based modules.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the enhancement:
In order to support
network.direction
setting in our rsa2elk modules, we can leverage the newadd_network_direction
processor in any of our modules that use "perimeter"-based network models (i.e. firewalls, etc.). Currently however, all rsa2elk modules have the same module configuration. Since certain modules, such as AV modules, are "host"-based, we should have a way of making each module have the ability to leverage distinct configuration.This issue is to track adding support for distinct configuration in the generated modules and also leveraging the new procssor for
network.direction
enrichment in the "perimeter"-based modules.The text was updated successfully, but these errors were encountered: