On this weblog put up, you’ll discover ways to document SSH classes on a Crimson Hat Enterprise Linux (RHEL) VSI in a non-public VPC community utilizing in-built packages. The VPC personal community is provisioned by means of Terraform and the RHEL packages are put in utilizing Ansible automation. Moreover, you’ll discover ways to arrange a extremely accessible bastion host.
What’s session recording and why is it required?
A bastion host and a leap server are each safety mechanisms utilized in community and server environments to manage and improve safety when connecting to distant programs. They serve related functions however have some variations of their implementation and use instances. The bastion host is positioned in entrance of the personal community to take SSH requests from public visitors and move the request to the downstream machine. Bastion host and leap servers are susceptible to intrusion as a result of they’re uncovered to public visitors.
Session recording helps an administrator of a system to audit person SSH classes and ensure they adjust to regulatory necessities. Within the occasion of a safety breach, the administrator will need to audit and analyze the person classes. That is vital for a security-sensitive system.
What’s a non-public VPC community?
A virtual private cloud is totally personal if there isn’t a public ingress or outgress community visitors. In easy technical phrases, it’s personal if there are not any public gateways on the subnets (personal subnets) and no floating IPs on the Digital Server Cases (VSIs).
How do I connect with the personal VPC community?
Shopper-to-site VPN for VPC is without doubt one of the two VPN choices accessible on IBM Cloud, and it permits customers to connect with IBM Cloud sources by means of safe, encrypted connections.
The client-to-site VPN is extremely accessible, with two VPN servers which are created in two totally different availability zones in the identical area. The bastions are extremely accessible as properly.
Stipulations
Provision the personal VPC community utilizing Terraform
- After you have the IBM Cloud Secrets Manager secret with the certificates, launch your terminal and set the next Terraform variables:
export TF_VAR_ibmcloud_api_key=<IBM_CLOUD_API_KEY>
export TF_VAR_secrets_manager_certificate_crn=<SECRET_CRN>git clone https://github.com/VidyasagarMSC/private-vpc-network
cd terraform- Run the Terraform instructions to provision the VPC sources (e.g., subnets, bastion hosts (VSIs), VPN, and many others.):
terraform init
terraform plan
terraform applyHook up with client-to-site VPN
- As soon as the VPC sources are efficiently provisioned, it’s good to obtain the VPN shopper profile by navigating to VPN servers page on IBM Cloud.
- Click on the Shopper-to-site servers tab after which on the identify of the VPN:
- Obtain the profile from the Purchasers tab.
- The VPN provisioned by means of Terraform makes use of certificates. Comply with the instructions here to connect with the OpenVPN Shopper.
- It is best to see the profitable connection in your OpenVPN Shopper:
Confirm the SSH connection
- On a terminal, add the SSH personal key to the SSH agent with the next command:
ssh-add <LOCATION_OF_PRIVATE_SSH_KEY> - Instance:
ssh-add ~/.ssh/<NAME_OF_THE_PRIVATE_KEY> - Run the next command to SSH into the RHEL VSI by means of a bastion host. You may be utilizing the personal IP tackle of the bastion in Zone 1:
ssh -J root@10.10.0.13 root@10.10.128.13- Keep in mind, you have to be linked to the client-to-site VPN to entry the RHEL VSI by means of the bastion host.
- After SSH, It is best to see directions to allow SSH session recording utilizing the TLOG package deal on RHEL.
Deploy session recording utilizing Ansible
To deploy the session recording resolution, it’s good to have the next packages put in on the RHEL VSI:
tlogSSSDcockpit-session-recording
The packages can be put in by means of Ansible automation on all of the VSIs—each bastion hosts and RHEL VSI.
- Transfer to the Ansible folder:
cd ansible- Create
hosts.inifrom the template file:
cp hosts_template.ini hosts.ini- Run the Ansible playbook to put in the packages from an IBM Cloud personal mirror/repository:
ansible-playbook main_playbook.yml -i hosts.ini --flush-cacheYou possibly can see in Determine 1 that after you SSH into the RHEL machine, you will note a observe saying: ATTENTION! Your session is being recorded!
Examine the session recordings, logs and studies
In the event you intently observe the messages post-SSH, you will note a URL to the online console that may be accessed utilizing the machine identify or personal IP over port 9090. To permit visitors on port 9090, within the Terraform code, change the worth of allow_port_9090 variable to true and run terraform apply. The most recent terraform apply will add ACL and safety group guidelines to permit visitors on port 9090.
- Now, open a browser and navigate to
http://10.10.128.13:9090. To entry utilizing the VSI identify, it’s good to arrange a non-public DNS (out of scope for this text). You want a root password to entry the online console:
- Navigate to Session Recording on the left-hand aspect to see the record of session recordings. Together with session recordings, you possibly can verify the logs, diagnostic studies, and many others.:
Really helpful studying
Conclusion
This text coated why session recording is required in bastion hosts for auditing and compliance and the way session recording could be arrange with the built-in RHEL packages utilizing Ansible Automation.
Whereas designing a secured digital personal cloud community, you discovered the most effective practices in architecting a VPC personal community. We additionally coated the necessity to construct extremely accessible VPN servers and bastion hosts. With the provisioning of cloud infrastructure utilizing Terraform and Ansible for session recording, you bought hands-on expertise.
Learn more about IBM Cloud VPC
In case you have any queries, be happy to achieve out to me on Twitter or on LinkedIn.
