Security response headers — CSP, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy present

HTTP security headers provide a critical layer of browser-side protection against XSS, clickjacking, MIME sniffing, and data leakage. These headers are visible in any HTTP response and their absence signals a basic security gap to both regulators and attackers.

Medium priority

Trigger

When this rule fires

Content-Security-Policy header absent; X-Frame-Options header absent; X-Content-Type-Options: nosniff absent; Referrer-Policy absent

Applicability gate

Confirm the entity's role before treating this as a duty

This is a readiness rule mapped to JS2 themes. Its presence in the library does not establish that JS2 applies directly to the firm.

Insurance Broker: Most independent non-life Category I brokers are not directly in JS2's defined scope. A broker may be directly in scope if it separately meets a listed category, and may face contract or oversight requirements from an in-scope institution. Third-party provisions impose duties on the in-scope financial institution. They do not themselves make every supplier or intermediary directly subject to JS2.
Uma Binder Holder: UMA or binder-holder status is not itself listed in JS2's definition. Direct scope depends on another listed capacity; insurer contracts and oversight may create evidence requirements. JS2 paragraph 3.3 concerns juristic persons structured under an insurer or designated insurance group; it is not a blanket rule for every independent UMA or intermediary.
Insurer: An insurer as defined in the Insurance Act is directly in scope of JS2 from 1 June 2025. Apply proportionality and distinguish the insurer's own duty from requirements it places on third parties.

Citation

Mapped source

This control maps to the public instruments below. The mapping does not establish entity applicability.

Section

Joint Standard 2 of 2024 / POPIA s.19 / OWASP Top 10

Legislation

Joint Standard 2 of 2024
POPIA s.19

Remediation

How to close the gap

Add security headers to all web server responses. Use SecurityHeaders.com to test. Start with X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Referrer-Policy: strict-origin-when-cross-origin. Build CSP progressively.

Evidence required

Evidence to prepare if this control applies

SecurityHeaders.com scan report (B or above)
Web server configuration showing header additions
Screenshot of response headers from browser dev tools

Automated assessment

Verified by the Provantis cyber scanner. Machine checks performed:

CSP_HEADER
XFRAME_HEADER
XCONTENT_HEADER
REFERRER_POLICY

← Back to Digital Channel and Technical Security