การจัดการข้อมูลลับอย่างปลอดภัย

When building applications, especially at the edge, you often need to handle sensitive information. These are called secrets.

Secrets include things like API keys, database credentials, authentication tokens, and private encryption keys. They are critical for your application's security and functionality.

A common mistake, especially for beginners, is to hardcode secrets directly into your application's source code.

• Exposure: Anyone with access to your code (e.g., in a public Git repository) can see your secrets.
• Rotation Issues: Changing a secret means changing and redeploying your code everywhere it's used.
• Security Breach: A single leak can compromise your entire system.

Cloudflare Workers provide a secure way to manage secrets using environment variables. These variables are:

• Injected securely at runtime, not stored in your code.
• Encrypted at rest by Cloudflare.
• Specific to each Worker, allowing fine-grained control.

They are accessed via the env object in your Worker's fetch handler.

This Worker accesses an environment variable named MY_API_KEY. Notice how the secret itself is never hardcoded in the script.

Try running it! (The actual key won't be shown for security).

Similar to Workers, Deno applications also use environment variables for secrets. You can access them using Deno.env.

For local development, you might use .env files (though not directly supported by Deno, tools like deno task or third-party modules can help). For Deno Deploy, secrets are configured securely through their platform UI or CLI.

Here's a simple Deno script that retrieves a secret named DB_PASSWORD from its environment variables. Run this example to see it in action.

For Cloudflare Workers, the Wrangler CLI is your go-to tool for managing secrets. It encrypts and securely uploads them to Cloudflare's infrastructure.

• wrangler secret put <NAME>: Prompts for a secret value and uploads it.
• wrangler secret delete <NAME>: Removes a secret.
• wrangler secret list: Lists all secrets for your Worker.

This keeps secrets out of your wrangler.toml file and source code.

A crucial security principle is the Principle of Least Privilege. This means:

• Granting only the minimum necessary permissions to access resources.
• Only giving access to secrets to the specific services or users that absolutely need them.

Avoid giving a Worker access to a secret it doesn't actually use, even if it seems convenient.

Even with secure storage, secrets can be compromised. Implement these practices:

• Secret Rotation: Regularly change your API keys and tokens (e.g., every 90 days). This limits the window of opportunity for attackers if a secret is leaked.
• Auditing: Monitor and log access to your secrets. This helps detect unusual activity and potential breaches.

Automate these processes where possible to reduce manual overhead.

Test your understanding of secure secrets management.

In this lesson, we learned about the importance of securely managing sensitive information in edge applications.

• Never hardcode secrets.
• Utilize platform-provided environment variables (Cloudflare Workers env, Deno Deno.env).
• Use tools like Wrangler CLI for secure secret deployment.
• Follow the Principle of Least Privilege.
• Implement regular secret rotation and auditing.

These practices are fundamental to building robust and secure edge applications.