slug

SlugPostViewer_Query

LandingLayout

blogPost

viewer

query SlugPostViewer_Query(
  $slug: String!
) {
  ...LandingLayout
  blogPost(slug: $slug) {
    __typename
    ... on QueryBlogPostSuccess {
      data {
        ...ArticleBlogHeader_BlogPost
        body
        seoTitle
        summary
        title
        featuredImage
        metaDescription
        published
        updated
        author {
          name
          profileImage
          bio
        }
        tags {
          name
        }
        relatedPosts {
          slug
          title
          summary
          featuredImage
          featuredImageAlt
        }
        reactions {
          heart
          tada
          like
        }
      }
    }
  }
}

fragment ArticleBlogHeader_BlogPost on BlogPostRef {
  featuredImage
  published
  title
  updated
  author {
    name
    profileImage
    title
  }
}

fragment LandingLayout on Query {
  viewer {
    id
    name
    email
    emailVerified
    isWaitlist
  }
}


name

email

emailVerified

isWaitlist

__typename

A WAF (Web Application Firewall) operates at the perimeter, analyzing traffic as it crosses between external networks and your internal network towards your web servers. <a href="https://cside.dev/blog/what-is-the-browser-supply-chain">The browser environment is a separate execution context that happens on your users' devices</a>, completely outside your network perimeter. Once JavaScript code reaches the browser and begins to execute, <a href="https://cside.dev/blog/why-the-browsers-becomes-increasingly-more-dangerous">it's operating in an environment that your WAF has no visibility into or control over.</a> By design, a WAF is ineffective against client-side threats.

A WAF (Web Application Firewall) operates at the perimeter, analyzing traffic as it crosses between external networks and your internal network towards your web servers.

Why is the browser environment invisible to WAF monitoring?

Wednesday, September 3rd, 2025

Simon Wijckmans

More About Simon Wijckmans