Secure Coding & OWASP Top 10 for Backend · 课时

软件与数据完整性验证

实施机制来验证代码、配置和关键数据的完整性，防止未经授权的篡改或损坏。

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

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

What is Data Integrity?

In secure backend development, integrity means ensuring that data, code, and configurations haven't been tampered with or altered in an unauthorized way. Think of it as protecting against silent, malicious changes.

Without integrity, an attacker could:

Modify your application's code.
Change critical configuration settings.
Alter sensitive data in your database.

These changes can lead to system malfunction, data breaches, or complete compromise.

Hashing for Integrity

A core tool for integrity verification is cryptographic hashing. A hash function takes an input (like a file or a string) and returns a fixed-size string of bytes, called a hash value or digest.

Key properties of a good hash function:

Deterministic: Same input always gives same output.
One-way: Hard to reverse the hash to get the original input.
Collision-resistant: Hard to find two different inputs that produce the same hash.

Popular algorithms include SHA-256 and SHA-512.

Simple Hashing Example (Java)

Let's see how to generate a SHA-256 hash in Java. Notice how even a tiny change in the input string completely changes the hash output.

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 originalString = "CoddyKit is awesome!";
    String alteredString = "CoddyKit is awesome."; // Small change

    try {
      MessageDigest digest = MessageDigest.getInstance("SHA-256");

      byte[] hash1 = digest.digest(originalString.getBytes(StandardCharsets.UTF_8));
      String encodedHash1 = Base64.getEncoder().encodeToString(hash1);
      System.out.println("Original Hash: " + encodedHash1);

      byte[] hash2 = digest.digest(alteredString.getBytes(StandardCharsets.UTF_8));
      String encodedHash2 = Base64.getEncoder().encodeToString(hash2);
      System.out.println("Altered Hash:  " + encodedHash2);

    } catch (NoSuchAlgorithmException e) {
      e.printStackTrace();
    }
  }
}

Checking Software & Files

When you download software, especially from open-source projects, you'll often find a corresponding hash value (like an MD5 or SHA-256 checksum) provided. This allows you to verify the download.

Steps for verification:

Download the software and its provided hash.
Generate the hash of your downloaded file locally.
Compare your generated hash with the provided one.

If they match, the file hasn't been tampered with during download or storage.

Securing Configuration Files

Configuration files (.env, application.properties, web.xml) contain vital settings like database connection strings, API keys, and server ports. Tampering with these can open severe security holes.

To protect them:

Restrict access: Use strong file system permissions.
Hash at startup: Calculate and verify hashes of critical config files when your application starts.
Version control: Track changes using Git; prevent direct manual edits on production.

Protecting Data in Databases

Ensuring data integrity in databases goes beyond just hashing. It involves preventing unauthorized or accidental changes to the stored information.

Key database integrity mechanisms:

Constraints: PRIMARY KEY, UNIQUE, FOREIGN KEY, CHECK constraints enforce data rules.
Transactions: Ensure operations are atomic (all or nothing) to prevent partial updates.
Audit logs: Record who, what, and when data was changed.

For sensitive data, consider application-level hashing before storage, especially for immutable fields.

Digital Signatures & Trust

While hashing verifies what a file is, digital signatures verify who created it and that it hasn't been altered since it was signed. They add a layer of authenticity.

How they work:

The creator hashes the data.
They encrypt the hash with their private key (this is the "signature").
Anyone can use the creator's public key to decrypt the signature, get the original hash, and then compare it to a hash they calculate locally.

If hashes match, the signature is valid and the data is authentic.

Integrity During Execution

Integrity checks aren't just for files at rest. You can also monitor your application's integrity while it's running. This helps detect compromises that occur after deployment.

Examples of runtime checks:

Memory integrity: Detect unauthorized modifications to process memory.
Code integrity: Verify that loaded libraries or critical code segments haven't been swapped out.
System call monitoring: Look for unusual or unauthorized system calls from your application.

These are often part of advanced security solutions like RASP.

Continuous Integrity Monitoring

Manually checking integrity is not scalable. Automating these processes is crucial for continuous security.

Strategies for automation:

CI/CD integration: Hash critical files (code, configs) during build and deployment.
File Integrity Monitoring (FIM): Tools that continuously scan critical directories for changes and alert on deviations.
Scheduled tasks: Periodically run scripts to hash and compare critical system components.

Alerts from FIM tools should be integrated into your security monitoring system.

Check Your Integrity Knowledge

You've learned about various ways to ensure software and data integrity. Let's test your understanding!

Recap: Integrity is Key

We've explored how vital software and data integrity are for a secure backend. By implementing integrity verification mechanisms, you can protect against unauthorized tampering and ensure your systems behave as expected.

Remember to:

Use cryptographic hashing for files and critical data.
Securely manage configuration files.
Leverage database integrity features.
Consider digital signatures for authenticity.
Automate integrity monitoring with FIM tools.

These practices build a strong foundation for trust and reliability in your applications.

常见问题解答

「软件与数据完整性验证」课时是免费的吗？

是的 — 「软件与数据完整性验证」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 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 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 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