A web client is software that accesses a web application or web service through a browser or browser-like interface. It sends HTTP requests, renders responses, and may store session cookies, tokens, or other client-side state used for authentication and access control.
What a web client does
A web client is the software endpoint that initiates web interactions, usually through a browser or browser-like runtime. It requests pages or API responses over HTTP, renders returned content, and often manages local state such as cookies, tokens, cache, and browser storage that shape the user’s authenticated session.
How web clients handle state and sessions
Although HTTP is stateless, web clients frequently preserve continuity across requests by storing session cookies, bearer tokens, or other client-side state. That state helps the application recognise the user, maintain login state, and enforce access decisions without requiring re-authentication on every request.
This makes the client more than a display layer. It participates in identity-bearing workflows by carrying session material, presenting tokens to services, and enforcing browser security boundaries such as same-origin rules, cookie scope, and storage isolation.
Browser-based behaviour and security boundaries
Web clients operate inside a browser security model that affects what they can send, store, and expose. Rendering scripts, following redirects, processing cross-site content, and sharing cookies across related domains all create trust boundaries that application designers must understand.
Client-side storage can improve usability, but it also enlarges the attack surface. A weakly protected browser environment can expose tokens to cross-site scripting, session fixation, token theft, malicious extensions, or unsafe reuse across tabs, profiles, and devices.
Because the client can execute code received from the server, web client security is tightly linked to content handling, session protection, and careful treatment of any data that influences authentication or authorisation decisions.
Common web client implementation patterns
Web clients include traditional desktop browsers, mobile browsers, embedded webviews, single-page applications, and custom browser-like interfaces used inside enterprise software. These implementations differ in how they store state, isolate origins, handle certificates, and enforce navigation or download controls.
Modern web clients also interact with OAuth flows, federated login, device-bound sessions, and API-backed front ends. In those cases, the client becomes part of the authentication path, not just the presentation tier, so token handling and redirect handling become security-critical design choices.
For that reason, the term is useful in architecture discussions whenever teams need to distinguish the trusted server from the less-trusted user-controlled runtime where session material and rendered content meet.
Risk and Threat Considerations
Web clients concentrate risk because they hold the artefacts that make a session usable, then render content that may be attacker-influenced. If an adversary can read or replay client-side state, they may hijack sessions, impersonate users, or pivot into protected web services.
Failure mechanism: The client stores or exposes cookies, tokens, or other session material in a context that can be read through script injection, malicious extensions, unsafe sharing, or overly broad browser storage, allowing the attacker to reuse that material as if it were legitimate.
Impact: The result can be account takeover, unauthorised access to web applications, exposure of sensitive data, and compromised access control decisions that appear valid to the server.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Web clients rely on session material and client-side auth state that must be managed securely. |
| IA-8 — Identification and Authentication (Non-Organizational Users) | Browser clients commonly authenticate external users through web-facing applications. | |
| AC-6 — Least Privilege | Client-held sessions should carry only the minimum access needed for the web interaction. | |
| Recommendation — Limit token lifetime, scope, and storage exposure for browser-held authentication material. Apply external-user authentication controls to the web client session path. Restrict browser-established sessions to the minimum privileges required. | ||
Practitioner Guidance
Why practitioners should care: Web clients are often the least controlled part of the web stack, yet they carry the state that governs access. Design choices about cookies, redirects, storage, and browser isolation determine whether a compromise stays local or becomes a session-wide breach.
What to watch for: Treat long-lived client-side tokens, mixed trust content, and browser features that widen token exposure as security design decisions, not convenience details. A client that can persist sensitive state must also be assumed to leak it under the wrong conditions.
Practitioner takeaway: The safest web client is one that keeps sensitive state tightly scoped, short-lived, and protected by the browser’s strongest available isolation and session controls.
Related resources from NHI Mgmt Group
- How should security teams reduce risk from client-side code in modern web apps?
- Why do third-party scripts increase client-side risk in regulated web apps?
- What breaks when organisations treat client-side protection as an add-on to broader web security platforms?
- What breaks when a web search feature accepts server-side path parameters from untrusted client input?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org