Secure Coding & OWASP Top 10 for Backend · 课时

后端的内容安全策略（CSP）

了解后端配置如何影响内容安全策略（CSP），从而缓解 XSS 等客户端攻击。

第 3 / 4 课11 个步骤

后端的内容安全策略（CSP） 是 CoddyKit 上的免费 Secure Coding & OWASP Top 10 for Backend 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Secure Coding & OWASP Top 10 for Backend 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Backend's Role in CSP

Welcome to Content Security Policy (CSP) for Backend! You might think CSP is just for frontend developers, but the backend plays a crucial role.

CSP is a security standard that helps prevent client-side attacks like Cross-Site Scripting (XSS). It does this by telling the browser which resources (scripts, styles, images) it's allowed to load and execute.

The backend is responsible for delivering these rules to the browser.

How Backend Delivers CSP

The backend delivers CSP rules to the browser using a special HTTP response header called Content-Security-Policy. When the browser receives this header, it enforces the rules defined within it.

This means your backend application directly controls the security policy for your frontend. Let's see how a backend might set this header.

Setting the CSP Header

In a backend application, you'd typically add the CSP header to your HTTP response. This example simulates a backend sending a basic CSP header.

The default-src 'self' directive allows resources only from the same origin as the document.

public class BackendCspExample {
  public static void main(String[] args) {
    System.out.println("HTTP/1.1 200 OK");
    System.out.println("Content-Type: text/html");
    System.out.println("Content-Security-Policy: default-src 'self';");
    System.out.println("");
    System.out.println("<!-- Your secure HTML content goes here -->");
  }
}

Key CSP Directives for Backend

As a backend developer, you'll often define directives that control various resource types. Some common ones include:

script-src: Specifies valid sources for JavaScript.
style-src: Specifies valid sources for stylesheets.
img-src: Specifies valid sources for images.
connect-src: Restricts URLs that can be loaded using scripting interfaces (e.g., AJAX, WebSockets).

Each directive can have multiple allowed sources, like 'self', https://example.com, or 'unsafe-inline' (generally to be avoided).

Mitigating Inline Scripts with Nonces

One common XSS attack vector is injecting inline scripts. CSP can block these, but sometimes inline scripts are necessary.

The backend can generate a unique, cryptographically secure nonce (Number Used Once) for each request. This nonce is added to both the CSP header and the allowed inline <script> tags.

Backend Nonce Generation

Here's how a backend can generate a nonce. This nonce is then included in the Content-Security-Policy header (e.g., script-src 'nonce-YOUR_NONCE_HERE') and rendered into the HTML script tag.

The browser will only execute inline scripts that have a matching nonce attribute.

import java.util.Base64;
import java.security.SecureRandom;

public class NonceGenerator {
  public static void main(String[] args) {
    SecureRandom random = new SecureRandom();
    byte[] nonceBytes = new byte[16]; // 16 bytes for a good nonce
    random.nextBytes(nonceBytes);
    String nonce = Base64.getEncoder().encodeToString(nonceBytes);
    System.out.println("Generated Nonce: " + nonce);
    System.out.println("\nUse this in your CSP header:");
    System.out.println("Content-Security-Policy: script-src 'self' 'nonce-" + nonce + "';");
    System.out.println("\nAnd in your HTML:");
    System.out.println("<script nonce=\"" + nonce + "\">alert('Hello!');</script>");
  }
}

CSP Reporting: `report-to`

CSP isn't just about blocking; it's also about visibility. The backend can specify a reporting endpoint using the report-to directive (or older report-uri).

If a browser violates the CSP (e.g., tries to load a script from an unauthorized source), it will send a JSON report to this backend endpoint. Your backend can then log and analyze these reports to detect potential attacks or policy misconfigurations.

Integrating CSP with Frameworks

Modern backend frameworks often provide convenient ways to manage CSP headers without manually concatenating strings.

Spring Security (Java): Has dedicated configurations for HTTP security headers, including CSP.
Helmet (Node.js/Express): A middleware that helps secure Express apps by setting various HTTP headers, including CSP.
Django (Python): Can set CSP headers via middleware or specific libraries.

These tools simplify implementation and help ensure best practices.

CSP for XSS Prevention (Backend View)

From a backend perspective, correctly configured CSP adds a powerful layer of defense against XSS. Even if an attacker manages to inject malicious content into your HTML, CSP can prevent the browser from executing it.

By controlling the Content-Security-Policy header, your backend dictates what content is safe, significantly reducing the impact of client-side vulnerabilities.

CSP Header Challenge

Consider a backend service that needs to allow scripts only from its own domain and from cdn.example.com. Which CSP header directive would best achieve this?

在交互式课程中回答

Recap: Backend & CSP

You've learned that Content Security Policy (CSP) is a critical security layer delivered by the backend via the Content-Security-Policy HTTP header.

Backend sets CSP headers to control resource loading.
Directives like script-src define allowed sources.
Nonces are backend-generated tokens to safely allow specific inline scripts.
Backend can collect violation reports via report-to.
Frameworks simplify CSP implementation.

By actively managing CSP, backend developers significantly enhance their application's defense against client-side attacks like XSS.

免费开始

用 AI 导师学习 Secure Coding & OWASP Top 10 for Backend — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「后端的内容安全策略（CSP）」课时是免费的吗？

是的 — 「后端的内容安全策略（CSP）」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Secure Coding & OWASP Top 10 for Backend 课程的其余内容，请升级到 CoddyKit PRO。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。

「后端的内容安全策略（CSP）」这节课中我会学到什么？

了解后端配置如何影响内容安全策略（CSP），从而缓解 XSS 等客户端攻击。你通过在浏览器中直接运行的动手代码来练习 Secure Coding & OWASP Top 10 for Backend，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Secure Coding & OWASP Top 10 for Backend 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Secure Coding & OWASP Top 10 for Backend 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「后端的内容安全策略（CSP）」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Secure Coding & OWASP Top 10 for Backend 课中编写并运行代码吗？

能。每节 Secure Coding & OWASP Top 10 for Backend 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Secure Coding & OWASP Top 10 for Backend