Under Review
over 7 years ago

Post Migration Custom Command - Security Flaw

Is it possible to add a feature to the custom command post migration set-up that would restrict users from changing the variables defined in the custom command.  We restrict our end users from using the UNIX account that allows the ability to SSH.  If we define a custom command the user can put any command in the "command with parameters" window and compromise our server after selecting the run button during the post migration process.  We would like the ability to define the command but only allow the end user to execute the custom post migration as-is, preventing the user from adding or changing these variables.

This is a great feature but completely useless for us because of this security concern.

tim.rogers
Parents
  • over 7 years ago

    I raised this same concern....  

    I opened a case with Quest and they responded with the solution below to protect Post migration commands from being changed during execution.

    There are two security rights that user should not have. They are located under Maintenance-General:

    - Post Migration Command Edit

    - Pre Migration Command Edit

    Let me know if this works for you.

    Regards.

    Tom Shaw

Comment
  • over 7 years ago

    I raised this same concern....  

    I opened a case with Quest and they responded with the solution below to protect Post migration commands from being changed during execution.

    There are two security rights that user should not have. They are located under Maintenance-General:

    - Post Migration Command Edit

    - Pre Migration Command Edit

    Let me know if this works for you.

    Regards.

    Tom Shaw

Children
No Data