# Cis Apache 5.10

> Ensure Access to .ht* Files Is Restricted

- Skill: `cyberstrikeus/cis-apache-5-10` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-apache-5-10`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-apache-5-10/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/cis-apache-5-10

---


# Ensure Access to .ht\* Files Is Restricted

## Description

Restrict access to any files beginning with `.ht` using the `FilesMatch` directive.

## Rationale

The default name for the access file which allows files in web directories to override the Apache configuration is `.htaccess`. The usage of access files should not be allowed, but as a defense in depth a `FilesMatch` directive is recommended to prevent web clients from viewing those files in case they are created.

Also, common names for web password and group files are `.htpasswd` and `.htgroup`. Neither of these files should be placed in the document root, but in the event they are, the `FilesMatch` directive can be used to prevent them from being viewed by web clients.

## Audit Procedure

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

Verify that a `FilesMatch` directive similar to the one below is present in the Apache configuration and not commented out.

```
<FilesMatch "^\.ht">
  Order allow,deny
  Deny from all
</FilesMatch>
```

## Remediation

Perform the following to implement the recommended state:

Add or modify the following lines in the Apache configuration file at the server configuration level:

```
<FilesMatch "^\.ht">
  Order allow,deny
  Deny from all
</FilesMatch>
```

## Default Value

`.ht*` files are not accessible

## References

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

## CIS Controls

**Version 6**

18.3 Sanitize Input For In-house Software
For in-house developed software, ensure that explicit error checking is performed and documented for all input, including for size, data type, and acceptable ranges or formats.

**Version 7**

18.2 Ensure Explicit Error Checking is Performed for All In-house Developed Software
For in-house developed software, ensure that explicit error checking is performed and documented for all input, including for size, data type, and acceptable ranges or formats.

## Profile

Level 1 | Scored
Level 2 | Scored