When disabled, fortification mode allows write-access to any file under the Dokumentenstamm<\/a> of a hosted domain or subdomain. This is analogous to running the web application under your user account. When fortification is enabled, write-access is permitted to only select locations of a web application. Unless fortification permits it, the web application may not write to the destination.<\/p>\n <\/p>\n Fortification yields two benefits:<\/p>\n First, in the event that your site is hacked<\/a>, the attacker has limited mobility. Backdoors are frequently\u00a0installed in system files that give the attacker multiple methods of re-entry once the initial ingress point has been secured (often, outdated software installed on that web site). Unless\u00a0fortification explicitly permits write-access to those files, an attacker cannot install a backdoor. Those access points that the web application may write, e.g. \/wp-content\/uploads for WordPress or \/administrator\/cache in Joomla, are further limited by our security policies to disallow public access or serve only static content such as\u00a0images, movies, or downloadable files.<\/p>\n Second, if a breach were to occur,\u00a0running as a secondary user limits the scope of damage. An attacker is unable to snoop through your email, compromise your ssh keys, or gain access to the control panel. Damage is superficial at best. In addition, because these files are flagged with web application as its creator\/owner, it makes audit trails very easy to establish allowing for us to quickly inoculate your site.<\/p>\n But<\/em>, please – do stay on top of updates for your applications. Fortification is a feature to help keep your account secure, but it does not keep your account secure. Judicious use of third-party plugins, software updates, and strong passwords do. We cover automatic updates<\/strong> for WordPress, Joomla!, Drupal, and Magento, but there are thousands of web applications that users opt to install that are not enrolled in our automatic update program. Every time your account is compromised, a $15 fee is charged to the account.<\/p>\n Applications support a variety of fortification modes depending upon what support is provided in the control panel codebase. Only Learning Mode is enabled for unknown applications. For other supported applications, the following three fortification modes apply.<\/p>\n Learning Mode<\/strong>:\u00a0if an application is not recognized or has not been previously detected<\/a>, then Learning Mode is enabled. Learning Mode\u00a0allows 100% write-access to the document root. After 30 minutes, a background task calculates what files have been modified, then establishes a fortification\u00a0personality for that web site. Only files created or modified during that window will be allowed future write-access.<\/p>\n Fortification On (MIN)<\/strong>: Minimum Fortification allows the greatest degree of freedom by the web application to write to and modify files. When enabled, you should never be prompted to change permissions on any files. Consequently, an attacker will have access to modify more files, including vital system files and potentially alter your .htaccess<\/a> file – if present – to alter the way in which your web site is handled by the server.<\/p>\n Fortification On<\/strong>: Normal Fortification is the maximum reasonable fortification for a web site as established by our development team. You may need to alter permissions of files (or enable Web App Write Mode<\/em>)\u00a0to allow write-access in extreme situations, such as installing a new plugin or updating the application\u00a0system files from its built-in update panel if supported by the web app and not supported by the control panel. Most paths are also filtered to serve assets as-is reducing the ability a hacker has to leverage secondary backdoors installed once the site becomes compromised.<\/p>\n Web App Write Mode<\/strong>: Web App Write Mode releases fortification on a 10 minute timer. After 10 minutes has elapsed, Normal Fortification is enabled. This is useful in situations where new plugins are installed or in-place updates are performed.<\/p>\n Release Fortification:<\/strong> disable fortification on the web app entirely and allow write-access to every file on the site to the web application. Typically\u00a0very dangerous<\/em>.<\/span><\/p>\n The following diagram illustrates normal, min, and released fortification modes for WordPress.<\/p>\n![\"fortification-mode\"](\"https:\/\/kb.okra.host\/wp-content\/uploads\/2016\/06\/fortification-mode.png\")
<\/a><\/p>\nBenefits of Fortification<\/h2>\n
Fortification Modes<\/h2>\n
Fortification\u00a0Visualized<\/h2>\n
![\"fortification](\"https:\/\/kb.okra.host\/wp-content\/uploads\/2016\/06\/fortification-diagram-2.png\")
<\/a><\/p>\n