Menu

#3 jumphost_post_command

1.11
closed
Andreas
None
2019-07-31
2015-08-27
Petri Niemi
No

Hi there,

We would love to have an ability to run post commands on jumphost for every file so that based on the response from the command we could skip the file. This would make possible to implement any kind of virus scan in DMZ.

There is many ways to do this.

Make post commands work perfectly in Jade4DMZ. For example [source|jumphost|target]_post_command and ability to drop execution (or move to quarantine or something) for every file based on response from command.

Make Jade4DMZ available via jobchain (needed helper methods available and good examples). This might be quite flexible approach to custom workflow of Jade4DMZ.

Simple jump_host_scan parameter.

Br,
Pete

Discussion

  • Andreas

    Andreas - 2015-09-16

    Hi Pete,

    thank you for this feature request: we (assume that we) basically understand this feature request. At the same time we would love to move this to a complete requirement following the mantra "don't tell me what you want, tell me what you need".

    We have knowledge of users who run multiple dmz-like network zones and who would like to increase the number of supported jump hosts, with each network zone using its individual virus scanner and optionally transacational behavior that is configurable for an individual network zone or all network zones.

    This would include a requirement for more comprehensible (i.e. parseable) logging to allow simplified log analysis, e.g. by splunk or similar tools. And this would include some more compliance requirements.

    Last but not least the file transfer history and JADE Background History Viewer should be capable to show the respective file, problem, network zone and subsequent action, e.g. quarantining, that occurred.

    To make a long story short: IMO this feature is not just about a jump_host_scan parameter, but about introducing better security and more compliance with standards, e.g. SOX. We therefore would like to discuss with you how your feature request fits into this picture. Please get in contact, we suggest to set-up a conf call that allows to discuss the scenario in more detail.

    Best regards
    Andreas

     
  • Petri Niemi

    Petri Niemi - 2015-10-07

    Thanks!!!

    Sorry that it took a while to get back in touch.

    As I say, I don't mind how. After all my use case is quite simple :)

    I'm always ready for more details converstaion.

    Br,
    Pete

     
  • Andreas

    Andreas - 2016-01-29
    • Milestone: 1.9 --> 1.11
     
  • Andreas

    Andreas - 2017-04-06
    • status: open --> closed
    • assigned_to: Andreas
     
  • Andreas

    Andreas - 2017-04-06

    Hi Pete,

    we announced availability of Maintenance Release 1.11.1.

    The requested feature is available with releases starting from 1.11.0.

    Can you please let us know if release 1.11.1 resolves the issue for you?

    Best regards
    Andreas

     

Log in to post a comment.

MongoDB Logo MongoDB