Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Identity and Data Security for Web Development

Identity and Data Security for Web Development

Best Practices
Build web apps that limit the damage when identity or data protections fail.
by Jonathan LeBlanc 2016 204 pages
3.33
43 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Design for the breach, because prevention alone cannot guarantee safety

Plan for compromise. Security is not a promise that nobody will get in. It is a way to reduce the chance of intrusion, limit what an attacker can take, and buy time to respond. The book’s example is Slack’s 2015 breach: passwords had been stored as bcrypt hashes with unique salts, so stolen records were harder to turn into usable credentials. Slack also added two-factor authentication and a tool that let team owners log users out and require new passwords.

Make damage smaller. That example captures the book’s central stance: treat a breach as a possibility, not an impossibility. Encryption and response controls cannot erase risk, but they can change a catastrophic incident into a manageable one.

Analysis

The breach-planning approach resembles resilience engineering, which asks not only whether a system can fail, but how it behaves when failure occurs. That shift is valuable because organizations often spend heavily on prevention while neglecting detection, containment, and recovery. Slack’s response illustrates that security controls can preserve choices after an incident. The principle still needs operational follow-through: a kill switch matters only if someone can invoke it quickly, and stored hashes help only if the hashing method remains appropriately costly. Security is therefore a continuing capacity, not a box checked at launch.

Make safe choices easy, because users optimize for friction

Design for real behavior. Users often choose passwords they can remember, reuse them, or avoid extra security steps. The book cites a typical two-factor authentication adoption rate of only 5% to 10%. Requiring elaborate character combinations can backfire: people may forget passwords or write them down. The better goal is to build protection into the service rather than assume every user will select the safest option.

Reduce the burden. Password managers can generate and store stronger credentials. Clear password rules, visible input, and strength indicators can help users make better choices; the book notes research finding that users chose stronger passwords when shown a strength meter. Good security should protect people without turning every ordinary task into an obstacle course.

Analysis

This is a human-factors lesson as much as a technical one. A control that people routinely bypass is not effective in practice, even if its theoretical protection is strong. Usability research often treats friction as a design cost, while security treats it as a possible barrier to attackers; the challenge is to make the cost asymmetric, small for legitimate users and significant for abuse. Yet convenience should not become a blanket excuse to weaken safeguards. The right friction depends on the action: reading a public page and changing a payment destination do not deserve identical checks.

Store passwords as salted, deliberately slow hashes, never reversible encryption

Make guessing expensive. A password hash is a one-way transformation used to check a later login attempt without storing the original password. A salt is random data added before hashing; each password needs its own salt so identical passwords do not produce identical stored hashes and precomputed lookup tables become far less useful. Key stretching repeats computational work, slowing attackers who steal the database and try guesses offline.

Choose password tools. The book presents bcrypt, PBKDF2, and scrypt as password-oriented options, in contrast to fast general-purpose hashes such as MD5 and SHA-1. During login, the service hashes the submitted password using the stored salt and compares the result. As hardware improves or standards change, hashes can be upgraded when users next authenticate.

Analysis

The key insight is economic: a defender processes one login at a time, while an attacker with a stolen database can test guesses at scale. A deliberately expensive password hash changes that cost calculation. Salts do not make weak passwords strong, and they do not prevent online guessing, so rate limits and account protections still matter. The book’s three algorithms are useful vocabulary, but choosing parameters requires current guidance and maintained libraries. Teams should avoid designing their own password construction or treating a large hash output as a substitute for a suitable password-hashing scheme.

Collect less, encrypt what remains, and keep keys separate

Shrink the target. Data that is never collected cannot be stolen from your database. The book advises storing only what an application needs, encrypting sensitive information at rest, and keeping encryption keys apart from the data they protect. It also describes data federation: keeping personal records in the region where they are needed rather than copying everything into one central store.

Hand off what you can. A payment provider can store card details so an application does not have to hold them itself. The book also points to Slack’s hashed passwords and post-breach response as an example of limiting fallout. These measures do not make a breach impossible. They reduce the amount of valuable information exposed and make stolen information harder to exploit.

Analysis

