3.10 Ensure the ScoreBoard File Is Secured
Profile Applicability
Description
The ScoreBoardFile directive sets a file path which the server will use for inter-process communication (IPC) among the Apache processes. On most Linux platforms, shared memory will be used instead of a file in the file system, so this directive is not generally needed and does not need to be specified. However, if the directive is specified, then Apache will use the configured file for the inter-process communication. Therefore, if it is specified, it needs to be located in a secure directory.
Rationale
If the ScoreBoardFile is placed in a writable directory, other accounts could create a denial of service attack and prevent the server from starting by creating a file with the same name, and users could monitor and disrupt the communication between the processes by reading and writing to the file.
Audit
- Check to see if the
ScoreBoardFile is specified in any of the Apache configuration files. If it is not present, the configuration is compliant.
- Find the directory in which the
ScoreBoardFile would be created. The default value is the ServerRoot/logs directory.
- Verify that the scoreboard file directory is not a directory within the Apache
DocumentRoot
- Verify that the ownership and group of the directory is
root:root (or the user under which Apache initially starts up if not root).
- Change the permissions so that the directory is only writable by
root (or the startup user if not root).
- Check that the scoreboard file directory is on a locally mounted hard drive rather than an NFS mounted file system.
Remediation
- Check to see if the
ScoreBoardFile is specified in any of the Apache configuration files. If it is not present, no changes are required.
- If the directive is present, find the directory in which the
ScoreBoardFile would be created. The default value is the ServerRoot/logs directory.
- Modify the directory if the
ScoreBoardFile is in a directory within the Apache DocumentRoot
- Change the ownership and group to be
root:root, if not already.
- Change the permissions so that the directory is only writable by root, or the user under which apache initially starts up (default is
root),
- Check that the scoreboard file directory is on a locally mounted hard drive rather than an NFS mounted file system.
Default Value
The default scoreboard file is logs/apache_status.
References
- https://httpd.apache.org/docs/2.4/mod/mpm_common.html#scoreboardfile
CIS Controls
| Controls Version |
Control |
IG 1 |
IG 2 |
IG 3 |
| v8 |
3.3 Configure Data Access Control ListsConfigure data access control lists based on a user's need to know. Apply data access control lists, also known as access permissions, to local and remote file systems, databases, and applications. |
● |
● |
● |
| v7 |
14.6 Protect Information through Access Control ListsProtect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
● |
● |
● |
Profile
1---2name: cis-apache24-3-103description: Ensure the ScoreBoard File Is Secured4---56# 3.10 Ensure the ScoreBoard File Is Secured78## Profile Applicability910- Level 11112## Description1314The `ScoreBoardFile` directive sets a file path which the server will use for inter-process communication (IPC) among the Apache processes. On most Linux platforms, shared memory will be used instead of a file in the file system, so this directive is not generally needed and does not need to be specified. However, if the directive is specified, then Apache will use the configured file for the inter-process communication. Therefore, if it is specified, it needs to be located in a secure directory.1516## Rationale1718If the `ScoreBoardFile` is placed in a writable directory, other accounts could create a denial of service attack and prevent the server from starting by creating a file with the same name, and users could monitor and disrupt the communication between the processes by reading and writing to the file.1920## Audit21221. Check to see if the `ScoreBoardFile` is specified in any of the Apache configuration files. If it is not present, the configuration is compliant.232. Find the directory in which the `ScoreBoardFile` would be created. The default value is the `ServerRoot/logs` directory.243. Verify that the scoreboard file directory is not a directory within the Apache `DocumentRoot`254. Verify that the ownership and group of the directory is `root:root` (or the user under which Apache initially starts up if not `root`).265. Change the permissions so that the directory is only writable by `root` (or the startup user if not `root`).276. Check that the scoreboard file directory is on a locally mounted hard drive rather than an NFS mounted file system.2829## Remediation30311. Check to see if the `ScoreBoardFile` is specified in any of the Apache configuration files. If it is not present, no changes are required.322. If the directive is present, find the directory in which the `ScoreBoardFile` would be created. The default value is the `ServerRoot/logs` directory.333. Modify the directory if the `ScoreBoardFile` is in a directory within the Apache `DocumentRoot`344. Change the ownership and group to be `root:root`, if not already.355. Change the permissions so that the directory is only writable by root, or the user under which apache initially starts up (default is `root`),366. Check that the scoreboard file directory is on a locally mounted hard drive rather than an NFS mounted file system.3738## Default Value3940The default scoreboard file is `logs/apache_status`.4142## References43441. https://httpd.apache.org/docs/2.4/mod/mpm_common.html#scoreboardfile4546## CIS Controls4748| Controls Version | Control | IG 1 | IG 2 | IG 3 |49| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- |50| v8 | 3.3 Configure Data Access Control Lists<br>Configure data access control lists based on a user's need to know. Apply data access control lists, also known as access permissions, to local and remote file systems, databases, and applications. | ● | ● | ● |51| v7 | 14.6 Protect Information through Access Control Lists<br>Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. | ● | ● | ● |5253## Profile5455- Level 1 | Manual
cyberstrikeus