<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Clickjacking on Nalar</title>
    <link>https://nalar.dev/tags/clickjacking/</link>
    <description>Recent content in Clickjacking on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/clickjacking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Block Clickjacking with an Explicit Framing Policy</title>
      <link>https://nalar.dev/block-clickjacking-with-an-explicit-framing-policy/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/block-clickjacking-with-an-explicit-framing-policy/</guid>
      <description>&lt;p&gt;A sensitive web page can have sound authentication and authorization yet still be exposed through another site&amp;rsquo;s interface. If an attacker can place that page inside a transparent or disguised frame, a signed-in user may believe they are clicking one control while their click reaches a different control in the framed application.&lt;/p&gt;&#xA;&lt;p&gt;That attack class is &lt;strong&gt;clickjacking&lt;/strong&gt;, also called UI redressing. The browser is doing what both pages request; the security failure is that the sensitive application allowed an untrusted page to become part of its user interface.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
