A system administrator is usually responsible for the entirety of an IT infrastructure. This includes several services (e.g. web server, mail server, database server, SSH, DNS, etc.) on one or on several servers. If one component is compromised, it is likely that this opens holes to attack other services.
As a consequence, it is desired to secure all components of an IT
infrastructure and keep them up-to-date and secure with only a little
or no dependencies to other system. It is also wise to abandon
services which are not necessarily required (e.g. an additional
IMAP/POP3 server, etc.). In short words:
keep your hosting environment as slim as possible for performance and
Events in TYPO3 Log Files¶
Login attempts to the TYPO3 backend, which are unsuccessful, are logged using the TYPO3 logging API. It is possible to create a dedicated logfile for messages from TYPO3 authentication classes which can be handled by external tools, such as fail2ban.
Example logging configuration:
$GLOBALS['TYPO3_CONF_VARS']['LOG']['TYPO3']['CMS']['Core']['Authentication']['writerConfiguration'] = [ \Psr\Log\LogLevel::INFO => [ \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [ 'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_auth.log', ] ] ];
Defending Against Clickjacking¶
Clickjacking, also known as user interface (UI) redress attack or UI redressing, is an attack scenario where an attacker tricks a web user into clicking on a button or following a link different from what the user believes he/she is clicking on. This attack can be typically achieved by a combination of stylesheets and iframes, where multiple transparent or opaque layers manipulate the visual appearance of a HTML page.
To protect the backend of TYPO3 against this attack vector, a HTTP
X-Frame-Options is sent, which prevents embedding backend pages
in an iframe on domains different than the one used to access the
X-Frame-Options header has been officially standardized as
System administrators should consider enabling this feature at the frontend of the TYPO3 website, too. A configuration of the Apache web server would typically look like the following:
<IfModule mod_headers.c> Header always append X-Frame-Options SAMEORIGIN </IfModule>
SAMEORIGIN means, that the page can only be displayed in
a frame on the same origin as the page itself. Other options are
(page cannot be displayed in a frame, regardless of the site attempting
to do so) and
ALLOW-FROM [uri]` (page can only be displayed in a frame
on the specified origin).
Please understand that detailed descriptions of further actions on a server-level and specific PHP security settings are out of scope of this document. The TYPO3 Security Guide focuses on security aspects of TYPO3.