Secure Coding & OWASP Top 10 for Backend · 课时

安全的用户身份验证机制

设计并实现安全的身份验证流程，涵盖密码管理、凭据存储和暴力破解防护。

第 2 / 4 课12 个步骤

安全的用户身份验证机制 是 CoddyKit 上的免费 Secure Coding & OWASP Top 10 for Backend 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Secure Coding & OWASP Top 10 for Backend 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Secure Authentication Matters

Authentication is the process of verifying who a user claims to be. It's the gatekeeper to your application's resources.

Without strong authentication, attackers can easily impersonate users, gain unauthorized access, and compromise sensitive data. This makes it a critical first line of defense.

Identity Verification: Confirms user identity.
Access Control: Basis for granting permissions.
Data Protection: Prevents unauthorized data access.

Crafting Strong Passwords

The journey to secure authentication starts with users choosing strong passwords. Your system should enforce policies that guide users towards better choices.

Best practices for password policies include:

Minimum Length: At least 12-16 characters.
Complexity: Mix of uppercase, lowercase, numbers, and symbols.
Uniqueness: Prevent reuse of old passwords.
No Common Passwords: Block dictionary words or easily guessable patterns.

Hashing Passwords: One-Way Security

You should never store passwords in plain text. If your database is breached, all user accounts would be immediately compromised.

Instead, use a cryptographic hash function. Hashing converts a password into a fixed-size string of characters (a 'hash' or 'digest'). It's a one-way process: you can hash a password, but you cannot reverse the hash to get the original password back.

This means even if an attacker gets the hashes, they can't directly recover the passwords.

Hashing Passwords in Action

Here's a simple Java example demonstrating how a hash function works. We're using SHA-256, which generates a unique, fixed-length output.

Important: While SHA-256 is a one-way hash, it's not secure enough for passwords on its own. Strong password hashing requires additional techniques like salting and computational cost, which we'll discuss next.

import java.security.MessageDigest;
import java.security.NoSuchAlgorithmException;
import java.nio.charset.StandardCharsets;
import java.util.Base64;

public class Main {
  public static void main(String[] args) {
    String password = "mySecretPassword123";
    String hashedPassword = hashPassword(password);
    System.out.println("Original: " + password);
    System.out.println("Hashed:   " + hashedPassword);
  }

  public static String hashPassword(String password) {
    try {
      MessageDigest digest = MessageDigest.getInstance("SHA-256");
      byte[] hash = digest.digest(password.getBytes(StandardCharsets.UTF_8));
      return Base64.getEncoder().encodeToString(hash);
    } catch (NoSuchAlgorithmException e) {
      e.printStackTrace();
      return null;
    }
  }
}

The Power of Salting Passwords

To make password hashes even more secure, we use a salt. A salt is a unique, random string of data added to a password before it's hashed.

Here's why salting is crucial:

Prevents Rainbow Tables: Without salts, attackers can use pre-computed 'rainbow tables' to quickly find passwords from hashes.
Unique Hashes: Even if two users have the same password, their salted hashes will be different.
Increased Work: Forces attackers to crack each password individually, making attacks much slower and less efficient.

Always use a unique, cryptographically random salt for each password.

Storing Hashed Credentials Safely

Once you've hashed and salted a password, you need to store it securely. Both the hash and the salt should be stored in your database, usually in separate columns.

Key considerations for storage:

Database Security: Ensure your database itself is protected with strong access controls and encryption at rest.
No Plaintext: Reiterate: never store original passwords.
Use Strong Algorithms: Prefer algorithms like BCrypt, Argon2, or scrypt, which are designed to be computationally intensive (slow), making brute-force attacks harder.

Understanding Brute-Force Attacks

A brute-force attack is when an attacker tries to guess a password or login credential by systematically trying many combinations.

They might use dictionaries of common passwords, or simply try every possible character combination. Without protection, an attacker could try millions of guesses per second, eventually succeeding.

This can lead to unauthorized access, account lockouts for legitimate users (Denial of Service), and system resource exhaustion.

Defense: Rate Limiting Login Attempts

