( Expressions in this article are mine and does not reflect my employer's IBM point of view )
One of the key questions or rather the first question that I have heard when I meet people at trade shows/ conferences or other informal meeting with folks who are curious about the IBM products on the cloud is "SECURITY ".
ITM 6.2.3 ( IBM Tivoli Monitoring 6.2.3 ) is deployed on the IBM Cloud, and has the security measures as described in this blog are in place.
Firstly no one can access or login to the ITM Image as 'root', which means no one can login as 'su' or 'ssh' as root.
However a default user "idcuser" is created and ssh connections to this user has been enabled by default.
Services like FTP/ and telnet are disabled.
SSH has been configured to accept only key authentication instead of password authentication (giving it a greater level of security)
No SFTP is provided to the Tivoli Monitoring image.
No VNC is permitted - in other words - some one cannot start a VNC session to this Tivoli Monitoring Instance.
Firewalls: Two levels of security for the Tivoli Monitoring app is provided. One is the operating system level and other is at the application level.
In the IBM cloud instance VM that is hosting the Tivoli application - the guest VM is locked down by disabling the ports and only allowing the ports required for the application in a special file called " parameters" file.
At the outset - all the incoming and outcoming ports are disabled, and only related ports are enabled.
One of the key questions or rather the first question that I have heard when I meet people at trade shows/ conferences or other informal meeting with folks who are curious about the IBM products on the cloud is "SECURITY ".
ITM 6.2.3 ( IBM Tivoli Monitoring 6.2.3 ) is deployed on the IBM Cloud, and has the security measures as described in this blog are in place.
Firstly no one can access or login to the ITM Image as 'root', which means no one can login as 'su' or 'ssh' as root.
However a default user "idcuser" is created and ssh connections to this user has been enabled by default.
Services like FTP/ and telnet are disabled.
SSH has been configured to accept only key authentication instead of password authentication (giving it a greater level of security)
No SFTP is provided to the Tivoli Monitoring image.
No VNC is permitted - in other words - some one cannot start a VNC session to this Tivoli Monitoring Instance.
Firewalls: Two levels of security for the Tivoli Monitoring app is provided. One is the operating system level and other is at the application level.
In the IBM cloud instance VM that is hosting the Tivoli application - the guest VM is locked down by disabling the ports and only allowing the ports required for the application in a special file called " parameters" file.
At the outset - all the incoming and outcoming ports are disabled, and only related ports are enabled.
( e.g: these ports are enabled ) "22 80 443 2809 8880 9401 9403 9402 9060"
No comments:
Post a Comment