This is just the same behavior as on any other Linux/Unix box with OpenSSH, as long as we are not talking about SMB appliances.
ssh_config is for the SSH client.
sshd_config is for the SSH server.
If you you not specify any ciphers in that file(s), the defaults apply.
See defaults/supported ciphers here:
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
When changing these on versions prior to R81.10, please take care of:
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
When running at least R80.40, a quite good hardening suggestion would be for example:
KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
MACs hmac-sha2-256,hmac-sha2-512,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com
HostKeyAlgorithms ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
Just before hitting the "reply" button, I saw you are on R80.30. Thats sad, because that means you are limited to the possibilities of the very old OpenSSH version CheckPoint uses before R80.40, as PhoneBoy said already. Please see sk165685 for supported ciphers. The list is very short, but you can use ctr and get rid of cbc by specifiying only the ctr ciphers in your Ciphers string:
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
Not sure about Kex, MAC and HostKeyAlgorithms support in R80.30. Its not documented on sk165685 and I do not have access to anything older that R80.40 at the moment to look up myself.