Data minimization connects security engineering with privacy by design: less collection means fewer records to protect, fewer opportunities for misuse, and often less operational complexity. Separating keys from encrypted data is equally important because encryption offers little protection if an attacker can take both together. Outsourcing payment data can reduce an application’s direct exposure, but it does not remove responsibility for choosing and monitoring the provider. Regional storage can help meet legal or operational needs, though duplicated systems can introduce their own access-control and maintenance risks.

Match identity checks to the risk of the action

Choose the right identity. The book distinguishes social identity, which supports casual services and social connections; concrete identity, which includes details such as address or payment information; and thin identity, which verifies a person without requiring a rich profile. These models can overlap, but a service should request only the attributes its purpose requires. Forcing login before a visitor can even preview a service may hurt conversion and needlessly collect information.

Adjust confidence carefully. Trust zones use signals such as a known device, browser, or location to estimate whether a user is likely to be genuine. The book cites an Electronic Frontier Foundation browser study in which 84% of tested browsers had unique configurations. Such signals may help tailor checks, but location can be masked and device details can change.

Analysis

This is a useful expression of proportionality: identity is not a single switch, and not every interaction requires the same assurance. The model also aligns with data minimization, because a low-risk service can avoid collecting the more revealing details required by banking or commerce. Browser fingerprints and location signals deserve particular restraint. Uniqueness does not prove that a device belongs to the person claiming an account, and gathering these signals can create privacy risks of its own. A risk score should inform a decision, not silently become a substitute for a reliable authentication factor.

Use OAuth for delegated access, and OpenID Connect for login

Separate two jobs. Authentication establishes who is signing in; authorization determines what that person or application may access. OAuth 2.0 is primarily an authorization framework: it lets a user grant a client limited access without handing that client the user’s password. OpenID Connect adds a standardized authentication layer to OAuth 2.0 and can provide identity claims through an ID Token and a UserInfo endpoint.

Limit each grant. The book explains that scopes describe what information or resources a client may request. In a common authorization-code flow, the user approves access, the service redirects a code to the client, and the client exchanges that code for a token. A state value helps guard against cross-site request forgery during the redirect, while short-lived access tokens reduce the window for misuse.

Analysis

The distinction prevents a persistent category error: a token that grants access to an API does not, by itself, establish a standardized identity for a user. Delegation also improves the password model by avoiding repeated disclosure of credentials to unrelated sites. The design works only when scopes are narrow, redirect destinations are validated, and tokens are protected in transit and storage. Protocol names can create a false sense of safety; a system may use OAuth and still mishandle tokens or grant excessive access. The authorization decision remains a product and governance choice, not merely a standards-compliance exercise.

Layer possession, knowledge, and biometrics without trusting any single factor

Add independent evidence. Multifactor authentication combines different kinds of proof: something a user knows, something the user possesses, and something associated with the user’s body. A one-time password is usable once or for a short interval, reducing the value of replaying an old code. The book discusses authenticator apps, text messages, and hardware keys, while noting that SMS can be intercepted and is not strongly encrypted.

Treat biometrics differently. A password can be replaced after exposure; a fingerprint cannot. The book recounts the Chaos Computer Club’s 2013 demonstration of bypassing Apple Touch ID with a replica made from a photograph. It therefore frames biometrics as a way to verify identity, not as an infallible secret. FIDO’s UAF and U2F approaches aim to combine or add factors while keeping biometric checks local to the device.

Analysis

Multiple factors are strongest when compromise of one does not automatically compromise the others. A password plus a code delivered through the same compromised account may offer less independence than the label suggests. Biometrics also change the recovery problem: they are convenient identifiers, but cannot be rotated like a password, and their use raises consent and privacy questions. The book’s central caution is sound: a biometric match is evidence, not certainty. Authentication design should include fallback and recovery paths, since a factor that locks out legitimate users can push them toward weaker workarounds.

Treat sessions, XSS, and CSRF as separate doors to secure

Layer the application. A session lets a user stay signed in across requests, often through a browser cookie. Session identifiers should be difficult to guess, and cookies should be configured for secure transport. Cross-site scripting, or XSS, tricks a browser into running malicious code in a trusted site; escaping displayed input helps prevent that. Cross-site request forgery, or CSRF, tricks a browser into sending an unwanted request as an authenticated user; a unique token checked on submission can block it.

