Skip to content

AL-JANEF/janef-forge / skills/security/security-logging

security-logging

Verified

Design and review security audit logging and detection: record who did what and when for auth events, data changes, and admin actions; never log passwords, tokens, or PII; keep logs tamper-evident; add a few high-value alerts such as failed-login thresholds. Use for audit trails, log redaction, monitoring, or incident investigation.

FileKindSize
SKILL.mdskill md4.8 KB
capability.jsonconfig1.9 KB
references/patterns.mdmarkdown3.1 KB
references/privacy-and-retention.mdmarkdown1.2 KB

references/patterns.md

View on GitHub
# Logging & Detection Patterns

Copyable structures for audit logging, redaction, and detection.

## Audit log entry structure

A consistent, structured (JSON) entry makes logs queryable and useful for
reconstruction:

```js
function auditLog(event) {
  logger.info({
    ts: new Date().toISOString(),   // UTC
    actor: event.userId,            // id, not full PII
    action: event.action,           // 'login.failure', 'record.update', 'role.grant'
    target: event.target,           // what was affected (record id, user id)
    source: {
      ip: event.ip,
      requestId: event.requestId,
    },
    outcome: event.outcome,         // 'success' | 'failure' | 'denied'
    // for mutations, a diff makes the entry genuinely useful:
    changes: event.changes,         // { field: { from, to } } — already redacted
  });
}
```

Example calls:
```js
auditLog({ userId: u.id, action: 'login.failure', target: u.id,
           ip, requestId, outcome: 'failure' });

auditLog({ userId: admin.id, action: 'role.grant', target: target.id,
           ip, requestId, outcome: 'success',
           changes: { role: { from: 'member', to: 'admin' } } });
```

## Redaction before logging

Strip sensitive fields before anything is written:

```js
const REDACT = ['password', 'token', 'authorization', 'cookie',
                'secret', 'apiKey', 'cardNumber'];

function redact(obj) {
  const out = Array.isArray(obj) ? [] : {};
  for (const [k, v] of Object.entries(obj)) {
    if (REDACT.includes(k)) out[k] = '[REDACTED]';
    else if (v && typeof v === 'object') out[k] = redact(v);
    else out[k] = v;
  }
  return out;
}

logger.info(redact(payload));
```

Mask rather than drop when a fragment aids debugging:
```js
const masked = card.slice(0, 6) + '******' + card.slice(-4);
```

## Detection: failed-login threshold

```js
// Count recent failures per account; alert + throttle past a threshold.
async function onLoginFailure(userId, ip) {
  const key = `login_fail:${userId}`;
  const count = await store.incr(key);
  if (count === 1) await store.expire(key, 15 * 60);   // 15-min window
  if (count >= 5) {
    auditLog({ userId, action: 'login.bruteforce_suspected', target: userId,
               ip, outcome: 'denied' });
    alert(`Repeated login failures for ${userId} from ${ip}`);
    throttleOrLock(userId);   // coordinate with auth-hardening's lockout policy
  }
}
```

## Detection rules worth having (pick a few, keep them actionable)

- N failed logins per account or IP within a window → brute-force alert.
- Spike in access-denied (403) responses → enumeration / privilege probing.
- Admin action outside normal hours → review.
- Bulk export / large data read by a single actor → possible exfiltration.
- Login from a new country for an account → step-up verification.

Keep the alert set small and high-signal. Each alert should have a clear action;
an alert nobody responds to just trains people to ignore alerts.

## Integrity

- Write logs append-only where possible.
- Ship logs off the generating machine (central log store) so a compromised host
  can't rewrite its own trail.
- Use consistent UTC timestamps so events across services line up.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall