Syncfusion aspnetcore security
Skill syncfusion/aspnetcore-ui-components-skills/skills/syncfusion-aspnetcore-security
**CONTENT SECURITY POLICY (CSP) GUIDE** — Assist with configuring Syncfusion ASP.NET Core EJ2 components to work with strict Content Security Policy (CSP) headers. Use when: implementing CSP headers, generating and applying nonces to inline scripts/styles, configuring external font allowlists, or troubleshooting CSP violations.From its SKILL.md
npx -y skills add syncfusion/aspnetcore-ui-components-skills --skill syncfusion-aspnetcore-securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 278 tokens by cl100k_base, as published. Nobody here has run it
Content Security Policy (CSP) — Syncfusion ASP.NET Core (Security)
Use this skill for high-level, Syncfusion-specific CSP guidance and references. Detailed code snippets and implementation examples live in the concern's references files.
When to Use
- Implementing CSP headers for Syncfusion EJ2 controls
- Running in strict CSP mode where inline scripts/styles are restricted
- Adding nonces to inline scripts/styles for Syncfusion initialization
- Allowlisting CDN resources or external fonts required by Syncfusion themes
Quick Checklist
- Generate a cryptographically secure nonce per request
- Add the nonce to the CSP header and to all Syncfusion script/style tags
- Allow required CDN origins and font providers in CSP directives
- Avoid
unsafe-inline/unsafe-evalunless absolutely necessary - Verify behavior in browser DevTools and address CSP violations
Generic Guidelines (Summary)
- Generate nonces early in the pipeline and store them in
HttpContextfor views - Use minimal, explicit CSP directives (prefer
'self', explicit hostnames, and'nonce-<value>') - Prefer data binding over inline templates to avoid
unsafe-evalrequirements - Document your CSP policy and the reasons for any relaxations
References
- Main implementation and examples: references/csp-guide.md
What ships with it: 1 file
11.9 KB alongside SKILL.md
references/
- csp-guide.md11.9 KB