Use multiple controls. The book recommends safe template escaping, session protections, CSRF middleware, and security headers through tools such as Helmet or Lusca. Browser filters can add protection, but should not replace server-side safeguards. Each defense covers a different failure mode, so one successful control should not be mistaken for complete security.

Analysis

The castle analogy in the book captures defense in depth, but the more useful principle is independence: layers should fail in different ways. Output escaping addresses how data becomes executable; a CSRF token addresses whether a request was deliberately initiated by the site’s user. A secure session cookie addresses yet another boundary. Middleware can make sound defaults easier to apply, but it can also hide configuration choices from developers. Security reviews should verify the behavior of the deployed application, not just the presence of a package or header.

Use TLS for transport, and avoid inventing your own cryptography

Protect data in motion. TLS provides an encrypted connection between a client and a server, while a certificate helps the client verify the server’s identity. The book distinguishes this from encryption at rest, which protects stored information. It also explains the broad trade-off between public-key cryptography, which uses related public and private keys, and symmetric cryptography, which uses a shared secret and is generally faster.

Protect integrity too. Encryption alone does not necessarily show whether data was altered. The book presents AES-GCM as a mode that provides both confidentiality and authentication, while emphasizing that the parties must handle keys and initialization data correctly. A self-signed certificate is useful for local testing, not a trusted production site. Prefer established secure transport and vetted cryptographic libraries to custom schemes.

Analysis

The practical lesson is to use cryptography as a system, not as a collection of impressive algorithms. Key generation, storage, rotation, certificate validation, and error handling all determine whether encryption actually protects users. TLS already combines key agreement and efficient symmetric encryption, so application developers rarely need to assemble these pieces themselves. The book’s code samples are demonstrations from 2016, not production recipes. Modern implementations should follow current protocol guidance and library documentation, particularly because cryptographic defaults and supported APIs change over time.

Analysis

This book is best understood as a developer’s tour of security decisions, not as a timeless implementation manual. Its strongest organizing idea is that identity protection depends on a chain of human, software, and operational choices. Password storage, delegated authorization, multifactor checks, sessions, browser behavior, and encrypted transport solve different problems. None can stand in for the others. The book is especially effective when it translates abstract risk into engineering choices, such as unique salts, short-lived tokens, minimal data retention, and checks proportionate to the sensitivity of an action.

Its most valuable conceptual move is to treat usability as part of security rather than its enemy. Users routinely choose convenience, so systems must make safer behavior practical. Its account of trust zones extends this idea by asking whether known devices or contexts can reduce unnecessary challenges. That proposal is useful but needs a privacy boundary: a distinctive browser or location is not proof of identity, and persistent identification can itself become a harm.

The technical material requires a sharper historical filter. Published in 2016, the code examples use libraries and APIs that may be obsolete, and some claims should not be copied as written. Most notably, SHA-256 is a hash function, not an encryption algorithm, despite its inclusion among recommended database-encryption options in the text. Password hashing, encryption at rest, and transport security are distinct jobs. The book’s sample implementations should therefore be read as teaching illustrations, not deployed without current review.

The durable lesson is architectural: minimize sensitive data, make stolen records difficult to exploit, limit each identity grant, and plan for containment and recovery. The specific tools will change. The discipline of asking what each control protects, what it fails to protect, and how users will actually encounter it remains the book’s lasting contribution.

Summary in 30 Seconds
Treat compromise as a possibility: minimize stored data, encrypt what remains, and keep keys separate. Store passwords with unique salts and deliberately slow hashing so stolen records cost more to crack. Match identity checks to the action’s risk, and distinguish login from delegated access. Secure transport, sessions, cross-site scripting, and request forgery with controls suited to each threat. Usability matters because burdensome safeguards are often bypassed.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.33 out of 5
Average of 43 ratings from Goodreads and Amazon.

