Skip to main content

CLOUD MODELS – PROS AND CONS – PRIVATE CLOUD – IAAS

 




It is up to the IT department and infrastructure to provide scalable, secure, high performing and fast deliverable solutions that will aid the business to be successful.

CIOs have to make the critical decision to choose the right infrastructure that will meet the demands of the business and the market. A bad decision can be the demise of a line of business or the business as whole.

With all the IT infrastructure options we have at our disposal as of 2021, IT CIOs need to pick what makes sense from a cost, speed to deliver, performance, scalability and security. To name a few.

This article will provide information on the different cloud computing models. I will go over the advantages and disadvantages of the four most widely cloud models.

Private Cloud (on prem).

  1. IaaS (Infrastructure as a Service).
  2. PaaS: (Platform as a Service).
  3. SaaS: Software as a Service
Consider Donating to allow me to make more useful videos for you  and keep this space (your space) ad free. When you donate I will provide a discount code in my training store. Go to the discount page here.

 
  1. Go to the Training store for mode in-depth training 
  2. Go to the Training Index to checkout all the courses we have available 

Comments

Popular posts from this blog

How to Connect to AWS in a Quick & Inexpensive way Part 2:

  Architecture Benefits 1.       End to End Dynamic Routing. a.       BGP . b.       ECMP. 2.       Highly Available. a.       Dual Firewalls. b.       Dual IPSec Tunnels. 3.       Scalable. a.       IPSec Tunnels. b.       AWS Firewalls. 4.       Secure. a.       End to End Encrypted Traffic  to AWS (IPSec). b.       Encrypted Apps (https, SSH, FTPS, etc). 5.       Throughput: 2x 5.6Gbps. Traffic Flow 1.       On-Prem network. 2.       IPSEC ECMP (Load Balancing) To FWs 3.       GRE Tunnels. 4.       TGW Peer Attachment 5.       VPC (Servers or Endpoints) Consider Donating   to allow me to make more useful videos for you  . When you donate I will provide a discount code in my   training store . Go to the discount page here.   Go to the  Training store  for mode in-depth training  Go to the  Training Index  to checkout all the courses we have available  Disclaimer : The information posted here is informational only. Ricardo Gutierrez won’t be held liable for any mishaps, failures or an

HOW TO BLOCK NAT SLIPSTREAMING ON PALO ALTO FIREWALLS

  Update: 02/10/2021 If you are using threat DB version 8373-6537, the default action now is reset-server. The main objective of Cybersecurity professionals, is to reduce the attack surface, on network connected devices (computers, IoT, hvac, smart UPSs, smart power strips, etc.). Cybersecurity professionals often assume that devices that have no internet connectivity will never be compromised by a hacker. The NAT slipstreaming cyberattack proves this wrong. “ NAT Slipstreaming allows an attacker to remotely access ANY TCP/UDP service bound to ANY system behind a victim’s NAT, bypassing the victim’s NAT/firewall (remote arbitrary firewall pinhole control),  all it takes is the victim’s computer to visit the attacker’s website”. Once the victim’s computer visits the website, the attacker’s servers start to scan your network to identify the network connected devices. If your devices have not been patched to mitigate vulnerabilities, the attackers will exploit these to take control over

EASIEST WAY TO BUILD SECURITY GROUP RULES AND ROUTE ENTRIES IN AWS

  Adding IP prefixes to security group rules and route entries can be a time consuming and error prone task, especially when you have to build them on multiple VPCs. The fastest and most accurate method to reuse IP prefixes in your Security groups and route table entries is to use “Managed Prefix List“. This will save you time to build your security group rules and your route table entries. When you build several security group, you have to specify the IP prefixes on EVERY Security group rule . If you have a rule with 10 or more IP prefixes you need to add them manually; it becomes a time consuming and error prone task. Even if you automate this process (eg. Terraform, CloudFormation) you still have to build your code for each security group for every VPC. Another advantage is when you use the “managed prefix list” When you build Route tables you need to specify IP prefixes. You may have multiple IP prefixes, this can also be a time consuming and error prone task.  You will have to add