cloud-topics

virtual host configuration in Linux: 1. Buy a domain from godaddy etc. 2. Must have server to host this domain with static IP. 3. After buying this domain update dns records/name server in go daddy(name server of your service provider where you buy a server) 4.Now create zone for your domain to update records A etc in name server of your service provider where you buy a server and this name server is managed by sp so you need to ask them to update. Note: There can be two different name servers for zones (DNS-forward, RDNS-reverse) 5.Now as usual install package httpd,apache,ngnix,tomcat (different webservers) in the server. 6.for ex , for http go to virtual host conf file and add this domain(check online for more info) SSL configuration in Linux: 1.Generate csr and private key to ssl provider 2.They give crt file,bundle file once you purchase 3.Before step 4 you should have crt file  which is saved domain.crt(mycloud.com.crt),bundle file and key 4.Now in the server inst

Every server running in your IT environment needs an account, and every account requires privileges. Many organizations take inadequate steps in managing privileged accounts – leaving them vulnerable to attack and opening the door to potentially devastating data breaches. Today, most breaches start with people installing something they shouldn’t, connecting to somewhere they shouldn’t, or accessing data they shouldn’t. What does all of this have in common? Privilege misuse and abuse. When users need elevated privileges on a Unix or Linux server, security admins often turn to free tools like Super User Do, or Sudo (“soo-doo”). Sudo enables privileged access without exposing the root password. But it has flaws. Like limited granularity, lack of data integrity and no log security. Its policies typically need to be managed on each server, making it hard to lock down and prone to tampering. With this ad-hoc tool, it’s virtually impossible to maintain security and compliance