Identity and Data Security for Web Development receives mixed reviews, with an average rating of 3.32 out of 5. Readers appreciate its wide coverage of web security topics and use of JavaScript examples. The book is seen as a good introduction, providing links for further exploration. However, some criticize its lack of depth and real-world examples. Reviewers suggest it's suitable for beginners but may not satisfy those seeking more advanced content. The availability of a GitHub repository for practicing examples is noted as a positive feature.

Your rating:
3.98
69 ratings
Want to read the full book?

Glossary

Password fatigue

Strain from managing passwords

Password fatigue is the burden people experience when they must create and remember many passwords. The book links this burden to predictable choices, reuse, and avoidance of security steps. Password managers and more usable sign-in flows can reduce the burden without expecting users to memorize a different complex password for every service.

Information entropy

A measure of unpredictability

In password security, information entropy estimates how difficult a password is to guess, expressed in bits. It depends on factors such as the possible character set and password length. The book cautions that human-created passwords are hard to measure accurately because people choose patterns and familiar words rather than random combinations.

Salt

Unique random hashing input

A salt is random data combined with a password before it is hashed. A distinct salt for each password makes matching passwords produce different stored hashes and undermines precomputed hash tables. Salts are typically stored with the password hash so the service can repeat the same calculation during a login attempt.

Key stretching

Repeated work to slow guessing

Key stretching applies a password-hashing process repeatedly, or with substantial computational or memory cost, to make each password guess slower. This is intended to hinder attackers who obtain stored password hashes and test guesses offline. It raises the cost of cracking but does not make weak passwords impossible to guess.

Trust zones

Context-based confidence levels

Trust zones are a way to vary authentication requirements according to evidence about a user and their context. Signals may include a familiar device, browser configuration, or location. A higher confidence estimate can reduce unnecessary prompts, while unfamiliar or risky circumstances can trigger additional checks. These signals are indicators, not definitive proof of identity.

OAuth 2.0

Delegated resource authorization

OAuth 2.0 is an authorization framework that lets a user grant a client limited access to protected resources without giving the client the user’s password. It uses grants and access tokens, with scopes describing the permitted access. OAuth 2.0 alone is not a standardized user-authentication protocol; OpenID Connect supplies that identity layer.

OpenID Connect

Authentication built on OAuth

OpenID Connect is an identity and authentication layer built on OAuth 2.0. It standardizes how a client can learn that a user has authenticated and, when authorized, receive claims about that user. Its ID Token carries authentication information, while a UserInfo endpoint can return additional profile claims.

One-time passwords

Short-lived or single-use codes

One-time passwords are authentication codes intended to be accepted once or for a limited period. They can be generated by an authenticator application or delivered through channels such as SMS or email. Their changing or single-use nature reduces the value of replaying a previously captured code, though the delivery channel may have vulnerabilities.

Security-layering

Stacked, complementary defenses

Security-layering is the practice of combining protections so that a failure in one control does not automatically expose the entire system. In a web application, layers might include secure password storage, protected sessions, output escaping, CSRF tokens, and encrypted transport. The approach works best when each control addresses a distinct threat.

UAF

Passwordless FIDO authentication

The Universal Authentication Framework is a FIDO approach designed for passwordless or multifactor authentication. It can use local device mechanisms such as a PIN, fingerprint, or voice input to verify the user. The design described in the book keeps biometric verification on the device rather than sending biometric details to the service.

U2F

Hardware-based second factor

Universal 2nd Factor is a FIDO standard that adds a hardware authenticator to an existing login. The device communicates through a supported browser and may connect using USB or NFC. It is intended to strengthen password-based sign-in without requiring the user to depend on a code sent by text.

About the Author

Jonathan LeBlanc is an author and expert in the field of web development and security. While specific biographical information is not provided in the given content, his work suggests a strong background in identity management and data protection within web applications. LeBlanc's approach in the book indicates a focus on practical, code-based explanations using popular technologies like NodeJS and JavaScript. This writing style suggests he may have experience as a developer or technical educator. His choice to cover a broad range of topics at an introductory level implies an intent to provide a comprehensive overview of web security for developers new to the field.

Download PDF

To save this Identity and Data Security for Web Development summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.32 MB     Pages: 16

Download EPUB

To read this Identity and Data Security for Web Development summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.38 MB     Pages: 19
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...