Timeline for How to prevent directory access by a third party component?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2018 at 22:46 | comment | added | NivF007 | The cPanel/WHM option lacks facilities for automated offsite and encrypted backups therefore is neither secure nor reliable. You can do a search for best practices for backups, but it is generally accepted that a good policy will include remote storage, automated frequent and regular backups, a retention span policy, encrypted and protected from 3rd party access, use of RAID arrays and a stack of multiple solutions (i.e. some hosts take daily backups with a retention span of 30 days - a good addition to the above mentioned best practices). A conscientious admin will employ these practices. | |
| Feb 15, 2018 at 22:24 | comment | added | itoctopus | How often does a regular Joomla administrator use the above features? If you need only site backup, then the best (and, again, most reliable) method would be to use cPanel/WHM backup. | |
| Feb 15, 2018 at 21:11 | comment | added | NivF007 | To answer your question, Akeeba provides the tools for added convenience and security for creating automated, encrypted, offsite backups. For example, one recommended setup is to use the encrypted JPS format with 64 truly random character password, Amazon S3 with buckets for each site, a write-only IAM account, a policy for object lifecycle, saving certain older backups to Amazon Glacier and automatically removing the rest. I could be wrong, but I'm not sure creating this level of security and automation for backups is even possible through just the cPanel/WHM - at best it would be arduous. | |
| Feb 14, 2018 at 19:35 | history | edited | itoctopus | CC BY-SA 3.0 |
deleted 6 characters in body
|
| Feb 14, 2018 at 13:22 | history | answered | itoctopus | CC BY-SA 3.0 |