Skip to content

Content Security Policy (CSP) header not set #2202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tolgaOzen opened this issue May 1, 2025 — with Aikido Issues · 0 comments
Open

Content Security Policy (CSP) header not set #2202

tolgaOzen opened this issue May 1, 2025 — with Aikido Issues · 0 comments
Labels

Comments

Copy link
Member

Find more live information in Aikido here: https://app.aikido.dev/queue?sidebarIssue=7034472&groupId=6798&sidebarIssueTask=482645&sidebarTab=tasks

Scope

This task includes issues in the following domain:

TLDR

Content Security Policy (CSP) is a first line of defense against common attacks including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft via account takeovers to site defacement or distribution of malware. CSP config allows you to declare what content can be loaded and executed via a standard HTTP header. You can whitelist JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.

How to fix

Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant