Style Attributes vs Style Tags
What you'll learn: You'll understand how CSP treats inline style attributes differently from <style> tags, and why that matters for your security policy.
The Core Difference
In the CSP world, not all inline styles are created equal. There are two distinct types:
Style attributes are CSS rules applied directly to an HTML element:
<div style="color: red; font-size: 16px;">Hello</div>
Style tags are <style> elements containing CSS rules:
<style>
.greeting { color: red; font-size: 16px; }
</style>
Both are "inline" CSS (not loaded from external files), but CSP handles them separately.
Why CSP Treats Them Differently
Think of style attributes as "micro-injections" scattered throughout your HTML, while style tags are "centralized blocks" of styling. From a security perspective, they pose different risks.
Style attributes require the 'unsafe-inline' keyword in your style-src directive, OR you can use 'unsafe-hashes' with a hash of the specific attribute value. They're harder to secure with nonces because they're scattered everywhere.
Style tags can be secured with nonces or hashes, just like script tags. You add a nonce attribute to the <style> tag itself:
<style nonce="random123abc">
.greeting { color: red; }
</style>
The Practical Impact
Most modern CSP implementations focus on securing <style> tags with nonces, while either avoiding style attributes entirely or reluctantly allowing 'unsafe-inline' (which weakens your policy). Some teams extract all inline styles to <style> blocks or external files to strengthen CSP.
Key Takeaway: CSP distinguishes between style attributes (harder to secure, requiring 'unsafe-inline' or 'unsafe-hashes') and <style> tags (easier to secure with nonces or hashes), making style tags the preferred choice for strict policies.