secure-by-default

Enforces input validation, least privilege access and secret redaction in software.

Updated Aug 23, 2026
Ready to run
npx skills add https://github.com/dylanmarriner/windsurf-hooker --skill secure-by-default
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: secure-by-default
Source: https://github.com/dylanmarriner/windsurf-hooker/tree/main/windsurf/skills/secure-by-default
Command: npx skills add https://github.com/dylanmarriner/windsurf-hooker --skill secure-by-default

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures security guardrails are built into software by enforcing input validation, least-privilege access, and redaction of secrets by default, reducing risk from insecure coding practices.

Core Features & Use Cases

  • Automated input validation across boundaries (HTTP requests, API payloads, file uploads) to prevent malformed data.
  • Enforced least-privilege access for services and components, minimizing blast radius.
  • Secrets redaction and safe-logging to prevent leakage of credentials or tokens.
  • Use Case: Integrate these guardrails into a new API endpoint to ensure only well-formed requests are processed and secrets are never logged.

Quick Start

Configure your project to validate external input, apply least-privilege, and redact secrets by default in all critical paths.

Frequently Asked Questions about secure-by-default

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent secrets and credentials from leaking in application logs?▼

Secrets redaction prevents credentials and tokens from leaking by automatically masking sensitive data in application logs. It enforces safe-logging practices across services and data-handling components to ensure credentials are never exposed in log output.

What is the best way to enforce input validation across API payloads and HTTP requests?▼

Input validation across boundaries checks HTTP requests and API payloads to prevent malformed data processing. Automated validation ensures only well-formed requests reach your services, reducing risk from insecure coding practices and injection vulnerabilities.

How do I implement least-privilege access control for microservices and API components?▼

Least-privilege access control restricts service and component permissions to minimize blast radius. Enforcing least-privilege ensures services only access resources strictly required for operation, reducing risk from over-permissive roles across runtimes.

Can I apply secure-by-default guardrails across different programming languages and runtimes?▼

Secure-by-default checks apply across languages and runtimes for APIs, services, and data-handling components. The guardrails validate inputs, enforce least privilege, and redact secrets regardless of the specific implementation language.

When do I need to configure input validation and secrets redaction in my software development lifecycle?▼

Configure input validation and secrets redaction during development of critical paths in new API endpoints and services. Integrating these guardrails early ensures only well-formed requests are processed and sensitive data is protected by default.