<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Headers on N7 Docs</title><link>https://docs.n7.io/delivery/security/headers/</link><description>Recent content in Headers on N7 Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.n7.io/delivery/security/headers/index.xml" rel="self" type="application/rss+xml"/><item><title>Origin Whitelisting with Origin Identity Secret</title><link>https://docs.n7.io/delivery/security/headers/accesskey/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/delivery/security/headers/accesskey/</guid><description>&lt;p&gt;To enhance the security of your origin servers when using Nitrogen (N7), we have introduced the Origin Identity Secret (&lt;code&gt;X-Nv-Access-Key&lt;/code&gt;) HTTP header. This feature allows your origin to verify that incoming requests have been processed and forwarded by the N7 network, preventing unauthorized direct access.&lt;/p&gt;
&lt;p&gt;This document explains how the &lt;code&gt;X-Nv-Access-Key&lt;/code&gt; works, how to manage your secret keys, and how to configure your origin server for seamless key rotation.&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;a class="heading-anchor" href="#overview" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When enabled, Nitrogen will add a unique &lt;code&gt;X-Nv-Access-Key&lt;/code&gt; header to all requests forwarded to your origin server. The value of this header is a secret key that you can manage within the Nitrogen dashboard (&lt;code&gt;dash.n7.io&lt;/code&gt;).&lt;/p&gt;</description></item><item><title>CORS</title><link>https://docs.n7.io/delivery/security/headers/cors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/delivery/security/headers/cors/</guid><description>&lt;p&gt;This page will show you the options to configure CORS (Cross-Origin Resource Sharing) response headers for your site. Refer this &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS" target="_blank" rel="noreferrer"&gt;MDN link&lt;/a&gt;
 for more details.
&lt;/br&gt;&lt;/br&gt;
It is a mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources.&lt;/br&gt;
&lt;/br&gt;
&lt;em&gt;Note: For demo purpose, we will be using &lt;code&gt;www.nviztest.com&lt;/code&gt; domain as an example.&lt;/em&gt;&lt;/br&gt;&lt;/p&gt;
&lt;h2 id="prerequisite"&gt;Prerequisite&lt;a class="heading-anchor" href="#prerequisite" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;You must have a domain configured on Nitrogen.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="steps"&gt;Steps&lt;a class="heading-anchor" href="#steps" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;code&gt;Security&lt;/code&gt; menu, and open &lt;code&gt;CORS&lt;/code&gt; tab.&lt;br/&gt;&lt;/p&gt;</description></item><item><title>CSP</title><link>https://docs.n7.io/delivery/security/headers/csp/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/delivery/security/headers/csp/</guid><description>&lt;p&gt;This page will show you the step to configure CSP (Content-Security-Policy) response header for your site. Refer this &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy" target="_blank" rel="noreferrer"&gt;MDN link&lt;/a&gt;
 for more details.
&lt;/br&gt;&lt;/br&gt;
It allows website administrators to control resources the user agent is allowed to load for a given page. This helps guard against cross-site scripting attacks (Cross-site_scripting).&lt;/br&gt;
&lt;/br&gt;
&lt;em&gt;Note: For demo purpose, we will be using &lt;code&gt;www.nviztest.com&lt;/code&gt; domain as an example.&lt;/em&gt;&lt;/br&gt;&lt;/p&gt;
&lt;h2 id="prerequisite"&gt;Prerequisite&lt;a class="heading-anchor" href="#prerequisite" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;You must have a domain configured on Nitrogen.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="steps"&gt;Steps&lt;a class="heading-anchor" href="#steps" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;code&gt;Security&lt;/code&gt; menu, and open &lt;code&gt;CSP&lt;/code&gt; tab.&lt;br/&gt;&lt;/p&gt;</description></item><item><title>HSTS</title><link>https://docs.n7.io/delivery/security/headers/hsts/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/delivery/security/headers/hsts/</guid><description>&lt;p&gt;This page will show you steps to configure HSTS (Strict-Transport-Security) response header for your site. Refer this &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security" target="_blank" rel="noreferrer"&gt;MDN link&lt;/a&gt;
 for more details.
&lt;/br&gt;&lt;/br&gt;
HSTS response header informs browsers that the site should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS.&lt;/br&gt;&lt;/p&gt;
&lt;p&gt;When a browser knows that a domain has enabled HSTS, it does two things:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Always uses an https:// connection, even when clicking on an http:// link or after typing a domain into the location bar without specifying a protocol.&lt;/li&gt;
&lt;li&gt;Removes the ability for users to click through warnings about invalid certificates.
&lt;/br&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Note: For demo purpose, we will be using &lt;code&gt;www.nviztest.com&lt;/code&gt; domain as an example.&lt;/em&gt;&lt;/br&gt;&lt;/p&gt;</description></item><item><title>XSS</title><link>https://docs.n7.io/delivery/security/headers/xss/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/delivery/security/headers/xss/</guid><description>&lt;p&gt;This page will show you the options to configure XSS (Cross-Site-Scripting) response headers for your site.
&lt;/br&gt;&lt;/br&gt;
Cross-site scripting (XSS) is a security exploit which allows an attacker to inject into a website malicious client-side code. These attacks succeed if the Web app does not employ enough validation or encoding. Refer this &lt;a href="https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting" target="_blank" rel="noreferrer"&gt;MDN link&lt;/a&gt;
 for more details.&lt;/br&gt;
&lt;/br&gt;
&lt;em&gt;Note: For demo purpose, we will be using &lt;code&gt;www.nviztest.com&lt;/code&gt; domain as an example.&lt;/em&gt;&lt;/br&gt;&lt;/p&gt;
&lt;h2 id="prerequisite"&gt;Prerequisite&lt;a class="heading-anchor" href="#prerequisite" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;You must have a domain configured on Nitrogen.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="steps"&gt;Steps&lt;a class="heading-anchor" href="#steps" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;code&gt;Security&lt;/code&gt; menu, and open &lt;code&gt;XSS&lt;/code&gt; tab.&lt;br/&gt;&lt;/p&gt;</description></item></channel></rss>