Apa wae praktik keamanan utama kanggo aplikasi Node.js?

Question

Accepted Answer

Ngamanake aplikasi Node wis ateges ngalindungi saka kerentanan web umum (OWASP Top 10) ing lapisan-lapisan kang beda-beda — panganan input, otentikasi, dependensi, lan konfigurasi. Keamanan kang berlapis (defense in depth), dudu perbaikan tunggal.

## 1. Validasi lan sanitasi kabeh input

```js
import { z } from "zod";
// never trust client input — validate shape/type before using it
const schema = z.object({ email: z.string().email(), age: z.number().min(0) });
const data = schema.parse(req.body); // rejects malformed/malicious input
```

## 2. Cegah injeksi (SQL, NoSQL, command)

```js
// ❌ string concatenation → SQL injection
db.query(`SELECT * FROM users WHERE id = ${req.params.id}`);
// ✅ parameterized queries — input is data, never executable SQL
db.query("SELECT * FROM users WHERE id = $1", [req.params.id]);
```

Slalu nggunakake parameterized queries / ORM, lan nundhung gawe perintah saka input pengguna (deleng command injection kanthi `child_process`).

## 3. Otentikasi & rahasia

```text
✓ Hash passwords with bcrypt/argon2/scrypt (slow + salted) — never plain/SHA
✓ Store secrets in env vars, never in code/git
✓ Use httpOnly, secure, sameSite cookies for sessions (XSS-resistant)
✓ Sign/verify JWTs properly; keep tokens short-lived
```

## 4. Itungan header keamanan & rate-limit

```js
import helmet from "helmet";
import rateLimit from "express-rate-limit";

app.use(helmet()); // sets secure HTTP headers (CSP, HSTS, X-Frame-Options, etc.)
app.use(rateLimit({ windowMs: 60_000, max: 100 })); // throttle abuse/brute-force
```

`helmet` nambah header pelindung; rate limiting mbela saka brute-force lan DoS.

## 5. Tetep dependensi aman (supply chain)

```bash
npm audit          # check installed packages for known vulnerabilities
npm audit fix
# + keep deps updated; review postinstall scripts; pin versions via the lockfile
```

Kabeh kode Node iku paket pihak ketiga — dependensi sing rentan iku vektor serangan utama. Audit lan ngapdate regular.

## 6. Liyane essensial

```text
✓ Use HTTPS (TLS) everywhere; redirect HTTP → HTTPS
✓ Don't leak error details/stack traces to clients in production
✓ Escape output to prevent XSS (frameworks usually do this)
✓ Implement proper authorization (not just authentication) — check permissions per action
✓ CORS configured to an allowlist, not "*" for credentialed APIs
✓ Limit request body size to prevent payload-based DoS
```

## Apa iku penting

Aplicasi web iku target konstan, lan aplikasi Node kaekspos ing kabeh jangkauan kerentanan web — injeksi, otentikasi rusak, XSS, dependensi sing rentan, misconfiguration.

Tak ana ukuran tunggal sing cukup; keamanan iku **berlapis**: validasi input, parameterisasi queries, hash password kanthi bener, kelola rahasia kanthi aman, itungan header protektif, rate-limit, audit dependensi, lan nggunakake HTTPS.

Ngerteni praktik-praktik kasebut (lan risiko OWASP ing mburi padha) iku tanggung jawab penting kanggo sapa bae sing mbangun layanan Node produksi — luwih siji lapisan sing kelupaan (injeksi, rahasia sing bocor, dependensi sing durung diperbaiki) bisa ngompromiso kabeh sistem.