One of the most effective ways to combat brute-force attacks is rate limiting. This technique restricts the number of login attempts a user or IP address can make within a specific timeframe.

If the limit is exceeded, further attempts are temporarily blocked, slowing down or stopping the attacker.

Rate Limiting Example

This Java code demonstrates a basic rate-limiting concept. It tracks failed login attempts for a user and 'locks' the account after a certain threshold.

In a real application, this would involve database storage, IP tracking, and potentially time-based lockouts.

import java.util.HashMap;
import java.util.Map;

public class Main {
  private static Map<String, Integer> failedAttempts = new HashMap<>();
  private static final int MAX_ATTEMPTS = 3;

  public static void main(String[] args) {
    String username = "testUser";

    System.out.println("Attempt 1 for " + username + ": " + login(username, "wrongPass"));
    System.out.println("Attempt 2 for " + username + ": " + login(username, "wrongPass"));
    System.out.println("Attempt 3 for " + username + ": " + login(username, "wrongPass"));
    System.out.println("Attempt 4 for " + username + ": " + login(username, "wrongPass"));
    System.out.println("Attempt 5 for " + username + ": " + login(username, "correctPass"));
  }

  public static boolean login(String username, String password) {
    if (isAccountLocked(username)) {
      System.out.println(username + " is locked out. Try again later.");
      return false;
    }

    // Simulate password check
    if (!password.equals("correctPass")) {
      incrementFailedAttempts(username);
      System.out.println("Login failed for " + username);
      return false;
    } else {
      resetFailedAttempts(username);
      System.out.println("Login successful for " + username);
      return true;
    }
  }

  private static boolean isAccountLocked(String username) {
    return failedAttempts.getOrDefault(username, 0) >= MAX_ATTEMPTS;
  }

  private static void incrementFailedAttempts(String username) {
    failedAttempts.put(username, failedAttempts.getOrDefault(username, 0) + 1);
  }

  private static void resetFailedAttempts(String username) {
    failedAttempts.remove(username);
  }
}

Beyond Rate Limiting: Lockouts & CAPTCHA

While rate limiting is great, you can add more layers of defense:

Account Lockout: After a certain number of failed attempts (e.g., 5), temporarily lock the account for a duration (e.g., 30 minutes) or until manually reset.
CAPTCHA: Implement a CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) after a few failed attempts. This makes automated bot attacks much harder.
Multi-Factor Authentication (MFA): While covered in another lesson, MFA significantly boosts security by requiring more than just a password.

Check Your Understanding

Which of the following are recommended best practices for securely handling user passwords in a backend application?

在交互式课程中回答

Recap: Secure Authentication

You've learned the essentials of building secure user authentication processes:

Strong Passwords: Enforce policies for length, complexity, and uniqueness.
Password Hashing: Never store plain text passwords; use one-way hashing.
Salting: Add unique salts to prevent rainbow table attacks.
Secure Storage: Store hashes and salts in a protected database.
Brute-Force Protection: Implement rate limiting, account lockouts, and CAPTCHAs to deter attackers.

By following these principles, you significantly enhance the security of your users' accounts and your application.

免费开始

用 AI 导师学习 Secure Coding & OWASP Top 10 for Backend — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「安全的用户身份验证机制」课时是免费的吗？

是的 — 「安全的用户身份验证机制」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Secure Coding & OWASP Top 10 for Backend 课程的其余内容，请升级到 CoddyKit PRO。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。

「安全的用户身份验证机制」这节课中我会学到什么？

设计并实现安全的身份验证流程，涵盖密码管理、凭据存储和暴力破解防护。你通过在浏览器中直接运行的动手代码来练习 Secure Coding & OWASP Top 10 for Backend，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Secure Coding & OWASP Top 10 for Backend 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Secure Coding & OWASP Top 10 for Backend 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「安全的用户身份验证机制」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Secure Coding & OWASP Top 10 for Backend 课中编写并运行代码吗？

能。每节 Secure Coding & OWASP Top 10 for Backend 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Secure Coding & OWASP Top 10 for Backend