Skip to content
JAENES

PROTECTION GUIDE

Protection — self-defense by level

笹尾 祐太朗の写真Reviewed by Yutaro SasaoWritten by Leak Watch editorial team published

You cannot prevent every leak. What matters is limiting the damage when one happens and moving fast afterward. From "do today" basics to "design for defense", organized by level, with links to authoritative sources (CISA, NCSC, OWASP).

Beginner — the basics, starting today

About half an hour in total. This alone blocks most non-targeted damage (credential stuffing, first-wave phishing).

Adopt a password manager

Email-password pairs are what most breaches expose. Reuse the same pair and one leak becomes unauthorized logins everywhere (credential stuffing).

Let a password manager generate a strong, unique password per service; memorize only the manager's own passphrase. Even the browser's built-in manager is effective.

CISA — Secure Our World ↗

Enable multi-factor authentication (MFA)

Even with a leaked password, a second factor — an authenticator app or hardware key — blocks nearly all account takeovers. Authenticator apps (Google Authenticator etc.) and FIDO2/passkeys are safer than SMS codes.

Enable it on your most important accounts (email, finance, social) first. Email is the "last fortress" that receives password resets for everything else — start there.

passkeys.dev (official guide) ↗

Turn on automatic updates

Most attacks hit known vulnerabilities. Auto-updating your OS, browser, and phone apps keeps the known holes plugged.

CISA — Update Your Software ↗

Get used to being suspicious (phishing)

After a breach, phishing surges pretending to be the "change your password" notice. Never log in from links in email or SMS — open the official site or app yourself.

Urgent wording ("within 24 hours...") and trusting the sender display alone are mistakes. When unsure, contact the company's official support channel.

Check whether your data has leaked

Have I Been Pwned tells you if your email appeared in past breaches. For Japanese incidents, search this site's breach database by company name and data type.

Prioritize changing passwords for the affected service and for every service where you reused it.

Have I Been Pwned ↗

Intermediate — building structures that limit damage

Once the basics are done, build structures that keep the blast radius small.

Separate email addresses and aliases

Separate addresses for logins, receiving, and throwaway signups limit the scope of any leak and make it easier to identify which service leaked.

iCloud's Hide My Email or alias services like SimpleLogin let you register with a distinct address per service.

Move to passkeys and hardware keys

FIDO2/passkeys are phishing-resistant — the strongest form, removing the password itself. Set them up wherever offered.

For your most-targeted accounts (main email, social, finance), register a hardware key like a YubiKey as backup so device changes or loss don't lock you out.

FIDO Alliance ↗

Don't hand over your real card number

Prefer virtual cards (with limits and merchant restrictions), convenience-store payment, or carrier billing over giving real card numbers to online shops.

If a card-data breach is disclosed, contact your card issuer about reissue and set up transaction alerts.

Maintain recovery paths

After enabling MFA, store backup codes somewhere safe (password manager, or paper in a safe). Stale recovery emails and phone numbers mean you can't recover when it matters.

Delete accounts you no longer use

Dormant registrations are inventory for future leaks. Delete what you can; for services you can't leave, switch the email to a throwaway address.

Advanced — designing your attack surface deliberately

Design defenses around your own risk profile: what to protect, and from whom.

Threat modeling — decide what to protect from whom

Don't maximize everything: match controls to the assets you protect (money, reputation, privacy) and the realistic adversary (indiscriminate automation vs. targeted). NCSC's Small Business Guide offers a framework individuals can borrow.

NCSC — Small Business Guide ↗

DNS-level filtering

Filtering DNS like NextDNS or Quad9 blocks connections to malicious and phishing domains at the device level — and works for the whole family's devices.

Quad9 ↗

Isolate critical accounts in a dedicated environment

Keep main email and finance in a dedicated address and browser profile (or device) never used for everyday signups. If the everyday side gets contaminated, the critical side stays unreachable.

Public Wi-Fi and VPNs today

With HTTPS everywhere, eavesdropping on public Wi-Fi is less of a risk than it was. Higher priorities: never bypass certificate warnings, and avoid financial operations on public networks. A VPN still makes sense for geo-restrictions or link encryption.

The 3-2-1 backup rule

3 copies, 2 media, 1 off-site. Recovering from ransomware or accidental deletion is fastest with your own backups — faster than insurance or vendors.

For developers — security libraries & tools

Developer mistakes cause many leaks, and a large share is mechanically preventable with the right libraries and tools. The staples, by category.

Dependency vulnerability management

  • npm audit / pnpm auditLockfile-based known-vulnerability checks. A CI must.
  • DependabotGitHub's dependency-update bot. Auto-PRs when vulnerabilities appear.
  • SnykVulnerability management across dependencies, IaC, and containers.
  • RenovatePlanned dependency updates automated (beyond vulnerabilities).

Preventing secret leaks

  • gitleaksScans git history for API keys and other secrets. Use in pre-commit and CI.
  • GitGuardianSaaS for secret detection and monitoring — including after public exposure.
  • pre-commitEnforce secret, format, and static-analysis checks before commits.

Web application defenses

  • helmetSecurity-header (CSP, HSTS, etc.) middleware for Node/Express.
  • DOMPurifyThe definitive sanitizer against XSS. Always before rendering user HTML.
  • OWASP Top 10Web vulnerability priorities. Read this map first.
  • OWASP Cheat Sheet SeriesPer-topic checklists: SQLi, auth, sessions, and more.

Authentication & cryptography

  • argon2 / bcryptThe standards for password hashing. Never plaintext, MD5, or raw SHA.
  • Auth.js (OAuth/OIDC)Authentication for Next.js and friends. Prefer audited implementations.
  • joseModern JWT/JWE. Don't skip signature verification.

Static analysis & CI integration

  • SemgrepFast rule-based code scanning — including your team's own rules.
  • CodeQLGitHub's semantic vulnerability scanning (free for public repos).
  • TrivyAll-in-one scanner for containers, IaC, and dependencies.

Vulnerability information in Japanese is tracked on JVN; the international numbering scheme is CVE.

To check whether a service you use appears in an incident, search the breach database. For the latest, see news.

Written & reviewed

笹尾 祐太朗の写真

Reviewed byYutaro SasaoFounder & CEO, MediaLeap Inc.

CEO of MediaLeap Inc. Working on both sides of web advertising and web media since 2013; founded the company in May 2025.

Review scope: cross-checking against primary sources (official and government announcements), verifying claims stay within the facts, and checking source attribution。Last reviewed:

Written by:Leak Watch editorial team (AI-assisted drafts verified against sources by the editorial team) · Reviewer profile · Request a correction