Backend Service Auditor

Comprehensive auditor for backend services (APIs, workers, microservices) focusing on security, reliability, correctness, performance, data integrity, and operability. All findings are grounded in actual code and configuration.

When to Use

• Reviewing backend code changes before merge
• Security auditing APIs or microservices
• Pre-deployment checks for critical services
• Investigating reliability or performance concerns
• Auditing authentication/authorization flows
• Reviewing data handling and integrity patterns

Audit Workflow

On EVERY invocation, execute these steps in order:

Step 1: Detect Stack & Service Boundaries

Identify the technology stack and architectural boundaries:

- Language/framework (Node/Express/Nest, Go, Python/FastAPI, Java/Spring, Rust, etc.)
- Entrypoints (main files, server bootstrap, lambda handlers)
- Module/package boundaries
- Infrastructure config (Docker, K8s, Terraform, serverless.yml)
- Shared libraries and internal packages

Step 2: Scan Recent Changes

Review what has changed recently:

# Check working directory changes
git status
git diff --stat

# Review recent commits affecting backend
git log --oneline -20 --all -- "src/" "api/" "services/" "internal/"

Summarize:

• What behavioral changes were introduced?
• What new attack surface was added?
• What critical paths were modified?

Step 3: Build Service Map

Create a mental model of the service:

Step 4: Execute Audit Checklist

Audit touched services plus all critical paths (auth, payments, trading, user data).

See CHECKLIST.md for the complete audit checklist covering:

• Security (AuthN/AuthZ, injection, secrets, dependencies)
• Reliability & Correctness (idempotency, retries, concurrency, data integrity)
• Performance & Scalability (queries, caching, memory)
• Observability & Ops (logging, metrics, deployment)

Output Format

Structure your audit report as follows:

A) Scope Scanned

Services: [list services/modules audited]
Files reviewed: [count]
Commits analyzed: [range]
Stack: [detected technology stack]

B) Service Map

Endpoints: [count] routes across [modules]
Data stores: [list DBs, caches]
External deps: [list integrations]
Critical paths: [auth, payments, etc.]

C) Findings

Use severity levels:

For each finding:

### [SEVERITY] Title

**Location:** `path/to/file.ts:123`
**Category:** Security > Input Validation

**Issue:** [Describe the problem]

**Evidence:**
[Code snippet or proof]

**Risk:** [What could go wrong]

**Recommendation:** [How to fix]

D) Summary Table

E) Recommendations

Prioritized action items:

1. [Most critical fix]
2. [Second priority]
3. ...

Quick Commands

# Check for vulnerable dependencies (Node)
npm audit

# Check for vulnerable dependencies (Python)
pip-audit

# Find hardcoded secrets
grep -rn "password\|secret\|api_key\|token" --include="*.ts" --include="*.js" --include="*.py"

# Find TODO/FIXME security notes
grep -rn "TODO.*security\|FIXME.*auth\|XXX" src/

Resources

• CHECKLIST.md - Complete audit checklist
• PATTERNS.md - Common vulnerability patterns by framework