The classic shared-hosting fear: badly written PHP next door eats your CPU — or a hostile neighbour reads files under /home. CloudLinux CageFS cages each user into their own visible filesystem; LVE caps CPU/RAM/IO.
What does CageFS hide?
Depending on configuration, CageFS separates other users' home directories and sensitive system paths from the account's view. Do not assume event coverage: verify the scope and retention of audit, Imunify360 and system logs separately, and test isolation through permission and escape checks.
Reading LVE limits
When a customer reports a slow site, review LVE faults—EP, NPROC, IO and memory—against a baseline. Confirm cause and plan scope before raising limits. If there are no faults, measure the application, cache, queries, external services, network and storage separately; the LVE result alone does not prove root cause.
Isolation has licensing and operating cost; evaluate it against shared-resource impact, unauthorised access, incident response and expected outage cost. No single layer guarantees absolute separation.
