Security: Add baseline security headers #692
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anonymoususer72041
force-pushed
the
security/headers-defaults
branch
from
291a167 to
ae12963
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a small set of conservative, low-risk HTTP security headers to the default Apache
.htaccessto improve baseline hardening for public OpenCATS installations.To avoid breaking setups where the Career Portal is embedded into an external website, the clickjacking protection (
X-Frame-Options: SAMEORIGIN) is applied globally but explicitly unset for/careers/(and all subpaths) via a dedicatedcareers/.htaccess.Motivation
OpenCATS currently ships without a baseline set of HTTP security headers. Adding these defaults provides immediate, broadly compatible security improvements for typical deployments without requiring server-specific configuration.
The chosen headers are intentionally conservative to minimize the risk of breaking existing installations or customizations, while still providing meaningful protection (e.g. against MIME sniffing, clickjacking, and unnecessary referrer leakage).