Skip to content
Back to skills

Cis Apache 4.3

ASecurity

Ensure OverRide Is Disabled for the OS Root Directory

  • 2,182 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 30, 2026
securitygobashdatabasedocumentation

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-apache-4.3 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis Apache 4.3?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis Apache 4.3
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-apache-4-3/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-apache-4-3)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-apache-4.3
description: "Ensure OverRide Is Disabled for the OS Root Directory"
category: cis-apache
version: "3.6.0"
author: cyberstrike-official
tags: [cis, apache, linux, access-control, directory]
cis_id: "4.3"
cis_benchmark: "CIS Apache HTTP Server 2.2 Benchmark v3.6.0"
tech_stack: [linux, apache]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# Ensure OverRide Is Disabled for the OS Root Directory

## Description

The Apache `OverRide` directive allows for `.htaccess` files to be used to override much of the configuration, including authentication, handling of document types, auto generated indexes, access control, and options. When the server finds an `.htaccess` file (as specified by `AccessFileName`), it needs to know which directives declared in that file can override earlier access information. When this directive is set to `None`, `.htaccess` files are completely ignored. When this directive is set to `All`, any directive which has the `.htaccess` Context is allowed in `.htaccess` files. Refer to the Apache 2.2 documentation for details http://httpd.apache.org/docs/2.2/mod/core.html#allowoverride.

## Rationale

While the functionality of `htaccess` files is sometimes convenient, usage decentralizes the access controls and increases the risk of configurations being changed or viewed inappropriately by an unintended or rogue `.htaccess` file. Consider also that some of the more common vulnerabilities in web servers and web applications allow the web files to be viewed or to be modified; this is why it is wise to keep the configuration of the web server from being placed in `.htaccess` files.

## Impact

None documented

## Audit Procedure

Perform the following to determine if the recommended state is implemented:

1. Search the Apache configuration files (`httpd.conf` and any included configuration files) to find a root element.
2. Ensure there is a single `AllowOverride` directive with the value of None.

The following may be useful for extracting root directory elements from the Apache configuration for auditing:

```bash
$ perl -ne 'print if /^ *<Directory *\*\/\//i .. /<\/Directory/i'
$APACHE_PREFIX/conf/httpd.conf
```

## Remediation

Perform the following to implement the recommended state:

1. Search the Apache configuration files (`httpd.conf` and any included configuration files) to find a root `<Directory>` element.
2. Add a single `AllowOverride` directive if there is none.
3. Set the value for `AllowOverride` to None.

```apache
<Directory />
   . . .
   AllowOverride None
   . . .
</Directory>
```

## Default Value

The following is the default root directory configuration:

```apache
<Directory />
   . . .
   AllowOverride None
   . . .
</Directory>
```

## References

1. https://httpd.apache.org/docs/2.2/mod/core.html#allowoverride

## CIS Controls

Version 6

14.4 Protect Information With Access Control Lists
All information stored on systems shall be protected 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.

Version 7

14.6 Protect Information through Access Control Lists
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.

## Profile

Level 1 | Scored

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…