Urgent.News

What's breaking now, across thousands of outlets.

Tech

What is Web Security? A Simple Guide for Developers

Imagine this familiar scenario: You just finished building your full-stack application. You built a sleek frontend in React , developed a fast REST API in Node.js & Express , connected it to MongoDB , styled everything with CSS, and deployed it to the cloud. Everything works smoothly. Forms submit, buttons respond, and data loads quickly. Then, a senior developer sits down beside you and asks a…

Web security refers to the protection of a web application, its data, and its users when users do not behave honestly. It involves safeguarding various assets such as user accounts, passwords, authentication tokens, personal information, API endpoints, databases, business logic, and cloud infrastructure.

A typical web application operates through a sequence of interactions between the user, browser, network, API, authentication middleware, and database. Each step presents potential security risks ranging from untrusted input and XSS attacks in the frontend, packet sniffing and man-in-the-middle attacks in the network layer, to SQL injection and unencrypted sensitive fields in the database.

Authentication is the process of verifying a user's identity, akin to a security guard checking a badge at an entrance. It involves comparing entered credentials with stored hashes, ensuring the claimed identity is valid. Unlike trusting the frontend, all security checks must be performed on the backend server.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

We Stopped Waiting for Platform Changes to Find Us

For years, our warning system for Apple and Google changes was a developer whose build failed first. The community gave us excellent reports, but the sequence was backwards.

  • Codename One introduced daily scheduled Codex task to address platform changes.
  • Task identified Android 16 back handling and permission-safe Contact Picker changes.
  • Change moves security work into normal release cycle and helps developers choose narrower API.

Added a BFF layer before reaching for GraphQL. What happened next?

TL;DR: One table page was making 1 + 1 + N network calls and pulling every bill into the browser. A thin server layer that speaks "one screen at a time" fixed it.

  • React app made three network calls per page, causing N+1 problem
  • Introduced BFF (Backend For Frontend) to reduce requests to one per screen
  • BFF handled permission checks, caching, server-side computation, and data filtering

More from Tuesday 15 September →