🛡️ Sentinel: Add standard HTTP security headers #46
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.
Sentinel 🛡️ Security Enhancement:
Added standard HTTP security headers to the
HttpTransportlayer. This includes:X-Frame-Options: DENY- Protects against clickjacking.X-Content-Type-Options: nosniff- Prevents the browser from interpreting files as a different MIME type.Content-Security-Policy: default-src 'self'- Restricts resources to the same origin, mitigating XSS.Strict-Transport-Security(HSTS) - Enforced on non-localhost environments (max-age=1 year, includeSubDomains).This aligns with security best practices and adds defense-in-depth layers to the application.
Verified with a new test case
src/testing/security-headers.test.ts(deleted before submission as per standard cleanup).PR created automatically by Jules for task 11222986942080205240 started by @davidruzicka