A private cloud has been created on a company intranet. The maintenance of this cloud has been given to another company, which will be accessing the private cloud directly through a remote management

SCP (Secure Copy Protocol) is used for secure file transfer, not for establishing an interactive management session, and initiating it 'from a browser' to a remote server is not a typical or secure management workflow in this context.

While SSH is correct, the direction 'SSH from an intermediary server in the DMZ' implies the intermediary server initiates the connection outwards, which is typically not how external companies connect *into* a network for management.

SSH (Secure Shell) is the appropriate protocol for secure remote access and management, establishing an encrypted channel to the intermediary server in the DMZ. The external company would initiate an SSH connection *to* this server to begin managing the private cloud securely.

HTTP is not a secure protocol for remote management and sending it 'to a browser in the private cloud' doesn't describe the secure remote management access from an external entity.