server cloud Piergiorgio Venuti

Server Cloud

server cloud

A cloud server or VPS (Virtual Private Server) is a fully-fledged server with its own operating system and well-defined hardware features only that unlike a classic server it shares physical resources with other virtual machines in this way more VPS can be run simultaneously on the same server (hypervisor).

This virtualization technique allows significant cost savings and an optimization of hardware resources as it is possible to run multiple operating systems on the same hardware.

 

Server Cloud – Pros cons

Pros:

 

   ♦ Migration: It is possible to “move” (migrate) a VPS from one server (hypervisor) to another (even without interruption of service).

Example: You have created a VPS on a hypervisor in Italy and you want to move it to a server in America. With a VPS, as long as the Cloud Provider has another Datacenter in America, this can be done quickly.

   ♦ Scalability: It is the possibility of increasing or decreasing the hardware resources (CPU, RAM, Disk, etc) without rebuilding the VPS and in some cases without restarting it in full transparency to users who use the services provided.
Example: A VPS of 2 cores, 1 GB of RAM and 20 GB of disk has been created but after a few months we realize that the RAM memory is insufficient for the services provided and it is necessary to increase it. With a VPS it is very easy to solve this problem, just increase the RAM from the configuration panel and the new configuration will be applied (in the case of linux systems without the need to reboot).

   ♦ Autoscaling: It is the possibility to increase or decrease the resources (scaling) automatically according to well defined hardware policies. This technique is extremely valid in cases of load peaks.
Example: A VPS has been created with 2 cores, 1 GB of RAM and 20 GB but in some periods of the year due to the high user access these resources are not sufficient, then in this case it is possible to configure these policies:

a) If the CPU is at 90% for more than 1h then the CPU of a core increases every 30min for a maximum of 6 cores and then if the CPU is less than 10% for more than 1h decrease the CPU of a core every 30 min up to a minimum of 2 cores.

b) If the RAM is 99% for more than 1h then increase the RAM of 1Gb every 30min for a maximum of 32Gb and then if the RAM is less than 50% for more than 1h decrease the RAM of a core every 30 min until at a minimum of 1Gb.

   ♦ Low cost: by comparing the cost of a VPS to that of a fiscal server like hardware resources, the cost of a VPS is much lower, especially considering that some cost items are already included in the VPS fee. :
   a) Energy consumption;  

   b) Internet band;

   c) Cost of public IP addresses;

   d) Costs related to housing (cooling, surveillance, etc); 

   e) Firewall;

   f) Technical assistance.

Cons:

   ♦ Shared resources: Depending on the configurations and characteristics of the Cloud Provider, some hardware resources, such as the CPU, could be shared so performance may be lower than a physical server. This condition is not always true as it is possible to request a 100% allocation on all hardware resources to your Cloud Provider.

Server Cloud – Limits:

  1. ♦ OS Virtualization: Not all operating systems and platforms can be virtualized (Eg AS400, Apple OS).
  2. ♦ Band: Although this is not an inherent problem of virtualization itself there could be latency differences in the Internet connection between a physical server in the company and a VPS if users are predominantly within the company and if the company has not an adequate Internet line.
    Example: A physical server in the customer’s DMZ is accessed by its LAN users via a 10Gb line, if the server is virtualized and becomes a VPS at a Cloud provider, access to it is transmitted via the client’s Internet line which may be more slow.

Server Cloud – False myths:

  1. ♦ A VPS does not have the same performance as a physical server: By allocating 100% of the physical resources and correctly dimensioning a VPS the latter has nothing to envy to a physical server from a performance point of view.
  2. ♦ A VPS is less secure than a physical server: A VPS can have the same degree of security as a physical server because it is possible to adopt the same security measures (Firewall, Antivirus, Hardening, VPN) applicable to a Fiscal server.

Check out the Cloud Server

[btnsx id=”2931″]

Useful links:

IaaS | Cloud | Infrastructure as a Service

Let’s Encrypt Free Certificates for all Webhosting users

Alternative to the NAS

CloudFlare free Plesk extension for Webhosting users

Demo Cloud Servers

Free Microsoft Windows licenses

New templates for VPS

VPS

Docs

How to have your computer network under control

VPS Metered – Cloud location

ownCloud

Home

Share


RSS

More Articles…

Categories …

Tags

RSS Unknown Feed

RSS Full Disclosure

  • SEC Consult SA-20250604-0 :: Local Privilege Escalation and Default Credentials in INDAMED - MEDICAL OFFICE (Medical practice management) Demo version June 10, 2025
    Posted by SEC Consult Vulnerability Lab via Fulldisclosure on Jun 09SEC Consult Vulnerability Lab Security Advisory < 20250604-0 > ======================================================================= title: Local Privilege Escalation and Default Credentials product: INDAMED - MEDICAL OFFICE (Medical practice management) Demo version vulnerable version: Revision 18544 (II/2024) fixed version: Q2/2025 (Privilege Escalation, Default Password)...
  • Full Disclosure: CVE-2025-31200 & CVE-2025-31201 – 0-Click iMessage Chain → Secure Enclave Key Theft, Wormable RCE, Crypto Theft June 10, 2025
    Posted by josephgoyd via Fulldisclosure on Jun 09Hello Full Disclosure, This is a strategic public disclosure of a zero-click iMessage exploit chain that was discovered live on iOS 18.2 and remained unpatched through iOS 18.4. It enabled Secure Enclave key theft, wormable remote code execution, and undetectable crypto wallet exfiltration. Despite responsible disclosure, the research […]
  • Defense in depth -- the Microsoft way (part 89): user group policies don't deserve tamper protection June 3, 2025
    Posted by Stefan Kanthak on Jun 03Hi @ll, user group policies are stored in DACL-protected registry keys [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies] respectively [HKEY_CURRENT_USER\Software\Policies] and below, where only the SYSTEM account and members of the "Administrators" user group are granted write access. At logon the user&apos;s registry hive "%USERPROFILE%\ntuser.dat" is loaded with exclusive (read, write and...
  • CVE-2025-45542: Time-Based Blind SQL Injection in CloudClassroom PHP Project v1.0 June 3, 2025
    Posted by Sanjay Singh on Jun 03Hello Full Disclosure list, I am sharing details of a newly assigned CVE affecting an open-source educational software project: ------------------------------------------------------------------------ CVE-2025-45542: Time-Based Blind SQL Injection in CloudClassroom PHP Project v1.0 ------------------------------------------------------------------------ Product: CloudClassroom PHP Project Vendor:...
  • ERPNext v15.53.1 Stored XSS in bio Field Allows Arbitrary Script Execution in Profile Page June 3, 2025
    Posted by Ron E on Jun 03An authenticated attacker can inject JavaScript into the bio field of their user profile. When the profile is viewed by another user, the injected script executes. *Proof of Concept:* POST /api/method/frappe.desk.page.user_profile.user_profile.update_profile_info HTTP/2 Host: --host-- profile_info={"bio":"\">"}
  • ERPNext v15.53.1 Stored XSS in user_image Field Allows Script Execution via Injected Image Path June 3, 2025
    Posted by Ron E on Jun 03An authenticated user can inject malicious JavaScript into the user_image field of the profile page using an XSS payload within the file path or HTML context. This field is rendered without sufficient sanitization, allowing stored script execution in the context of other authenticated users. *Proof of Concept:*POST /api/method/frappe.desk.page.user_profile.user_profile.update_profile_info HTTP/2 […]
  • Local information disclosure in apport and systemd-coredump June 3, 2025
    Posted by Qualys Security Advisory via Fulldisclosure on Jun 03Qualys Security Advisory Local information disclosure in apport and systemd-coredump (CVE-2025-5054 and CVE-2025-4598) ======================================================================== Contents ======================================================================== Summary Mitigation Local information disclosure in apport (CVE-2025-5054) - Background - Analysis - Proof of concept Local information disclosure in systemd-coredump...
  • Stored XSS via File Upload - adaptcmsv3.0.3 June 3, 2025
    Posted by Andrey Stoykov on Jun 03# Exploit Title: Stored XSS via File Upload - adaptcmsv3.0.3 # Date: 06/2025 # Exploit Author: Andrey Stoykov # Version: 3.0.3 # Tested on: Debian 12 # Blog: https://msecureltd.blogspot.com/ Stored XSS via File Upload #1: Steps to Reproduce: 1. Login with low privilege user and visit "Profile" > "Edit […]
  • IDOR "Change Password" Functionality - adaptcmsv3.0.3 June 3, 2025
    Posted by Andrey Stoykov on Jun 03# Exploit Title: IDOR "Change Password" Functionality - adaptcmsv3.0.3 # Date: 06/2025 # Exploit Author: Andrey Stoykov # Version: 3.0.3 # Tested on: Debian 12 # Blog: https://msecureltd.blogspot.com/ IDOR "Change Password" Functionality #1: Steps to Reproduce: 1. Login as user with low privilege and visit profile page 2. Select […]
  • Stored XSS "Send Message" Functionality - adaptcmsv3.0.3 June 3, 2025
    Posted by Andrey Stoykov on Jun 03# Exploit Title: Stored XSS "Send Message" Functionality - adaptcmsv3.0.3 # Date: 06/2025 # Exploit Author: Andrey Stoykov # Version: 3.0.3 # Tested on: Debian 12 # Blog: https://msecureltd.blogspot.com/ Stored XSS "Send Message" Functionality #1: Steps to Reproduce: 1. Login as normal user and visit "Profile" > "Message" > […]

Customers

Newsletter

{subscription_form_1}